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
-
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
-
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
-
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
-
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-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
-
data-write-query
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
-
hr-comp-analysis
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
-
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