CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

squad

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured command catalog with clear menu interaction rules, concrete commands, and thoughtful UX details (drill-down, fallbacks, cancellation, confirmations). Its main weaknesses are the fully inlined 24-entry catalog, which defeats progressive disclosure, and the absence of post-execution verification guidance for shell commands.

Suggestions

Move the per-category operation catalogs into reference files (e.g., references/team-management.md) and keep SKILL.md to the menu presentation rules plus category summaries, so intent-matching detail loads only when needed.

Add a brief step for shell-action entries to check command exit status or output and report failures back to the user before proceeding.

State default metadata once (e.g., 'entries default to args: none and confirm: false unless noted') to trim the repeated per-entry fields.

DimensionReasoningScore

Conciseness

The catalog is dense structured metadata with no padding or explanations of concepts Claude already knows ('intent:', 'summary:', 'command:', 'args:' entries). Minor tightening is possible: repeated 'args: (none)' and 'confirm: false' per entry could be stated once as defaults.

4 / 5

Actionability

Mostly executable guidance: concrete shell commands ('squad upgrade', 'squad watch --interval {n}', 'squad plugin marketplace add'), file-edit targets ('.squad/config.json → defaultModel'), and a confirmation template. Coordinator entries like 'Add Team Member flow (Init Mode / Team Mode)' are less concrete, leaving minor gaps.

4 / 5

Workflow Clarity

The menu flow is explicitly sequenced (category menu first → drill-down → direct-match shortcut → ask_user fallback → back/cancel) with confirmation checkpoints on destructive entries ('confirm: true', 'Show current value and new value before confirming'). Minor gap: no guidance on verifying shell command success or handling command failures.

4 / 5

Progressive Disclosure

Sections are well organized by category, but the ~295-line body inlines all 24 per-operation metadata entries with zero external references. The catalog detail is reference-grade material loaded into context on every trigger; splitting it into per-category reference files would let the menu rules stay lean. The under-50-lines exception does not apply.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states what the skill does, how it is invoked (slash command plus natural-language triggers with concrete example phrases), and the categories it covers, all in third person without fluff. The only soft spot is that capability coverage stops at category names rather than concrete operations.

DimensionReasoningScore

Specificity

Names several concrete capabilities — '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' — but lists category names rather than the concrete operations within them, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('Squad's command catalog and interactive menu... Routes to the right squad CLI command or the Squad coordinator agent') and when ('Invoke via /squad... or natural language (...)') with concrete trigger phrases, satisfying the explicit-trigger-guidance requirement.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — '"squad commands", "what can squad do", "show me squad options"' plus the '/squad' slash command — though common variations like 'squad help' or 'squad menu' are missing.

4 / 5

Distinctiveness Conflict Risk

Every trigger term contains 'squad' and the scope is a single tool's command catalog, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

microsoft/waza

Path

.github/skills/squad/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.