CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/squad-commands/SKILL.md
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.

The content is a well-organized, actionable command catalog with clear menu-driven workflow rules and confirm/platform-caveat annotations. It is concise and executable; the main gap is progressive disclosure, since everything lives inline with no one-level-deep references despite the catalog size.

DimensionReasoningScore

Conciseness

The body is mostly lean structured catalog entries with commands, args, and confirm flags; it assumes Claude's competence and avoids explaining Squad concepts, with only minor redundancy between the menu rules and per-entry fields.

4 / 5

Actionability

Entries give concrete executable shell commands (squad upgrade, squad init, squad watch --interval {n}) and precise config-edit targets, with minor gaps where coordinator-driven flows are named but their exact invocation is abstract.

4 / 5

Workflow Clarity

Menu presentation is clearly sequenced (category menu -> drill-down -> argument collection -> confirmation) with back/cancel and fallback handling; destructive/batch entries carry confirm flags and platform caveats, though explicit validate-then-retry feedback loops are not spelled out for the few mutating operations.

4 / 5

Progressive Disclosure

The body is well-sectioned by category but is a single self-contained catalog with no external references or bundle files to split detail into; for a catalog of this size some of the per-entry detail could be offloaded, so structure is adequate rather than optimally layered.

3 / 5

Total

15

/

20

Passed

Description

70%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 is clear, third-person, and provides an explicit use-when clause with natural trigger terms. Its main weakness is specificity: it describes the catalog/menu mechanism rather than enumerating the concrete operations it contains.

Suggestions

Name 2-3 concrete operation categories (e.g., install/upgrade, team management, issues & PRs) in the description so the capability set is explicit rather than implied.

Add the natural phrase 'help' as an explicit trigger in the description since the body already treats it as a primary trigger.

DimensionReasoningScore

Specificity

It names the domain ('Categorized catalog of common Squad operations') and one concrete action ('presents it as an interactive menu'), but does not enumerate the actual operations it catalogs, so coverage is not comprehensive.

3 / 5

Completeness

It states a clear 'what' (categorized catalog of operations presented as an interactive menu) and an explicit 'when' ('when the user asks for available commands or help'), though the 'when' leans on a single scenario and could be more explicit about the menu-driven help context.

4 / 5

Trigger Term Quality

The triggers list and the inline trigger phrases ('squad commands', 'what can squad do', 'show me squad options', 'slash commands') are natural phrases a user would say, with good synonym coverage; a few common variations (e.g. 'help') are referenced in the body but only weakly surfaced in the description.

4 / 5

Distinctiveness Conflict Risk

The 'squad commands/help' niche is fairly distinct and tied to specific triggers, with minor overlap risk against a generic Squad help or status skill.

4 / 5

Total

15

/

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.

Validation15 / 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
bradygaster/squad
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.