Topic: multi-agent
1,931 skills in this topic.
-
hr-draft-offer
Rascunha uma carta/proposta de oferta com detalhes de remuneração e termos. Use quando um candidato está pronto para receber uma oferta, ao montar o pacote de remuneração total (base, equity, bônus de assinatura), ao escrever o texto da proposta, ou ao preparar orientações de negociação para o hiring manager.
EvolutionAPI/evo-nexus 211
-
hr-comp-analysis
EvolutionAPI/evo-nexus 211
-
gog-calendar
Review calendar agenda, find available meeting slots, and schedule events. Displays today's or week's schedule, suggests meeting times based on availability, creates calendar events with explicit user confirmation. Use when user mentions calendar, schedule, meetings, or availability. Never creates or modifies events without confirmation.
EvolutionAPI/evo-nexus 211
-
fin-weekly-report
Weekly financial report — consolidates Stripe and Omie data for the week: revenue, expenses, cash flow projection, overdue accounts, and variance analysis. Trigger when user says 'financial weekly', 'weekly financial report', or 'financial summary of the week'.
EvolutionAPI/evo-nexus 211
-
fin-sox-testing
Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.
EvolutionAPI/evo-nexus 211
-
fin-daily-pulse
Daily financial pulse — queries Stripe (MRR, charges, churn, failures) and Omie (accounts payable/receivable, invoices) to generate an HTML snapshot of the company's financial health. Trigger when user says 'financial pulse', 'financial snapshot', or 'financial metrics'.
EvolutionAPI/evo-nexus 211
-
fin-close-management
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
EvolutionAPI/evo-nexus 211
-
social-audience-growth-tracker
When the user wants to track follower growth, understand what drives new followers, or analyze audience development. Also use when the user mentions 'follower growth,' 'followers,' 'audience growth,' 'gaining followers,' 'losing followers,' 'who follows me,' or 'grow my audience.' Uses BlackTwist follower data when available. For post-level metrics, see social-performance-analyzer. For content patterns, see social-content-pattern-analyzer.
EvolutionAPI/evo-nexus 211
-
social-content-strategy
When the user wants to plan a social media content strategy, decide what to post, or figure out topic clusters and content mix. Also use when the user mentions 'content strategy,' 'what should I post,' 'content ideas,' 'topic clusters,' 'content pillars,' 'content planning,' 'content mix,' 'I don't know what to post,' or 'social media strategy.' Use this to define the what and why of posting. For writing actual posts, see social-post-writer. For scheduling, see social-content-calendar. For platform-specific tactics, see social-platform-strategy.
EvolutionAPI/evo-nexus 211
-
social-content-repurposer
When the user wants to turn one piece of content into multiple formats or adapt content across platforms. Also use when the user mentions 'repurpose,' 'turn this into,' 'adapt this for,' 'cross-post,' 'reformat,' 'blog to social,' 'newsletter to posts,' or 'get more from this content.' For writing original posts, see social-post-writer. For threads, see social-thread-writer. For carousels, see social-carousel-writer.
EvolutionAPI/evo-nexus 211
-
trigger-registry
Create, manage, and test reactive triggers (webhook & event-based). Triggers execute skills or routines in response to external events (GitHub push, Stripe payment, Linear issue, etc.). Use when user says 'create trigger', 'list triggers', 'novo trigger', 'webhook para', 'quando acontecer', 'trigger list', 'test trigger', or any reference to reactive event triggers.
EvolutionAPI/evo-nexus 211
-
social-thread-writer
When the user wants to write a multi-part thread for Twitter/X, LinkedIn, or other platforms. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,' 'multi-part post,' 'series of posts,' or has a long-form idea that needs breaking into parts. For single posts, see social-post-writer. For carousels, see social-carousel-writer.
EvolutionAPI/evo-nexus 211
-
social-post-writer
When the user wants to write a social media post for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'write a post,' 'draft a post,' 'LinkedIn post,' 'tweet,' 'Threads post,' 'Bluesky post,' 'social media post,' 'help me write,' or shares a topic and wants it turned into a post. For multi-part content, see social-thread-writer. For carousels, see social-carousel-writer. For opening lines specifically, see social-hook-writer.
EvolutionAPI/evo-nexus 211
-
social-platform-strategy
When the user wants platform-specific tactical guidance for LinkedIn, Twitter/X, Threads, or Bluesky. Also use when the user mentions 'LinkedIn strategy,' 'Twitter strategy,' 'Threads strategy,' 'Bluesky strategy,' 'algorithm,' 'what works on LinkedIn,' 'cross-posting,' 'platform differences,' 'adapt my content,' or 'which platform should I focus on.' For overall content strategy, see social-content-strategy. For writing posts, see social-post-writer.
EvolutionAPI/evo-nexus 211
-
social-performance-analyzer
When the user wants to analyze how their social media posts are performing. Also use when the user mentions 'analytics,' 'performance,' 'how did my posts do,' 'engagement,' 'impressions,' 'what's working,' 'post metrics,' 'my best posts,' or 'why isn't this post performing.' Uses BlackTwist analytics when available, works from user-provided data otherwise. For audience growth specifically, see social-audience-growth-tracker. For pattern detection, see social-content-pattern-analyzer. For actionable next steps, see social-optimization-advisor.
EvolutionAPI/evo-nexus 211
-
dev-ai-slop-cleaner
Post-AI-generation cleanup — remove single-use helpers, over-abstractions, generic naming, and unnecessary configurability. Use after dev-autopilot or any LLM-generated code burst.
EvolutionAPI/evo-nexus 211
-
data-validate
Valida uma análise antes de compartilhar — metodologia, precisão e verificações de viés. Use quando revisar uma análise antes de uma apresentação para stakeholders, verificar cálculos e lógica de agregação, conferir se os resultados de uma query SQL parecem corretos, ou avaliar se as conclusões são de fato suportadas pelos dados. Sempre rodar esta skill antes de compartilhar análises baseadas em Stripe, Omie, Licensing ou Evo CRM.
EvolutionAPI/evo-nexus 211
-
data-statistical-analysis
Aplica métodos estatísticos incluindo estatísticas descritivas, análise de tendências, detecção de outliers e testes de hipótese para dados do workspace. Use quando analisar distribuições de MRR/churn, testar se uma mudança de produto moveu métricas, detectar anomalias em instâncias do Licensing, calcular correlações, ou interpretar resultados estatísticos. Execução local via Python.
EvolutionAPI/evo-nexus 211
-
data-create-viz
Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento
EvolutionAPI/evo-nexus 211
-
cs-draft-response
Redige uma resposta profissional voltada ao cliente adaptada à situação e ao relacionamento. Use para responder uma pergunta de produto, responder a uma escalação ou incidente, entregar uma má notícia como atraso ou won't-fix, recusar um feature request, ou responder a um problema de billing. / Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
EvolutionAPI/evo-nexus 211
-
cs-customer-research
Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
EvolutionAPI/evo-nexus 211
-
cs-customer-escalation
Empacota uma escalação para Devs, Produto ou Davidson com contexto completo. Use quando um bug precisa de atenção além do suporte normal, vários clientes reportam o mesmo problema, um cliente está ameaçando cancelar, ou um problema ficou sem resolução além do SLA. / Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.
EvolutionAPI/evo-nexus 211
-
create-routine
Create a new automated routine (ADW) for the scheduler. Guides the user through defining what the routine does, the type (AI or systematic), the schedule, and generates the Python script + Makefile target. Use when the user says 'create a routine', 'add a routine', 'automate this', 'schedule this task', 'new ADW', 'I want this to run automatically', or wants to turn any manual task into a scheduled automation.
EvolutionAPI/evo-nexus 211
-
create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants to create a reusable slash command.
EvolutionAPI/evo-nexus 211