Topic: multi-agent
1,931 skills in this topic.
-
dev-skillify
Convert the current conversation into a reusable skill. Different from skill-creator (which creates from scratch) — skillify captures what just happened and templatizes it.
EvolutionAPI/evo-nexus 211
-
hr-recruiting-pipeline
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
-
obs-json-canvas
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
EvolutionAPI/evo-nexus 211
-
legal-signature-request
Preparar e encaminhar um documento para assinatura eletrônica — executar checklist pré-assinatura, configurar ordem de assinatura e enviar para execução. Use quando um contrato está finalizado e pronto para assinar, ao verificar nomes de entidades, anexos e blocos de assinatura antes de enviar, ou ao configurar um envelope com signatários sequenciais ou paralelos.
EvolutionAPI/evo-nexus 211
-
fin-audit-support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
EvolutionAPI/evo-nexus 211
-
dev-remember
Persist context across engineering sessions — save important decisions, gotchas, or patterns that should survive beyond the current conversation. For long-term workspace memory, prefer mempalace.
EvolutionAPI/evo-nexus 211
-
data-analyze
EvolutionAPI/evo-nexus 211
-
cs-ticket-triage
Triagem e priorização de ticket ou problema de suporte. Use ao receber um novo ticket que precisa de categorização, atribuição de prioridade P1-P4, decisão sobre qual time deve tratar, ou verificação de duplicidade antes de encaminhar. / Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.
EvolutionAPI/evo-nexus 211
-
ops-vendor-review
Avaliar um fornecedor — análise de custo, avaliação de risco e recomendação. Use quando revisar proposta de novo vendor, decidindo renovar ou substituir contrato, comparando dois vendors lado a lado, ou construindo breakdown de TCO e pontos de negociação antes da aprovação. Agente Nex.
EvolutionAPI/evo-nexus 211
-
ops-status-report
Gerar relatório de status com KPIs, riscos e action items. Use quando escrever update semanal ou mensal para liderança, resumir saúde do projeto com status verde/amarelo/vermelho, surfacing riscos e decisões que precisam de atenção dos stakeholders, ou transformar atividade do Linear em narrativa legível. Agente Atlas.
EvolutionAPI/evo-nexus 211
-
pm-roadmap-update
Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.
EvolutionAPI/evo-nexus 211
-
pm-write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
EvolutionAPI/evo-nexus 211
-
pm-stakeholder-update
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
EvolutionAPI/evo-nexus 211
-
prod-trends
Weekly trends analysis — compares community, GitHub, and financial metrics week-over-week to detect patterns, risks and opportunities. Use when user says 'trends analysis', 'trends', 'how are the metrics', 'weekly comparison', 'metrics evolution', or as part of the weekly review routine.
EvolutionAPI/evo-nexus 211
-
prod-activation-plan
Create a phased activation plan using the EvoNexus standard structure — single index file + folder-per-phase + file-per-item, each item detailed with owner, dependencies, decisions pending, suggested agent team. Use when the user asks for an activation plan, implementation plan, rollout plan, or any phased plan for business/engineering initiatives. Also triggered by Oracle's Step 6 (implementation plan delivery) instead of writing an ad-hoc plan.
EvolutionAPI/evo-nexus 211
-
pulse-monthly
Monthly community report — aggregates Discord and WhatsApp activity for the full month: MAM, growth, sentiment trends, top contributors, product insights, docs gaps, and week-over-week evolution. Generates an HTML report using the Evolution brand. Use when user says 'community monthly', 'monthly community report', 'monthly pulse', or any reference to monthly community analysis.
EvolutionAPI/evo-nexus 211
-
pulse-faq-sync
Sync and update the community FAQ from Discord conversations, WhatsApp groups, and GitHub issues. Identifies recurring questions, adds new entries, and keeps the FAQ as a living knowledge base. Use when user says 'update faq', 'sync faq', 'community faq', 'frequently asked questions', or when running community routines that detect unanswered/recurring questions.
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-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
-
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-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