swarm-status
Inspect a running swarm — show the agent tree, current tools, halts/pauses, and recent task/message activity for the orchestrator's own swarm.
What this skill does
# Swarm Status Quick orchestrator-side inspection of a live swarm. Run this when you want to see what your spawned subagents are doing right now without halting them or opening the aide-web dashboard. ## Steps ### 1. Resolve current session (your own) ```bash ./.aide/bin/aide reflect current-session ``` Use that ID as `<parent>` below — it's the orchestrator session that owns the swarm. ### 2. List agents in this swarm ```bash ./.aide/bin/aide agent list --parent=<parent> --json ``` Returns one record per registered subagent with `parent_session`, `namespace`, `status`, `halt`, `paused`, `deadline`. ### 3. Active tasks for this swarm ```bash ./.aide/bin/aide task list --parent-session=<parent> --json ``` Filters the project-wide task bucket to ones tagged with this swarm's parent. Look for tasks stuck in `claimed` without progress. ### 4. Recent messages ```bash ./.aide/bin/aide message list --parent-session=<parent> ``` Cross-agent comms within this swarm. High-priority messages from the orchestrator are surfaced to subagents on their next tool call by the signals hook. ### 5. Summarise for the user Group by agent. For each, report: - Status (running / paused / halted) - Current tool (read `agent:<id>:currentTool` via `aide state get currentTool --agent=<id>` if you want this) - Any flags (halt with reason, pause) - Open tasks they hold - Deadline if set Example output: ``` Swarm <parent-id-short> — 3 agents agent-auth (running): current: Edit src/auth/handler.ts tasks: 2 in_progress no flags agent-payments (paused): reason: scope drift — investigating tasks: 1 claimed (#42) paused 3m ago agent-docs (halted): reason: repeated rustdoc — see new instinct halted 12m ago ``` ### When to use halts vs. messages - **Halt** if the agent is clearly off-track or burning budget with no progress. The halt blocks tool calls; the model will respond once with the halt reason then stop. - **High-priority message** if you want to redirect without stopping — arrives as `additionalContext` on the next tool call so the model can read it and adjust. Both are sent via `aide` CLI: ```bash ./.aide/bin/aide agent halt <agent-id> --reason="..." ./.aide/bin/aide message send --from=orchestrator --to=<agent-id> \ --priority=high "redirect: focus on auth.ts only" ``` ## Not for This skill is read-only orchestration. Use the `swarm` skill itself to launch new agents or resolve worktrees at the end.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.