Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.
When the user triggers this skill (“squad commands”, “help”, “what can squad do”, etc.):
Category-level menu first. Present category names as an ask_user choice list:
📋 Squad Commands — pick a category:1. Install & Upgrade2. Team Management3. Issues & PRs4. Plugins & Skills5. Model & Cost6. Sessions & State
Drill-down. After selection, show operation titles in that category as a second ask_user list.
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_user is 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)
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.
MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.
Discovery
17 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 6 distinct layouts observed: .copilot/skills/*/SKILL.md, .github/skills/*/SKILL.md, */skill.md, .squad/*/skill.md, skills/*/SKILL.md, */SKILL.md.
Authorship
1 of 17 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.
Duplicates collapsed
3 mirror copies folded into their canonical skill — republished for Squad, Squad Templates. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.
Issue colours
Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
Heading repairs
None needed in this skill: the outline was already valid.
Spec compliance
6 editorial notes across 3 of 17 skills. They are printed in the margin of each skill rather than as errors here.
Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
Signal
Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.
Agent surfaces
The whole issue is available as one markdown document at /microsoft/waza.md, and each skill at its own .md URL.
Publication
Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.