Squadra skill
A skill that turns several Claude Code, Codex and Cursor windows into a team with a coordinator, shared registry and cross-review
- 970 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Agent windows run commands and checks in your repository and Squadra writes them to a shared registry
- Reads Claude Code and Codex session files to count token usage
- Paid store plugins and MCP plugins such as Playwright connect third-party services on your command
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/squadraDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Agent windows run commands and checks in your repository and Squadra writes them to a shared registry
- Reads Claude Code and Codex session files to count token usage
- Paid store plugins and MCP plugins such as Playwright connect third-party services on your command
This is third-party code. Review the repository files before installing.
What it does
Squadra is a skill that lets several coding-agent windows work on one project as a team. One window coordinates, others build, and a window that did not write the code reviews it. Assignments, decisions, executed checks and review reports live in one registry on your computer. Each window can work in its own checkout while writing to the shared record. The coordinator is the Claude window that first applies the skill. It finds the project's Codex, Claude and Cursor windows and introduces itself to each. A task counts as started only after its recipient confirms receiving it. Proof is bound to the exact code: if the code changes after a check, the check and the review stop counting. The package holds a skill with rules for the agents, the `squadra` CLI that records tasks, messages and checks, and a dashboard that shows progress, evidence and questions for you. The dashboard counts token spending per window and model and suggests which window should take the next task, but assigns nothing.
Who it is for. For people who run one job across several Claude Code, Codex and Cursor windows and want to see who does what, what has been checked and what awaits a decision.
Good fit when
- Work has spread over several sessions and you lose track of who owns which task and which code is checked
- Every change must be read by a window that did not write it
- Tasks on a complex job run long and you need a compact packet to resume where you stopped: `squadra context --task ID` prepares it
- Each window works in its own repository checkout and the reports must converge in one record
- You want token spending per window and model plus advice on which window should take the next task
Not a fit when
- You edit code in one window: the skill does not impose its scheme on ordinary changes
- You need fully automatic orchestration with no human: you open the Cursor window yourself and Codex does not coordinate when called first
- You work on Windows: macOS and POSIX are the tested environment, and Windows process control has not been tested
- You need shared cloud storage for a team: the registry lives on your computer and is not sent to the author
Example request
Use squadra for this project with the registry at ~/.local/state/squadra/my-project: find the other windows and introduce yourself to eachLimitations
- Needs Python 3.12 or newer, Git and a browser for the dashboard. Node.js is required for `selftest`. The tested environment is macOS and POSIX.
- Only a Claude window can coordinate. A Codex window called first reports its limits and gives a sentence for a Claude window, since from its sandbox it cannot see the other windows.
- Cursor windows work interactively only. Cursor runs team and user hooks outside the sandbox and they cannot be switched off, so Squadra never launches Cursor itself.
- The plugin does not put the `squadra` command on PATH: agents run `python3 <skill folder>/scripts/squadra.py`. For the `squadra` command use the standalone installer instead of the plugin, not both.
- Some add-ons in the Squadra plugin store are paid or have a trial, for example memoranda. Squadra itself is free under the MIT license.
How to disable. In Claude Code run `/plugin uninstall squadra@squadra`. For a standalone install roll back from the backup folder you gave in `--backup`: the installer keeps your previous skills and launcher. The registry sits in the directory set in SQUADRA_ROOT; delete it by hand when the data is no longer needed.
FAQ
How do I install Squadra in Claude Code?
Run `/plugin marketplace add dagoSte/squadra`, then `/plugin install squadra@squadra` and `/reload-plugins`. For Codex in a terminal: `codex plugin marketplace add dagoSte/squadra` and `codex plugin add squadra@squadra`. The easiest way is to paste the sentence with the SETUP.md link to an agent.
How does the plugin differ from the standalone installer?
The plugin brings the skill, scripts, references and dashboard but does not put the `squadra` command on PATH. The standalone `scripts/install.py` installs the command, backs up your setup and lets you roll back. Use one of them so the skill is not registered twice.
Who coordinates a Squadra team?
The Claude window that first applied the skill. It takes a census of the project's Codex, Claude and Cursor windows, introduces itself to each and assigns tasks.
How do I open the Squadra dashboard?
Run `squadra dash --root /path/to/registry --open`. The dashboard listens on 127.0.0.1 and brings together windows, tasks and token usage. With a plugin install ask the agent to open it.
Does Squadra read the text of my conversations?
For token usage it reads the session files Claude Code and Codex keep, but stores only token counts, model, time and message identifiers. Conversation text is never stored, shown or sent. The registry is not uploaded to the author automatically.
Discussion
No questions or reviews yet.
Related
SkillsA desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
31 skills for Claude Code and Codex: cross-vendor review, task handoff on low quota, a morning brief and a nightly retrospective
A skill with 25 commands to audit and improve the prompts, tools and agent designs of a project in Cursor, Claude Code and Codex
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
Skills for cross-provider work between Claude Code and Codex: one agent drafts the plan, the other reviews it, then a build and an independent code inspection f
A skill plus hooks that keep a coding agent on task and cut speculative defenses, unread checksums and scope creep
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Squadra (this entry) | no | 970 | ||
| CLI Agent Orchestrator | no | 1,489 | a CLI with a supervisor that hands tasks to worker agents, while here you run the windows and they sync through a registry | |
| MCP Agent Mail | no | API key | 2,228 | a mail layer for messages between agents without a task registry with checks and review |
README in short
Installation comes down to one sentence for an agent with a link to SETUP.md, and an 80-second video shows the dashboard at work. Besides the skill, the project runs its own plugin store and publishes security-scan results.
README badge
Original SKILL.md
--- name: squadra description: Coordinates work entrusted to several Codex, Claude, Cursor or mixed windows, with tasks, acknowledgements, proofs, a non-author reviewer and a persistent registry. Includes squadra dash to view the activity and squadra selftest to test the protocol. Use when the owner asks for a squad (squadra), a coordinator/builders/reviewer, resuming a squad or its dashboard; it does not impose this scheme on ordinary changes in a single window. compatibility: Runs locally with Python 3.12+; the dashboard listens on 127.0.0.1. Network access occurs through optional plugins and MCP services you install and configure, coding clients and tools you authorize, and external links you open. Squadra does not automatically upload its registry to its author. --- # Squadra 3 This file is written in English for agents; always answer the user in the user's language. ## Rule 0 — who coordinates, who answers **The coordinator is a Claude window.** The first Claude window that invokes this skill for a piece of work takes the coordinator role. **Before assigning or starting work, it takes a census of every Codex, Claude and Cursor window of the project and introduces itself to each one.** This is an operating rule for the agent, not an automatic election run by any CLI command.