squad-commands

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

96%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.

The content is an exemplar of lean, actionable, well-structured skill writing: terse field-based entries, concrete commands, and a clearly sequenced menu workflow with explicit confirmation and cancel checkpoints. The only gap is that the entire operation catalog is inlined in one file rather than progressively split into reference files.

Dimension	Reasoning	Score
Conciseness	The body is a lean, field-structured catalog (intent/summary/action/command/args/confirm/platform_caveats) with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the anchor-5 example of efficient, competence-assuming content.	5 / 5
Actionability	Each entry gives executable commands (e.g., `squad upgrade`, `squad watch --interval {n}`), exact config paths for file edits (`.squad/config.json → defaultModel`), args with choices and defaults, and confirm flags. It is copy-paste ready and covers the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The menu presentation rules are explicitly sequenced (category menu → drill-down → argument collection → confirmation) with validation checkpoints: a confirmation template, confirm:true flags on destructive ops (Remove Team Member, Remove Plugin, Archive Decisions), and a Back/Cancel feedback loop respected at any point. The Switch State Backend entry even requires showing current vs. new value before confirming, satisfying the destructive-operation feedback-loop requirement.	5 / 5
Progressive Disclosure	The skill is a single, flat, well-organized catalog with clear category headers and no nested references, and no bundle files exist to split out. It lands at anchor 4 rather than 5 because all operations are inlined in one ~290-line file rather than the bulk being split into separate one-level-deep reference files for easy navigation.	4 / 5
	Total	19 / 20 Passed

Description

73%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.

The description clearly communicates the skill's purpose and when to trigger it, using natural user-facing phrases and a distinct Squad-specific niche. Its main weakness is that the "what" stays at a high-level catalog framing rather than enumerating the concrete operations it covers.

Suggestions

Expand the description to name 2-3 concrete operation categories (e.g., upgrade/init, team management, model selection) so the "what" is more specific than "common Squad operations".

Add a few more natural synonyms in the trigger phrasing (e.g., "Squad help", "Squad menu") to push trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	"Categorized catalog of common Squad operations" names the domain and the concrete action of presenting it as an interactive menu, but does not enumerate the multiple specific operations it catalogs. It sits at anchor 3 rather than 4 because it lists only the high-level action (menu presentation) rather than several specific operations.	3 / 5
Completeness	It states both what the skill is (a categorized catalog of Squad operations presented as an interactive menu) and when to use it ("when the user asks for available commands or help"), with concrete trigger phrases. It is not anchor 5 because the "what" stays high-level ("common Squad operations") rather than explicitly enumerating the concrete operations available.	4 / 5
Trigger Term Quality	Natural trigger phrases like "squad commands", "what can squad do", "show me squad options", and "available commands or help" map well to what a user would actually say. It falls short of anchor 5 because it does not exhaustively cover synonyms or file extensions, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Squad operations command catalog) with distinctive triggers tied to Squad-specific phrasing, minimizing the chance of firing for an unrelated skill.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: bradygaster/squad
Path: .squad/skills/squad-commands/SKILL.md
Commit: a0d2563

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.