Topic: claude
14,433 skills in this topic.
-
hr-people-report
Gera relatórios de headcount, attrition, diversidade ou saúde organizacional. Use ao preparar snapshot de headcount para liderança, analisar tendências de turnover por time, preparar métricas de representatividade, ou avaliar span of control e flight risk no time.
EvolutionAPI/evo-nexus 211
-
fin-journal-entry
Prepare journal entries with proper debits, credits, and supporting detail. Use when booking month-end accruals (AP, payroll, prepaid), recording depreciation or amortization, posting revenue recognition or deferred revenue adjustments, or documenting an entry for audit review.
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-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
-
fin-journal-entry-prep
Prepare journal entries with proper debits, credits, and supporting documentation for month-end close. Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry.
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
-
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-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
-
hr-performance-review
Estrutura uma avaliação de desempenho com auto-avaliação, template de gestor e prep para calibração. Use quando a temporada de reviews começa, ao escrever a avaliação de um liderado, ao preparar distribuição de ratings e casos de promoção, ou ao transformar feedback vago em exemplos comportamentais específicos.
EvolutionAPI/evo-nexus 211
-
hr-policy-lookup
EvolutionAPI/evo-nexus 211
-
hr-onboarding
Gera checklist de onboarding e plano da primeira semana para um novo colaborador da Evolution. Use quando alguém tem data de início chegando, ao montar a lista de tarefas pré-start (contas, equipamento, buddy), ao agendar o Dia 1 e a Semana 1, ou ao definir metas de 30/60/90 dias para um novo membro do time.
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-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-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
-
fin-monthly-close-kickoff
Monthly close kickoff — initiates the month-end closing process with a checklist, simplified P&L, pending reconciliations, receivables, payables, and action items for the finance team. Trigger when user says 'monthly close', 'start closing', 'closing kickoff', or on the 1st of each month.
EvolutionAPI/evo-nexus 211
-
fin-reconciliation
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
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
-
gog-tasks
Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.
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-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-sciomc
Scientific method scaffolding — hypothesis → experiment → evidence → conclusion. Use when you need rigorous causal reasoning rather than vibes-based debugging.
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-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