Agent skill

Swarma

by glitch-rabin in glitch-rabin/swarma

Agent teams that run growth experiments and build their own playbook.

MITAuto-check: notesProduct & Project Management

Install Swarma

skills CLI
$ npx skills add glitch-rabin/swarma --skill swarma -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install glitch-rabin/swarma swarma --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
swarma
GitHub stars
173
Token cost
~4.4k tokens
SKILL.md length
1,328 words
Files
423
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Agent teams that run growth experiments and build their own playbook.

  • Works in 5 steps: Understand the goal → Install → Generate the team → …
  • Tasks that involve Product metrics
  • SKILL.md covers When to Use This Skill, Quick Reference, The GROWS Loop (Core Concept) and Setup Guide, plus 4 more sections
  • Calls pip, git and python; needs OPENROUTER_API_KEY

What it does

Swarma is an agent skill from glitch-rabin/swarma. Agent teams that run growth experiments and build their own playbook. GROWS loop: generate hypothesis, run experiment, observe signal, weigh verdict, stack playbook. 18 pre-built squads covering the full AARRR funnel. Your agents stop guessing and start learning.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 425 other files (for example `CONTRIBUTING.md` and `README.md`). Compatibility notes: Python 3.11+, pip, terminal access

It sits in Product & Project Management, covering Product metrics. The repository describes itself as: experiment loop for ai agents and swarms. The licence is MIT.

When your agent uses it

  • Tasks that involve Product metrics

Example prompts

  • “/swarma”

Requirements

  • Python 3
  • A credential in OPENROUTER_API_KEY
  • Compatibility (from SKILL.md): Python 3.11+, pip, terminal access

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand the goal
  2. Install
  3. Generate the team
  4. Run the first cycle
  5. Run more cycles and review

What it can do on your machine

Read from SKILL.md and the folder at commit 4f62366. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip
    • git
    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • openrouter.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENROUTER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Python 3.11+, pip, terminal access

    From compatibility in the SKILL.md frontmatter.

Context cost

Swarma loads about 4.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 1,328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:145
    be in the MCP `env` block. The instance `.env` is not inherited by subprocesses.
  • NoteMentions a .env fileSKILL.md:202
    k-or-..." >> ~/.swarma/instances/default/.env
  • NoteMentions a .env fileSKILL.md:211
    8181/mcp" >> ~/.swarma/instances/default/.env
  • NoteMentions a .env fileSKILL.md:504
    Y` | Add to `~/.swarma/instances/default/.env` |
  • NoteMentions a .env fileSKILL.md:505
    CP subprocess can't find key | Instance `.env` not inherited | Pass key in MCP config `env` block |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from glitch-rabin/swarma at commit 4f62366, republished under its MIT licence (© glitch-rabin). 1,328 words, ~4,408 tokens.

Download SKILL.mdSave it as .claude/skills/swarma/SKILL.md (or your agent's skills folder). This skill also uses 422 other files; get the full folder from GitHub.
name
swarma
description
Agent teams that run growth experiments and build their own playbook. GROWS loop: generate hypothesis, run experiment, observe signal, weigh verdict, stack playbook. 18 pre-built squads covering the full AARRR funnel. Your agents stop guessing and start learning.
compatibility
Python 3.11+, pip, terminal access
version
0.2.0
license
MIT
metadata.repository
https://github.com/glitch-rabin/swarma
metadata.website
https://swarma.dev
metadata.hook
a swarm runs 50 experiments while a human team runs 2
metadata.keywords
growth experiments, A/B testing, agent teams, swarm intelligence, AARRR funnel, playbook, learning agents, experiment loop, strategy evolution, self-improving

swarma -- growth experiment loop for agent teams

When to Use This Skill

Use swarma when the user wants to:

  • Run growth experiments (hooks, landing pages, outreach, pricing, activation, retention)
  • Build agent teams that learn and improve through A/B testing, not just execute once
  • Get a validated playbook of what actually works for their specific audience/product
  • Test ideas at scale (50+ experiments/week instead of 2-5)
  • Replace "we tried that, it didn't work" with logged, analyzed, searchable experiment data

Trigger phrases: "test what works", "optimize my funnel", "find the best hooks", "run experiments", "A/B test", "what's working", "build a playbook", "growth experiments", "improve conversion"

Do NOT use when: user wants workflow automation (use n8n/Make), conversation memory (use honcho), or one-shot agent pipelines (use CrewAI/AutoGen). swarma is specifically for experiment loops that improve over time.


Quick Reference

Commands at a Glance
CommandWhat it doesWhen to use
swarma initCreate instance + starter teamFirst-time setup
swarma cycle <team>Run one experiment cycleTesting, manual runs
swarma cycle <team> --topic "..."Run cycle with a specific topicAd-hoc experiments
swarma team create <name> --from-goal "..."Generate team from a goalStarting a new experiment area
swarma team show <name>Inspect a team's configReviewing what was generated
swarma team listShow all teamsOverview
swarma statusCosts, recent runs, experimentsHealth check
swarma metric log <team> <agent> <value>Log external metricFeeding real-world data
swarma metric import <team> <csv>Bulk import metricsBatch data ingestion
swarma metric show <team>View logged metricsReviewing performance
swarma serve --port 8282Start REST APIExternal integrations
swarma serve --mcpStart MCP serverClaude Code / Hermes integration
swarma runStart scheduled engineContinuous operation
swarma expert listBrowse reasoning lensesExploring expert frameworks
Decision: Which Squad Template?
User wants to improve...Use this squadAARRR stage
Opening lines / hookshook-labAcquisition
Landing page copylanding-labAcquisition
SEO rankingsseo-engineAcquisition
Cold outreach response ratescold-outboundAcquisition
Multi-platform contentchannel-mixAcquisition
Signup-to-value onboardingactivation-flowActivation
Pricing and packagingpricing-labRevenue
Churn and retentionretention-squadRetention
Viral loops and referralsreferral-engineReferral
Market positioningcompetitive-intel--
Short-form video pipelinefaceless-factoryAcquisition
Ad creative testingad-creative-labAcquisition
UGC content simulationugc-factoryAcquisition
Programmatic SEOprogrammatic-seoAcquisition
Newsletter growthnewsletter-engineRetention
Paid + organic loopsacquisition-squadAcquisition
Community-led growthcommunity-engineRetention
AI commerce optimizationagentic-storefrontRevenue
Decision: Generate vs Template?
SituationApproach
User has a specific, well-defined goalswarma team create --from-goal (let AI design the team)
Goal matches an existing squad templateCopy template, then customize
User wants to experiment broadlyStart with hook-lab (most general)
User doesn't know where to startAsk about their funnel bottleneck, then pick

The GROWS Loop (Core Concept)

Every experiment cycle follows five steps:

  Generate       Run         Observe       Weigh        Stack
 hypothesis --> experiment --> signal --> verdict --> playbook
     ^                                                  |
     └──────────────────────────────────────────────────┘
StepWhat happensWhere in code
G -- GenerateAgent reads strategy.md, proposes a hypothesiscore/cycle.py
R -- RunAgent executes with hypothesis active, produces outputflow/executor.py
O -- ObserveSeparate cheap LLM scores output (1-10, forced decimals)core/agent.py
W -- WeighAfter 5 cycles, compare average vs baseline. >20% = keep/discardcore/experiment.py
S -- StackValidated patterns written to strategy.md + playbookcore/agent.py

Key numbers:

  • Verdict threshold: 20% improvement to keep, 20% decline to discard
  • Default min_sample_size: 5 cycles before verdict
  • Scoring: 1-10 scale with forced decimals (7.3, not 7)

Setup Guide

Platform: Claude Code / Claude Desktop
bash
pip install swarma
swarma init

Add to .mcp.json:

json
{
  "mcpServers": {
    "swarma": {
      "command": "swarma",
      "args": ["serve", "--mcp"],
      "env": { "OPENROUTER_API_KEY": "sk-or-..." }
    }
  }
}

Important: OPENROUTER_API_KEY must be in the MCP env block. The instance .env is not inherited by subprocesses.

Platform: Hermes (via terminal)

Hermes has terminal access -- it can run swarma CLI commands directly. No MCP required.

bash
pip install swarma
swarma init

Then tell Hermes: "run swarma cycle hook-lab --topic 'AI agents are overhyped'"

Hermes reads terminal output and acts on results. For structured access, add MCP:

yaml
# hermes config.yaml
mcp_servers:
  swarma:
    transport: stdio
    command: swarma
    args: ["serve", "--mcp"]
    env:
      OPENROUTER_API_KEY: "sk-or-..."
Platform: OpenClaw
bash
pip install swarma
swarma init

Configure as MCP tool or use terminal access depending on your OpenClaw setup.

Platform: CLI (standalone)
bash
pip install swarma
swarma init                                        # creates instance + starter team
swarma cycle starter --topic "why do startups fail?"   # run one cycle
swarma status                                      # check costs, runs, experiments
From source
bash
git clone https://github.com/glitch-rabin/swarma.git
cd swarma && pip install -e .
swarma init
Environment setup

After swarma init, add your API key:

bash
echo "OPENROUTER_API_KEY=sk-or-..." >> ~/.swarma/instances/default/.env

Get a key at openrouter.ai/keys.

Optional (for cross-team knowledge):

bash
# Only needed when running 3+ teams
echo "QMD_ENDPOINT=http://localhost:8181/mcp" >> ~/.swarma/instances/default/.env

Onboarding Flow

When a user wants to set up swarma, follow this sequence. The team generator is the fastest path -- don't make users configure agents manually.

Step 1: Understand the goal

Ask:

  • "What do you want to improve?" (conversion, engagement, outreach response rate, SEO rankings, etc.)
  • "Who is your audience?" (B2B SaaS users, crypto community, enterprise buyers, etc.)
  • "What does success look like?" (more signups, higher CTR, better reply rates, etc.)
Step 2: Install
bash
pip install swarma
swarma init --yes
Step 3: Generate the team

This is the key step. Use the team generator instead of picking templates.

bash
swarma team create growth-lab \
  --from-goal "optimize landing page conversion for our B2B SaaS" \
  --context "developer tools company, 500 free users, 2% conversion to paid" \
  --budget 30

The generator:

  1. Designs the team (2-5 agents with specific roles)
  2. Picks models that fit each role
  3. Writes agent instructions and experiment patterns
  4. Creates a first experiment hypothesis ready to run

Review what it generated:

bash
swarma team show growth-lab
Step 4: Run the first cycle
bash
swarma cycle growth-lab

Expected output:

Running cycle: growth-lab
  flow: researcher -> copywriter -> judge
  agents: ['researcher', 'copywriter', 'judge']

                              Cycle: growth-lab
  Agent      Model              Cost       Output Preview
  researcher sonar-pro          $0.000384  **Topic:** 52% of executives...
  copywriter qwen3.5-plus-02-15 $0.000746  [A] We sent 4,382 cold emails...
  judge      mistral-nemo       $0.000416  **Hook Variations:** A: "Did...

  duration: 43.9s | total cost: $0.001546 | agents: 3
Step 5: Run more cycles and review
bash
swarma cycle growth-lab                    # run another cycle
swarma cycle growth-lab --topic "specific angle"  # with a topic
swarma status                              # check progress

After 5 cycles, the experiment engine issues its first verdict. The strategy file evolves automatically.


Show full SKILL.md (530 more words)Show less

Day-to-Day Usage

Running experiments
bash
# Single cycle
swarma cycle hook-lab

# With a specific topic
swarma cycle hook-lab --topic "AI agents are commoditizing"

# Continuous (teams with cron schedules run automatically)
swarma run

# Continuous with API server
swarma run --port 8282
Feeding real metrics

LLM self-eval is a starting proxy. For production, feed back real-world signals:

bash
# Log a single metric
swarma metric log hook-lab copywriter 4.2 --metric ctr_pct

# Attach to a specific experiment
swarma metric log hook-lab copywriter 127 --metric impressions --exp 3

# Add a note
swarma metric log hook-lab copywriter 5.1 --metric ctr_pct --note "from linkedin analytics"

# Bulk import from CSV
swarma metric import hook-lab metrics.csv

# View logged metrics
swarma metric show hook-lab

CSV format: agent,value,metric_name,note

csv
copywriter,4.2,ctr_pct,week 1
copywriter,5.1,ctr_pct,week 2
researcher,7.8,relevance_score,
Using squad templates
bash
# Copy a template to your instance
cp -r "$(python -c "import swarma; print(swarma.__path__[0])")/examples/hook-lab" \
  ~/.swarma/instances/default/teams/hook-lab

# Or if you cloned the repo
cp -r examples/hook-lab ~/.swarma/instances/default/teams/hook-lab

# Run it
swarma cycle hook-lab --topic "why most startups fail"
Checking status
bash
swarma status

Shows: all teams, recent runs, costs (today + this month), pending plans, queue stats.


MCP Tools Reference

When connected via MCP, these 16 tools are available:

ToolDescriptionParameters
swarma_healthCheck if swarma is running--
swarma_list_teamsList all configured teams--
swarma_get_teamGet team details (agents, flow, schedule)team_id
swarma_list_agentsList agents in a teamteam_id
swarma_run_agentRun a single agent with optional contextteam_id, agent_id, context?
swarma_run_cycleRun a full cycle for a teamteam_id, topic?
swarma_statusInstance status (costs, runs, experiments)--
swarma_costsCost breakdown (today, this month)--
swarma_list_plansShow pending experiment plansteam_id?
swarma_approve_planApprove a pending experiment planplan_id
swarma_reject_planReject a pending planplan_id, reason?
swarma_get_outputsRecent outputs from agentsteam_id?, agent_id?, limit?
swarma_list_toolsList available agent tools--
swarma_list_expertsBrowse expert reasoning lenses--
swarma_get_expertGet expert details by IDexpert_id
swarma_generate_teamGenerate a new team from a goalname, goal, context?, budget?
Common MCP Workflows

"What's been happening?"

  1. swarma_status -- overview
  2. swarma_get_outputs -- recent agent outputs
  3. swarma_list_plans -- pending experiments

"Run an experiment"

  1. swarma_run_cycle with team_id and optional topic
  2. swarma_get_outputs to review results

"Start a new experiment area"

  1. swarma_generate_team with goal and context
  2. swarma_get_team to review what was generated
  3. swarma_run_cycle to kick it off

"What's working?"

  1. swarma_get_outputs for recent results
  2. Read the team's strategy.md for validated patterns

Team Configuration Reference

A team is a folder. No code required.

teams/my-squad/
├── team.yaml          # goal, flow, schedule, budget
├── program.md         # team context and constraints
└── agents/
    ├── researcher.yaml
    ├── writer.yaml
    └── strategy.md    # pre-seeded growth knowledge (evolves automatically)
team.yaml
yaml
name: my-squad
goal: find what works.
flow: "researcher -> writer"        # sequential
# flow: "researcher -> [writer, analyst]"  # parallel
schedule: "0 8 * * 1-5"            # optional: weekdays at 8am
budget: 30                          # optional: monthly budget in $
agent.yaml
yaml
id: writer
name: Writer
instructions: |
  turn research into a post. max 200 words.
  hook in the first line. practitioner voice.
model: qwen/qwen3.5-plus-02-15     # optional: override default routing
metric:
  name: content_quality
  target: 8.0
experiment_config:
  min_sample_size: 5
  auto_propose: true
strategy.md (evolves automatically)

Starts with seed knowledge, grows with every validated experiment:

markdown
### Validated Patterns

**Specificity wins**
- Hooks with specific numbers outperform vague claims by 2-3x on saves
- "47% of startups" > "most startups"

### Anti-patterns (Discarded)
- Generic inspirational openings: -23% vs baseline. Discard.

### Patterns to Test
- [ ] First-person confession vs third-person case study
- [ ] Time-anchored ("In 2024...") vs timeless hooks
Flow DSL
yaml
# Sequential: a runs, output passes to b
flow: "researcher -> writer"

# Parallel: a runs, then b and c run concurrently
flow: "researcher -> [writer, analyst]"

# Mixed: sequential then parallel then sequential
flow: "researcher -> [writer, analyst] -> judge"

Cross-Team Knowledge (QMD)

By default, each team learns individually via its own strategy.md. To share knowledge across teams, wire in QMD:

yaml
# ~/.swarma/instances/default/config.yaml
knowledge:
  engine: qmd
  qmd_endpoint: http://localhost:8181/mcp

With QMD: team A discovers loss framing beats gain framing, team B sees that pattern in its next cycle. Anti-patterns are shared too.

You don't need QMD until running 3+ teams. Most users start without it.


Troubleshooting

ProblemCauseFix
"No API key found"Missing OPENROUTER_API_KEYAdd to ~/.swarma/instances/default/.env
MCP subprocess can't find keyInstance .env not inheritedPass key in MCP config env block
"No teams found"Empty instanceRun swarma init or copy a squad template
Experiments not issuing verdictsNot enough cyclesNeed min_sample_size (default 5) completed cycles
Strategy file not evolvingNo verdict yetRun more cycles, check swarma status
swarma cycle shows $0.000000 costModel returned emptyCheck API key validity, try swarma cycle starter
QMD not connectingQMD not runningStart with qmd serve before swarma
Results.tsv emptyNo cycles completedRun at least one cycle first

Verification

After setup, verify everything works:

bash
# 1. Run a cycle
swarma cycle starter --topic "test run"
# Expected: table showing agent outputs + costs

# 2. Check status
swarma status
# Expected: teams listed, recent run shown, costs displayed

# 3. Check a real squad (if installed)
swarma team show hook-lab
# Expected: team config with agents, flow, metrics

If all three pass, the GROWS loop is operational.


What swarma Is Not

swarma is not...Use this insteadThe difference
memoryhonchoswarma doesn't remember conversations. it runs experiment loops.
workflow automationn8n, Make, Zapierthose connect apps. swarma runs hypotheses and learns from results.
a prompt libraryagency-agentsswarma teaches agents what works through feedback. templates go in, playbooks come out.
agent orchestrationCrewAI, AutoGen, LangGraphthose run pipelines. swarma adds the GROWS loop that makes pipelines improve.
a hosted service--self-hosted. your data stays on your machine.

© glitch-rabin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 422 other files in the repository root of glitch-rabin/swarma.

  • SKILL.md
  • .env.template
  • .gitignore
  • CONTRIBUTING.md
  • LICENSE
  • README.md
  • brand/avatars/analyst.png
  • brand/avatars/branded-test/analyst-hex-spit.png
  • brand/avatars/branded-test/creator-bee.png
  • brand/avatars/branded-test/hermes-badge.png
  • brand/avatars/branded-test/mascot-bee.png
  • brand/avatars/branded-test/mascot-hex-spit.png
  • brand/avatars/branded-test/scanner-hex-spit.png
  • brand/avatars/creator.png
  • brand/avatars/hermes.png
  • brand/avatars/scanner.png
  • brand/avatars/strategist.png
  • brand/avatars/swarma-mascot.png
  • … and 405 more

Open the folder on GitHubat commit 4f62366

Compare with similar skills

Swarma next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Swarma compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Swarma this skillglitch-rabin/swarma173—~4.4kAutomated safety check: NotesMIT
Prdjuanandresgs/claude-ctrl193—~2.9kAutomated safety check: PassNone
AI Product Strategy InterviewerPrepLabsAI/InterviewMentor112—~4.5kAutomated safety check: PassMIT
Investigate MetricPostHog/posthog40k—~1.9kAutomated safety check: PassCustom licence
Weekly Creative Reportreal-simple-labs/parker-brain102—~4.7kAutomated safety check: PassCustom licence
North Starandreaskelm/pm-brain234—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Prd

    juanandresgs/claude-ctrl

    Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.

    193 GitHub stars~2.9k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed
  • AI Product Strategy Interviewer

    PrepLabsAI/InterviewMentor

    A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.

    112 GitHub stars~4.5k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Weekly Creative Report

    real-simple-labs/parker-brain

    Build the brand's weekly creative report, a polished, shareable page an agency can send straight to the brand's CMO and team.

    102 GitHub stars~4.7k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • North Star

    andreaskelm/pm-brain

    Define, sharpen, or audit a North Star metric and its input metrics tree, and decide which product metrics actually matter (leading vs.

    234 GitHub stars~2.5k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Bmad Product Brief

    aj-geddes/claude-code-bmad-skills

    Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method.

    488 GitHub stars~1.7k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes

Questions about Swarma

What does Swarma do?

Agent teams that run growth experiments and build their own playbook. Swarma is an agent skill from glitch-rabin/swarma. Agent teams that run growth experiments and build their own playbook.

When should I use Swarma?

Swarma fits situations like: tasks that involve Product metrics.

How do I install Swarma in Claude Code?

Run `npx skills add glitch-rabin/swarma --skill swarma -a claude-code`. Or copy the skill folder (the glitch-rabin/swarma repository) into .claude/skills/swarma in your project. Claude Code loads it when a task matches its description.

How do I install Swarma in Codex?

Run `npx skills add glitch-rabin/swarma --skill swarma -a codex`. Or copy the skill folder (the glitch-rabin/swarma repository) into .agents/skills/swarma in your project. Codex loads it when a task matches its description.

Can I use Swarma in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glitch-rabin/swarma --skill swarma -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swarma, .gemini/skills/swarma, .github/skills/swarma and .opencode/skills/swarma in your project.

What does Swarma need to run?

Going by SKILL.md and its folder, Swarma needs the command-line tools its instructions call (pip, git and python) and credentials named OPENROUTER_API_KEY. Our summary lists: Python 3; A credential in OPENROUTER_API_KEY. Compatibility (from SKILL.md): Python 3.11+, pip, terminal access.

Does Swarma access the network?

SKILL.md names 1 domain. As links in the text: openrouter.ai. This is read from the text; nothing was executed.

Is Swarma safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Swarma use?

Swarma is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Swarma use?

About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Swarma?

Skills that share tags, products or a category with Swarma: Prd (juanandresgs/claude-ctrl, 193 stars), AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Investigate Metric (PostHog/posthog, 40k stars) and Weekly Creative Report (real-simple-labs/parker-brain, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swarma?

glitch-rabin (a GitHub user) maintains it in glitch-rabin/swarma, which has 173 GitHub stars. The repository was last updated on March 29, 2026.

Source: glitch-rabin/swarma on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.