Topic: claude-code
35,830 skills in this topic.
-
conductor
Orchestrate parallel agent sessions through a sprint. Coordinates task claiming, dependency resolution, and artifact handoff between independent agents. Triggers on /conductor, /sprint, /parallel.
garagon/nanostack 173
-
webui
Start the Claude Paper web viewer to browse and study papers
alaliqing/claude-paper 173
-
summary
Use this for a quick summary of a research paper's core ideas and key points. Use when you want to quickly understand a paper without deep study materials. Triggers on PDF paths, arXiv URLs, or paper URLs.
alaliqing/claude-paper 173
-
study
Use this skill when the user wants to read, study, analyze, or deeply understand a research paper (PDF).
alaliqing/claude-paper 173
-
data-explore
Perfila e explora um dataset para entender sua forma, qualidade e padrões. Use ao encontrar uma nova tabela ou arquivo, verificar taxas de nulo e distribuições de colunas, identificar problemas de qualidade como duplicatas ou valores suspeitos, ou decidir quais dimensões e métricas analisar. Funciona com tabelas PostgreSQL do stack Evolution (Evo CRM, Evo AI), dados do Stripe, Omie, Licensing, ou arquivos CSV/Excel carregados.
EvolutionAPI/evo-nexus 211
-
data-build-dashboard
Constrói um dashboard HTML interativo com gráficos, filtros e tabelas no tema Evolution (fundo escuro, acento
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
-
cs-kb-article
Redige um artigo para base de conhecimento a partir de um problema resolvido ou pergunta frequente. Use quando a resolução de um ticket vale ser documentada para self-service, a mesma pergunta continua aparecendo, um workaround precisa ser publicado, ou um problema conhecido deve ser comunicado aos clientes. / Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
EvolutionAPI/evo-nexus 211
-
dev-autopilot
Full autonomous execution from idea to working code. Use when user says "autopilot", "autonomous", "build me", "create me", "make me", "full auto" — orchestrates spec → plan → code → QA → validation across the engineering layer agents.
EvolutionAPI/evo-nexus 211
-
data-write-query
EvolutionAPI/evo-nexus 211
-
dev-cancel
Cleanly stop an active engineering layer flow (dev-autopilot, dev-deep-interview, dev-plan) and report what was completed. Use when the user says "cancel", "stop", "abort", "cancelomc", or wants to exit a multi-phase dev workflow.
EvolutionAPI/evo-nexus 211
-
dev-configure-notifications
Set up Telegram, Discord, or Slack webhooks for engineering layer alerts — long-running task completion, build failures, security audit alerts.
EvolutionAPI/evo-nexus 211
-
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
-
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
-
dev-ralplan
Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.
EvolutionAPI/evo-nexus 211
-
dev-ralph
Persistence loop — keep working on a task until it's resolved or until a circuit breaker stops you. Different from /loop (which is time-based) — ralph is iteration-based with state.
EvolutionAPI/evo-nexus 211
-
dev-plan
Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
EvolutionAPI/evo-nexus 211
-
dev-mcp-setup
Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc. Use when adding a new integration that needs MCP-level access.
EvolutionAPI/evo-nexus 211
-
discord-list-channels
List all channels in a Discord guild/server via the Discord API. Use this skill when the user wants to see all channels, find specific channels, or audit server structure.
EvolutionAPI/evo-nexus 211
-
discord-create-channel
Create new channels in Discord guilds/servers via the Discord API. Use this skill when the user wants to create text channels, voice channels, announcement channels, or categories in a Discord server.
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