swarm-loop
Start an orchestrated multi-agent swarm loop
What this skill does
# Swarm Loop Command
Execute the setup script to initialize the swarm loop:
```!
mkdir -p .claude
# Write arguments to a PID-unique file using a quoted heredoc to prevent shell
# expansion of special chars ($, backticks, braces, parens) in user prompts.
# The setup script's --prompt-file flag reads the goal from this file and parses flags from it.
_prompt_file=".claude/swarm-loop.local.prompt.$$.md"
cat <<'__SWARM_PROMPT_EOF__' > "$_prompt_file"
$ARGUMENTS
__SWARM_PROMPT_EOF__
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-swarm-loop.sh" --prompt-file "$_prompt_file"
```
You are now the SWARM LOOP ORCHESTRATOR. Follow the instructions output by the setup script exactly.
Use `--mode deepplan` for multi-agent planning or `--mode async` for background-agent orchestration. See `/swarm-help` for details.
Key things to remember:
- Read the instance state file (path shown in setup output) and the instance log file at the start of each iteration
- The team is persistent — call TeamCreate ONCE at loop start (team_name is in the instance state file), do NOT recreate it between iterations
- Use native TaskCreate/TaskUpdate/TaskList for ALL task tracking — there is no tasks[] array in the state file
- Check `teammates_isolation` in state: if "worktree", use `isolation: "worktree"` on every Agent call; if "shared" (default), partition file ownership carefully
- Check `teammates_max_count` in state: do not spawn more than this many teammates at once
- Use TaskCreate with blockedBy dependencies to model the work graph; spawn teammates via Agent tool into the persistent team
- Each iteration follows the 7-step cycle: ASSESS → PLAN → EXECUTE → MONITOR → VERIFY → PERSIST → SIGNAL
- In MONITOR: persist each teammate's result to the instance log file and update last_updated in state IMMEDIATELY on receipt — do not defer to PERSIST (microcompact risk). Progress tracking to progress.jsonl is handled automatically by the TaskCompleted gate hook.
- In SIGNAL: if compact_on_iteration is enabled, run /compact BEFORE writing the sentinel
- Write the instance sentinel file (empty content) to signal the stop hook to start the next iteration
- Do NOT call TeamDelete — only /cancel-swarm calls TeamDelete; normal loop completion shuts down teammates but leaves the team intact
- Configure loop settings (compact mode, classifier, notifications, etc.) via /swarm-settings
CRITICAL: If a completion promise is set, you may ONLY output it when the statement is completely and unequivocally TRUE. Do not output false promises to escape the loop.
NOTE: Safe mode (default: true) enables auto-approval for file edits and injects safety context into teammates. Use `--safe-mode false` for supervised sessions where you want manual approval for all operations.
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.