Topic: multi-agent
1,931 skills in this topic.
-
collaborating-with-codex
Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSION_ID.
haoyu-haoyu/Multi-AI-Workflow 235
-
agent-orchestrator
Open-source, pluggable agentic coding orchestrator. Manages durable coding agents (Claude Code, Codex, OpenCode) through a simple interface — spawn agents, track progress, and let feedback loops like PR reviews and CI failures automatically route to the right agents. Use for fixing bugs, building features, working on GitHub issues, checking status, and managing agent sessions.
ComposioHQ/agent-orchestrator 6,182
-
ak-task
Full task lifecycle: create → assign → monitor → review → reject/complete.
Use when asked to "add a feature", "fix a bug", "create a task", "加个功能",
"修个 bug", or "/ak-task <description>".
saltbo/agent-kanban 188
-
ak-plan
Plan and execute a project — either a new version of an existing project, or a
brand new product from scratch. Analyzes gaps, creates board with tasks and
dependencies, assigns to agents. Use when asked to "plan a version", "plan v1.4",
"build a product", "create a project", "规划版本", or "/ak-plan <version> <goals>".
saltbo/agent-kanban 188
-
agent-kanban
CLI reference for agents — how to claim tasks, log progress, submit for review
saltbo/agent-kanban 188
-
rewind
List and restore to a named checkpoint from the current session. Use when the agent has gone off track and you need to recover to a previous good state.
juanandresgs/claude-ctrl 173
-
reckoning
Analyze a project's MASTER_PLAN.md to assess coherence, evolution trajectory, and intent alignment. Modes: default (full analysis), compare (delta between reckonings), operationalize (convert findings to actionable work via /decide), steer (strategic brainstorming grounded in findings).
juanandresgs/claude-ctrl 173
-
prd
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics. Use when describing a problem space, developing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
juanandresgs/claude-ctrl 173
-
observatory
Self-improving flywheel that analyzes agent traces, surfaces improvement signals, and proposes targeted system enhancements.
juanandresgs/claude-ctrl 173
-
diagnose
Validate hook integrity, state file consistency, and system health for the ~/.claude configuration.
juanandresgs/claude-ctrl 173
-
deep-research
Multi-model deep research with comparative assessment (OpenAI + Perplexity + Gemini). Queries 3 deep research providers in parallel and produces a comparative synthesis.
juanandresgs/claude-ctrl 173
-
decide
Generate an interactive decision configurator from research or plan analysis. Presents options as explorable cards with trade-offs, costs, and filtering. Integrates with Planner to collect DEC-ID decisions.
juanandresgs/claude-ctrl 173
-
context-preservation
Generate structured context summaries for session continuity across compaction
juanandresgs/claude-ctrl 173
-
consume-content
Produce a faithful content-snapshot of any source material (article, report, PDF, advisory) with verbatim quotes, structural transparency, and labeled editorial.
juanandresgs/claude-ctrl 173
-
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
-
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-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-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
-
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