Squad
Squad's command catalog and interactive menu.
Install
npx skills add microsoft/waza --skill squad -g -a claude-code -y- Repository
- microsoft/waza1.5k
- Category
- AI and agents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 2,662 tokens
- Runs scripts
- No, instructions only
What it does
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.
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)
