agentleFS
Sign inStart free
YoepanYoepan/TenAgent/.agents/skills/swarm/SKILL.md

swarm

Skill9 starsChanged 25 days agoMITView on GitHub

Autonomous Multi-Brain 10-Agent Swarm: Orchestrates connected AI providers (9Router, Groq, Gemini, DeepSeek, Claude, OpenAI, Ollama) to debate, generate contract-first specifications, and build software collaboratively.

87 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use poteto-help, make-bot-ui and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 27 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 23 projects that use this

  • jaydubya818Skill

    principle-attack-the-premise

    Apply when repeated fixes fail and a shared assumption may be wrong.

    Also in 31 projects that use this

  • jaydubya818Skill

    poteto-mode

    Use when non-trivial work should follow the smallest rigorous Jstack workflow.

    Also in 27 projects that use this

  • +5 more from jaydubya818

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 83 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If 2+ AI models are connected: initiates an adversarial pre-flight debate (council.py) to stress-test race conditions, security, and …

    line 27
  2. Distinctive:

    Run tests and builds through the stream runner:

    line 42

“Common” is measured: kept by at least 6 in 10 of the 83 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

TenAgent Multi-Brain Swarm Orchestrator (v1.0.1)

This skill defines the autonomous multi-brain collaborative execution protocol for the TenAgent Engineering Swarm.

When to Activate

Activate this skill whenever the user instructs the assistant to build, scaffold, develop, or implement a project, system, module, or major feature.

Core Directives

  1. Never Monolithic Generation: The primary AI CLI assistant acts as the Swarm Conductor. Do not generate entire applications from a single uncoordinated prompt context.

  2. Trigger the Multi-Brain Pipeline: The very first action must be running the collaborative swarm pipeline:

    python swarm_pipeline.py "<user_prompt>"

    (or python stream.py swarm "<user_prompt>")

    Execution flow handled by the pipeline:

    • Discovers all active AI keys configured in specs/swarm-config.json (9Router at localhost:20128, Groq, Gemini, DeepSeek, Claude, OpenAI, Ollama).
    • If 2+ AI models are connected: initiates an adversarial pre-flight debate (council.py) to stress-test race conditions, security, and scalability.
    • Maps the 10 engineering roles to the active brains.
    • Writes contract-first deliverables:
      • specs/prd/user-stories.md
      • specs/architecture/adr-001.md
      • specs/database/schema.sql
      • specs/api/openapi.yaml
      • specs/qa/test-matrix.md
      • specs/security/audit-report.md
      • specs/signoff.md
    • Streams real-time thoughts to specs/terminal.log and updates specs/swarm-status.json.
  3. Downstream Implementation & Test Verification:
    • Inspect the generated contracts in specs/.
    • Complete the implementation files in backend/ and frontend/ (or mobile/).
    • Run tests and builds through the stream runner:
      python stream.py run 07_qa "npm test" # or pytest / cargo test

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free