Skip to content

kbarbel640-del/skills / skills/0xnagato/antigravity-swarm

antigravity-swarm

Verified

Deploys autonomous sub-agents to perform tasks in the Antigravity IDE. Supports both manual dispatch and dynamic "Auto-Hiring" of agent teams.

Antigravity Subagents Skill

This skill allows you to dispatch autonomous sub-agents to perform tasks. It features a Manager layer (planner.py) that can automatically design a team of agents for a complex mission, and an Orchestrator (orchestrator.py) to run them visually. Both scripts include a Plan Mode (confirmation step) by default to prevent accidental usage limits consumption.

[!WARNING] Do NOT modify files in this directory while the Orchestrator is running. The system actively reads and writes to task_plan.md, findings.md, and subagents.yaml. Manual edits during execution may cause race conditions or inconsistent agent behavior.

🛠 Tools

dispatch_subagent

Runs a sub-agent with a specific task.

Usage: Use this when you have a parallelizable task or need to offload a specific job (e.g., "Write a test file", "Analyze this directory").

Arguments:

  • task: A clear, self-contained description of what the sub-agent should do.

Implementation Details: The sub-agent is powered by the gemini CLI. A Python wrapper intercepts specific output patterns to perform file system operations and command executions.

Syntax used by Sub-Agent (Handled Automatically):

  • <<WRITE_FILE path="...">>...<<END_WRITE>>
  • <<RUN_COMMAND>>...<<END_COMMAND>>

run_mission (Dynamic Orchestration)

Analyzes a high-level goal, hires a custom team of sub-agents, and creates a configuration for them.

Usage: Use this for complex, multi-step projects where you don't want to manually define every sub-agent.

Arguments:

  • mission: A description of the overall project (e.g., "Create a Snake game in Python").

How it works:

  1. Calls scripts/planner.py to generate subagents.yaml. (Will prompt for confirmation unless --yes is used).
  2. (Optional) You can then run scripts/orchestrator.py to execute the team. (Will prompt for confirmation unless --yes is used).

Usage Modes

Mode 1: CLI User (Terminal Visualization)

Run the Python orchestrator in your terminal to see a TUI.

python scripts/orchestrator.py

Mode 2: IDE Agent (Chat Visualization)

As an Agent, you act as the Orchestrator.

  1. Spawn: Use run_command to launch sub-agents in the background. Use --format json for logs.
    python scripts/dispatch_agent.py "Task A" --log-file logs/agent_a.json --format json &
    python scripts/dispatch_agent.py "Task B" --log-file logs/agent_b.json --format json &
    
  2. Monitor: Poll the JSON log files to check for {"type": "status", "content": "completed"}.
  3. Visualize: Render a Markdown dashboard in your chat response to the user.

🚀 Examples

1. Manual Dispatch (Single Agent)

run_command("python3 scripts/dispatch_agent.py 'Create a file named hello.py that prints Hello World'")

2. Auto-Hire a Team (Mission Mode)

# 1. Generate the team
run_command("python3 scripts/planner.py 'Create a fully functional Todo List app in HTML/JS'")

# 2. Run the team
run_command("python3 scripts/orchestrator.py")

[!WARNING] You must use gemini-3-pro or gemini-3-flash. Deprecated or older models may not support the file shim protocol correctly.

❓ FAQ & Philosophy

Why Sub-agents?

  1. Context Isolation: Prevents "Context Contamination." A UI Specialist doesn't need to see specific Database Migration code. Separation ensures higher accuracy.
  2. Scalability: While loop-based agents process sequentially, Sub-agents are architected to run in parallel threads.
  3. Fault Tolerance: If one sub-agent fails (e.g., Syntax Error), it doesn't crash the entire mission; the Orchestrator can retry just that agent.

Is this truly parallel?

Yes. orchestrator.py uses Python's threading.Thread to spawn separate OS processes for each agent. Note: You may perceive sequential behavior if the underlying gemini CLI tool enforces a global lock or if you hit API Rate Limits.

Planning with Files (Manus Protocol)

This skill adheres to the "Manus" state management philosophy. All agents operate on a shared set of "Memory Files" in the root of the workspace:

  1. task_plan.md: The Source of Truth for the mission checklist.
  2. findings.md: A shared scratchpad for discoveries and research.
  3. progress.md: A log of completed steps and current status.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall