squad
Skill1.5k starsChanged 5 months agoMITView on GitHub
Squad's command catalog and interactive menu. Invoke via /squad where the host exposes user-invocable skills as commands, or natural language ("squad commands", "what can squad do", "show me squad options"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.
11 other projects use a version of this, 6 of them edited.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- github/squadedited, first seen Nov 8, 2026
- microsoft/github-vteam-industry-demosedited, first seen Oct 25, 2026
- kubefleet-dev/kubefleetedited, first seen Oct 8, 2026
- priyanshijani/data-agentstheir own version, first seen Sep 30, 2026
- microsoft/fsi-banking-payments-dispute-resolution-acceleratoredited, first seen Aug 14, 2026
- inkwell-finance/claude-skillstheir own version, first seen Aug 13, 2026
Who's talking about microsoft/waza
- @matsuu.bsky.social“Go実装なんだな。”Bluesky · May 10, 2026 · 4 likes
- postfinance/devcontainer-features“Create a feature that installs waza (https://github.com/microsoft/waza)”GitHub · Aug 14, 2026 · 1 reactions
- @awakecoding.com“The tessl command-line tool uses server-side evals for the agent skills, so you don't have to figure out …”Bluesky · May 15, 2026 · 1 likes
- Azure/azure-sdk-tools“[Discussion][Benchmark] Benchmark framework selection”GitHub · Mar 30, 2026 · 1 reactions
- neilli-sable/dotfiles“Update dependency github:microsoft/waza to v0.40.0”GitHub · Nov 8, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub and Bluesky (50 times).
On GitHub · 48
- Aug 14, 2026Create a feature that installs waza (https://github.com/microsoft/waza) — postfinance/devcontainer-features1 reaction
- Mar 30, 2026[Discussion][Benchmark] Benchmark framework selection — Azure/azure-sdk-toolssays it tested it1 reaction · 5 comments
- Nov 8, 2026Update dependency github:microsoft/waza to v0.40.0 — neilli-sable/dotfiles0 reactions
- Nov 6, 2026自作 skill に評価(evals)と静的チェックを用意する — oddgai/dotfiles0 reactions
- Nov 2, 2026build(waza): bump pinned waza to 0.39.1 — akunzai/agent-skills0 reactions
43 more on GitHub
- Oct 13, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.9 — y-miyazaki/config0 reactions
- Oct 12, 2026build(waza): bump pinned waza to 0.38.10 — akunzai/agent-skills0 reactions
- Oct 9, 2026Update dependency github:microsoft/waza to v0.38.9 — neilli-sable/dotfiles0 reactions
- Oct 8, 2026[Candidate] microsoft/waza/examples/code-explainer - code-explainer — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 8, 2026[Candidate] microsoft/waza/.copilot/skills/error-recovery - error-recovery — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 8, 2026[Candidate] microsoft/waza/.copilot/skills/agent-collaboration - agent-collaboration — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 8, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.8 — y-miyazaki/config0 reactions
- Oct 5, 2026chore(deps): bump waza to 0.38.9 — akunzai/agent-skills0 reactions · 1 comment
- Oct 4, 2026Clean up the Google Sheet so the graph gets real topics (Category values, duplicates, empty tabs) — Amitro123/knowledgeBase-Agent0 reactions · 3 comments
- Oct 3, 2026Update dependency github:microsoft/waza to v0.38.8 — neilli-sable/dotfiles0 reactions
- Oct 3, 2026chore: update dependency github:microsoft/waza to latest — daaa1k/skills0 reactions · 3 comments
- Sep 3, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.7 — y-miyazaki/config0 reactions
- Aug 23, 2026Update dependency github:microsoft/waza to v0.38.7 — neilli-sable/dotfiles0 reactions
- Aug 22, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.6 — y-miyazaki/config0 reactions
- Aug 19, 2026Update dependency github:microsoft/waza to v0.38.6 — neilli-sable/dotfiles0 reactions
- Aug 17, 2026spec: replace API paired evaluation with Waza (Copilot-native) — akunzai/agent-skills0 reactions
- Aug 14, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.5 — y-miyazaki/config0 reactions
- Aug 12, 2026Update dependency github:microsoft/waza to v0.38.5 — neilli-sable/dotfiles0 reactions
- Aug 3, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.4 — y-miyazaki/config0 reactions
- Jul 24, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.3 — y-miyazaki/config0 reactions
- Jul 15, 2026Review and improve Waza User Guide documentation — microsoft/vscode-chat-customizations-evaluation0 reactions · 1 comment
- Jul 15, 2026feat(battle-testing-a-skill): add 7 adversarial dimensions missing vs superpowers/waza/academic threat models — tvna/gitapexsays it tested it0 reactions
- Jul 13, 2026feat(evals): add waza eval suites for all skills lacking coverage — tvna/gitapex0 reactions
- Jul 13, 2026ci: add waza check as a non-blocking skill report — tvna/gitapex0 reactions
- Jul 8, 2026renovate(mise): Update dependency github:microsoft/waza to v0.38.0 — y-miyazaki/config0 reactions
- Jul 4, 2026skill周り整備 umbrella — happy663/dotfiles0 reactions
- Jun 25, 2026renovate(mise): Update dependency github:microsoft/waza to v0.37.0 — y-miyazaki/config0 reactions
- Jun 3, 2026ci(portable-pr-policy): cache prek, waza, and uv artifacts to speed up the all-files run — tvna/claude-md0 reactions · 1 comment
- Jun 3, 2026ci(portable-pr-policy): prek "against all files" step is slow (~110s cold) -- cache hook envs and waza — tvna/claude-md0 reactions
- Jun 1, 2026Waza user guide: Content feedback — microsoft/vscode-chat-customizations-evaluation0 reactions
- May 31, 2026waza example: — KazuCocoa/specialist-role-cards0 reactions
- May 23, 2026[FEATURE]: Improving the skills for kelp migration and development — BenSchr/kelp-core0 reactions
- May 10, 2026feat(evals): introduce microsoft/waza for skill quality evaluation — iwasa-kosui/kamae-ts0 reactions
- Apr 8, 2026feat(ci): waza-based skill quality checks (Phase 1) — PRD #812 — github/squad0 reactions · 6 comments
- Apr 6, 2026PRD: Skill Security Scanning — Markdown-Aware Scanner for Agent-Executable Instructions — github/squad0 reactions · 3 comments
- Apr 6, 2026feat: Adopt waza ComplianceChecker for skill security scanning — github/squad0 reactions · 1 comment
- Apr 4, 2026PRD: Waza-Based PR Quality Checks for Squad Skills — github/squad0 reactions · 3 comments
- Apr 4, 2026PRD: Waza-Based PR Quality Checks for Squad Skills — diberry/squad0 reactions · 1 comment
- Mar 29, 2026Clean up Copilot CLI session-state after eval runs — ronniegeraghty/hyoka0 reactions · 3 comments
- Mar 27, 2026apr may 2026 — kimtth/azure-openai-llm-notes0 reactions
- Mar 25, 2026Bootstrap azure-net-skills-scenarios for .NET SDK skills measurement using waza — JonathanCrd/azure-net-skills-scenarios0 reactions
- Mar 22, 2026feat: add Waza evaluation suite for skill quality validation — ahmadabdalla/azure-cost-calculator0 reactions · 2 comments
- Mar 5, 2026Skill quality validation against sensei/waza best practices — haileyvictory/azure-building-blocks0 reactions
On Bluesky · 2
- May 10, 2026Go実装なんだな。 — @matsuu.bsky.social4 likes and reposts
- May 15, 2026The tessl command-line tool uses server-side evals for the agent skills, so you don't have to figure out how to do it yourself. I didn't… — @awakecoding.com1 likes and repost
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- github/gh-aw★ 5.6k98% same
- github/squad★ 3.4k99% same
- Azure/fleet★ 22798% same
- kubefleet-dev/kubefleet★ 16498% same
- microsoft/github-vteam-industry-demos★ 299% same
- microsoft/fsi-banking-payments-dispute-resolution-accelerator★ 098% same
Wrote their own version · 5
- rmotgi1227/CCSquad★ 4same name
- inkwell-finance/claude-skills★ 2same name
- buildstr/claude-skill-squad★ 1same name
- berch-t/Kopern-OS★ 0same name
- priyanshijani/data-agents★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .squad/copilot-instructions.mdCopilot instructions
- .squad-templates/copilot-instructions.mdCopilot instructions
- .squad/templates/copilot-instructions.mdCopilot instructions
- squad-commandsSkill
- code-explainerSkill
- evidence-judgeSkill
- agent-collaborationSkill
- azd-publishSkill
- coordinator-init-modeSkill
- coordinator-response-modeSkill
- coordinator-source-of-truthSkill
- cross-squad-communicationSkill
- cross-squadSkill
- error-recoverySkill
- git-workflowSkill
- iterative-retrievalSkill
- reflectSkill
- reviewer-protocolSkill
- secret-handlingSkill
- session-recoverySkill
- squad-conventionsSkill
- squad-helpSkill
- squad-version-checkSkill
- test-disciplineSkill
- tiered-memorySkill
- code-explainerSkill
- waza-interactiveSkill
- wazaSkill
- {skill-name}Skill
- squad-conventionsSkill
- {skill-name}Skill
- {skill-name}Skill
- squad-conventionsSkill
- waza-runnerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 16 are common, 0 are distinctive, and 4 are very specific to this project.
16
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
When the user triggers this skill (via /squad slash command, "squad commands", "help", "what can squad do", etc.):
- Very specific: line 27
Drill-down: After selection, show operation titles in that category as a second ask_user list.
- Common: line 28
Direct match skips the menu: If the user says "how do I upgrade with state backend," match to the specific entry and go straight to …
- Very specific: line 29
Compact fallback: If ask_user is unavailable, render as a markdown table instead.
- Common: line 83
intent: add team member, hire agent, add agent, add developer, recruit
- Common: line 84
summary: Add a new agent to the team roster
- Common: line 86
command: Add Team Member flow (Init Mode / Team Mode)
- Common: line 94
intent: remove team member, fire agent, delete agent, remove developer
- Common: line 95
summary: Remove an agent and delete their charter and history files
- Common: line 97
command: Remove Team Member flow
- Common: line 105
summary: Update a team member's role in team.md and their charter
- Common: line 107
command: Update team.md roster + charter.md
- Common: line 139
summary: Run the Lead triage flow on open GitHub issues
- Common: line 166
intent: start watch, squad watch, monitor issues, watch for issues, auto-triage
- Common: line 167
summary: Start squad watch to continuously poll and triage issues
- Common: line 191
intent: add plugin, install plugin, get plugin from marketplace
- Common: line 192
summary: Add a plugin from the marketplace to this Squad
- Common: line 201
intent: remove plugin, uninstall plugin, delete plugin
- Common: line 202
summary: Remove an installed marketplace plugin
- Very specific: line 255
summary: Remove a model override from config.json (reverts to system default)
“Common” is measured: kept by at least 6 in 10 of the 10 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.
Files
Menu Presentation Rules
Host-dependent invocation: user-invocable: true declares menu intent, not a guarantee
that every host exposes /squad. Use natural-language triggers or the host skill picker/tool
when slash invocation is unavailable. This menu is separate from the Squad coordinator agent.
When the user triggers this skill (via /squad slash command, "squad commands", "help", "what can squad do", etc.):
- Category-level menu first. Present category names as an
ask_userchoice list:📋 Squad Commands — pick a category: 1. Install & Upgrade 2. Team Management 3. Issues & PRs 4. Plugins & Skills 5. Model & Cost 6. Sessions & State - Drill-down. After selection, show operation titles in that category as a second
ask_userlist. - Direct match skips the menu. If the user says "how do I upgrade with state backend," match to the specific entry and go straight to argument collection.
- Compact fallback. If
ask_useris unavailable, render as a markdown table instead. - Back / Cancel. Include "← Back to categories" in sub-menus. Include "Cancel" in confirmation prompts. Respect "never mind" / "cancel" at any point.
Argument collection: For entries with args, iterate the list sequentially. Use ask_user with choices when choices is provided; free-text prompt otherwise. If the user says "just do it" or "defaults are fine," skip remaining args and use their defaults.
Confirmation template:
⚠️ This will {action-description}.
{what will change}
Proceed? (yes / no)Install & Upgrade
Upgrade Squad CLI
- intent: upgrade squad, update squad, install latest version, get new version
- summary: Upgrade Squad CLI to the latest version for your channel
- action: shell
- command: squad upgrade
- args:
state-backend: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
- confirm: false
- platform_caveats: Requires terminal. In VS Code, open the integrated terminal and run the command directly.
Initialize Squad
- intent: set up squad, initialize squad, create team, start squad in this project
- summary: Scaffold Squad in the current directory (idempotent)
- action: shell
- command: squad init
- args: (none)
- confirm: false
- platform_caveats: Requires terminal. Recommend a standalone terminal for best results.
Switch State Backend
- intent: switch state backend, change state storage, use git-notes, use orphan branch
- summary: Change where Squad stores mutable state (config.json)
- action: file-edit
- command: .squad/config.json → stateBackend
- args:
stateBackend: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
- confirm: true
- platform_caveats: May require migration if switching away from worktree. Show current value and new value before confirming.
Team Management
Add Team Member
- intent: add team member, hire agent, add agent, add developer, recruit
- summary: Add a new agent to the team roster
- action: coordinator
- command: Add Team Member flow (Init Mode / Team Mode)
- args:
role: What role should this agent fill? (e.g., Frontend Dev, Backend Dev, QA Engineer)name: Preferred name or casting universe? | default: (auto-cast from active universe)
- confirm: false
Remove Team Member
- intent: remove team member, fire agent, delete agent, remove developer
- summary: Remove an agent and delete their charter and history files
- action: coordinator
- command: Remove Team Member flow
- args:
member: Which team member to remove? (name or role)
- confirm: true
Reassign Roles
- intent: reassign role, change role, swap roles, update team member role
- summary: Update a team member's role in team.md and their charter
- action: coordinator
- command: Update team.md roster + charter.md
- args:
member: Which team member?newRole: New role?
- confirm: false
Show Roster
- intent: show roster, who is on the team, list team members, show team, capability profile
- summary: Display the current team roster and capability profile
- action: coordinator
- command: Direct Mode — read team.md, answer
- args: (none)
- confirm: false
Issues & PRs
Connect GitHub Repo
- intent: connect github, enable issues, set up issues, link repository, github issues mode
- summary: Connect this project to GitHub Issues via gh auth
- action: coordinator
- command: GitHub Issues Mode (connection flow)
- args: (none)
- confirm: false
- platform_caveats: Requires
gh auth loginto have been run in the terminal.
Triage Issues
- intent: triage issues, review issues, assign issues, label issues
- summary: Run the Lead triage flow on open GitHub issues
- action: coordinator
- command: GitHub Issues Mode → Lead triage
- args: (none)
- confirm: false
Activate Ralph
- intent: activate ralph, start ralph, ralph go, start work monitor, start auto-work
- summary: Activate Ralph — Work Monitor — to pick up and run queued issues
- action: coordinator
- command: Ralph — Work Monitor triggers
- args: (none)
- confirm: false
Set Ralph Polling Interval
- intent: set ralph interval, change ralph timing, how often does ralph check, ralph every N minutes
- summary: Tell Ralph how frequently to poll for new work
- action: coordinator
- command: Ralph trigger: "Ralph, check every N minutes"
- args:
interval: How often should Ralph poll? (in minutes) | default: 10
- confirm: false
Start Squad Watch
- intent: start watch, squad watch, monitor issues, watch for issues, auto-triage
- summary: Start squad watch to continuously poll and triage issues
- action: shell
- command: squad watch
- args:
interval: Poll interval in minutes | default: 10
- confirm: false
- platform_caveats: CLI-only — long-running foreground process. Not viable in VS Code without an integrated terminal. Run:
squad watch --interval {n}in your terminal.
Plugins & Skills
Browse Plugin Marketplace
- intent: browse plugins, explore plugins, what plugins are available, plugin marketplace
- summary: Browse available plugins in the Squad marketplace
- action: shell
- command: squad plugin marketplace browse
- args:
name: Plugin name to search for | default: (browse all)
- confirm: false
Add Marketplace Plugin
- intent: add plugin, install plugin, get plugin from marketplace
- summary: Add a plugin from the marketplace to this Squad
- action: shell
- command: squad plugin marketplace add
- args:
plugin: Plugin owner/repo (e.g., owner/plugin-name)
- confirm: false
Remove Marketplace Plugin
- intent: remove plugin, uninstall plugin, delete plugin
- summary: Remove an installed marketplace plugin
- action: shell
- command: squad plugin marketplace remove
- args:
name: Plugin name to remove
- confirm: true
List Marketplace Plugins
- intent: list plugins, show installed plugins, what plugins do I have
- summary: List all plugins registered in this Squad
- action: shell
- command: squad plugin marketplace list
- args: (none)
- confirm: false
List Installed Skills
- intent: list skills, show skills, what skills are installed, skill catalog
- summary: List all skills installed in .squad/skills/ and .github/skills/
- action: coordinator
- command: Direct Mode — list .squad/skills/ and .github/skills/ directories
- args: (none)
- confirm: false
Model & Cost
Set Default Model
- intent: set default model, change model, use gpt, use claude, switch model
- summary: Set the default model for all agents in config.json
- action: file-edit
- command: .squad/config.json → defaultModel
- args:
model: Model name (e.g., gpt-5.6-luna, claude-sonnet-4.5, gpt-5.3-codex)
- confirm: false
Override Per-Agent Model
- intent: set model for agent, agent model override, use different model for one agent
- summary: Set a model override for a specific agent in config.json
- action: file-edit
- command: .squad/config.json → agentModelOverrides.{agentName}
- args:
agent: Agent name (must match name in team.md)model: Model name (e.g., gpt-5.6-luna, claude-sonnet-4.5)
- confirm: false
Clear Model Preference
- intent: clear model, reset model, remove model preference, use default model
- summary: Remove a model override from config.json (reverts to system default)
- action: file-edit
- command: .squad/config.json → remove defaultModel or agentModelOverrides.{agentName}
- args:
scope: Clear default or a specific agent? | choices: {default model, specific agent} | default: default modelagent: Agent name (only if scope = specific agent)
- confirm: false
Sessions & State
Catch-Up Summary
- intent: catch me up, what happened, status, what did the team do, session summary
- summary: Summarize recent agent activity and key decisions
- action: coordinator
- command: Session catch-up flow (lazy scan)
- args: (none)
- confirm: false
Show Recent Decisions
- intent: show decisions, recent decisions, what decisions were made, decision log
- summary: Display recent entries from .squad/decisions.md
- action: coordinator
- command: Direct Mode — read decisions.md, answer
- args: (none)
- confirm: false
Archive Old Decisions
- intent: archive decisions, clean up decisions, move old decisions, compact decisions
- summary: Move old decisions from decisions.md to decisions-archive.md
- action: coordinator
- command: Move entries older than threshold from .squad/decisions.md → .squad/decisions-archive.md
- args:
olderThan: Archive decisions older than how many days? | default: 30
- confirm: true
Summarize Agent History
- intent: summarize history, what did agent do, agent history, compress history
- summary: Spawn an agent to summarize and compress a team member's history file
- action: coordinator
- command: Spawn agent with history.md summarization task
- args:
member: Which team member's history to summarize?
- confirm: false
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
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.

