Sponsored by

Find leads on Reddit on auto pilot

Agent skills
claude-code

Topic: claude-code

35,830 skills in this topic.

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-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
dev-deep-dive Two-stage investigation — causal trace (via @trail-tracer) followed by requirements crystallization (via @echo-analyst + dev-deep-interview). Use when a problem is both unclear in cause AND unclear in scope.
EvolutionAPI/evo-nexus 211
dev-visual-verdict Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
EvolutionAPI/evo-nexus 211
dev-ccg Tri-model orchestration — run the same task through Claude + Codex + Gemini in parallel and synthesize the best answer. Use for high-stakes decisions where multi-model consensus reduces single-model bias.
EvolutionAPI/evo-nexus 211
dev-verify Verify that a change really works before claiming completion. Use when the user wants confidence that a feature, fix, or refactor actually works — turns vague "it should work" claims into concrete evidence. Pairs with @oath-verifier agent.
EvolutionAPI/evo-nexus 211
dev-ultraqa QA cycling workflow — repeat build/lint/test/fix cycles up to 5 times until all checks pass. Stops early if the same error repeats 3 times (signals a fundamental issue, not a fixable one).
EvolutionAPI/evo-nexus 211
dev-ask Advisory router — query Claude, Codex, or Gemini for a quick second opinion. Experimental — only Claude is guaranteed available; other models require dev-mcp-setup configuration.
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
dev-trace Evidence-driven causal tracing with competing hypotheses. Use when an observation has multiple plausible explanations and you need to systematically rank them with evidence FOR and AGAINST each. Pairs with @trail-tracer.
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
dev-team On-demand spawning of multiple engineering agents in parallel for large-context work. Use when a task is too big for a single agent and the work can be split into independent streams.
EvolutionAPI/evo-nexus 211
dev-sciomc Scientific method scaffolding — hypothesis → experiment → evidence → conclusion. Use when you need rigorous causal reasoning rather than vibes-based debugging.
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
dev-release Release preparation — changelog generation, version bump, tag creation. Generic version (not project-specific). For EvoNexus releases, use custom-release instead.
EvolutionAPI/evo-nexus 211
dev-project-session-manager Worktree-first development environment — create per-issue or per-PR git worktrees, optionally with tmux sessions, so multiple work streams don't collide.
EvolutionAPI/evo-nexus 211
fin-variance-analysis Decompose financial variances into drivers with narrative explanations and waterfall analysis. Use when analyzing budget vs. actual, period-over-period changes, revenue or expense variances, or preparing variance commentary for leadership.
EvolutionAPI/evo-nexus 211
dev-learner Meta-skill — extract reusable skills from the current conversation. Identifies patterns that appeared 3+ times and proposes them as new skills. Pairs with skill-creator builtin.
EvolutionAPI/evo-nexus 211
dev-external-context Parallel external documentation lookup. Spawn multiple @scroll-docs agents simultaneously to fetch SDK refs, API docs, and framework guides for different topics in one pass.
EvolutionAPI/evo-nexus 211
dev-deepinit Deep codebase initialization — generate hierarchical AGENTS.md / CLAUDE.md context files for a new project so engineering agents have full context from session start.
EvolutionAPI/evo-nexus 211
dev-deep-interview Socratic questioning to crystallize vague requirements into a testable spec. Use when input is ambiguous, when the user asks for "deep interview", or before dev-autopilot if the brief is too broad. Pairs with @echo-analyst.
EvolutionAPI/evo-nexus 211
gog-email-triage Triage and prioritize inbox emails. Summarize unread messages, classify by urgency and category, propose actions (reply, archive, schedule, create task). Use when user wants to review inbox, process unread emails, or needs help prioritizing messages. Outputs structured summary with top priorities and suggested next actions.
EvolutionAPI/evo-nexus 211
gog-email-send Send email messages with explicit user confirmation. Requires the exact confirmation string "YES, SEND" before executing send operations. Logs all sends to audit trail. Use ONLY when user explicitly confirms they want to send an email, never auto-invoke. This is a critical write operation requiring human approval.
EvolutionAPI/evo-nexus 211