CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

squad-help

How to use the Squad coordinator agent and the separate squad menu skill, with host-dependent discovery and slash-command support.

Quality

69%

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 ./.github/skills/squad-help/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable routing guide that clearly separates the coordinator agent, menu skill, and slash-command invocation paths with concrete examples and anti-patterns. Its main weaknesses are mild redundancy in restating the agent/menu distinction and a meta 'discovery provenance' section that could be trimmed or dropped.

DimensionReasoningScore

Conciseness

The agent/menu/slash-command distinction is stated twice (table plus the following prose paragraph 'They are not interchangeable...'), and the 'How this skill was discovered' section carries jargon-heavy provenance text ('not pristine upstream text; preserve its... source-contract regression on upgrade') that adds no execution value — mostly efficient but could be tightened.

3 / 5

Actionability

Provides a concrete task(name=..., agent_type="Squad", prompt=...) template, explicit natural-language trigger lists per path, and the exact 'squad init' shell command with a when-not-to-run caveat; minor gaps remain around host-dependent menu-skill invocation ('skill(squad) when available').

4 / 5

Workflow Clarity

Clear intent-based routing with three labeled paths (A/B/C), each with 'Use this when the user says' triggers, plus a 'What NOT to do' section; no destructive or batch operations so no validation cap applies, but A and B triggers can overlap ('squad help' vs. 'Squad, help me with...').

4 / 5

Progressive Disclosure

Well-organized single file with headed sections, a comparison table, and a clearly signaled one-level-deep 'See also' list; the provenance section is organizationally tangential and the file exceeds the ~50-line simple-skill threshold, keeping it at 'good structure with minor gaps' rather than 5.

4 / 5

Total

15

/

20

Passed

Description

57%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 distinctive and clearly names its niche, but it reads as a structural summary rather than an invocation contract: it lacks explicit trigger guidance ('Use when the user says...') and natural trigger phrases. Adding a 'when' clause with user-sayable phrases would materially improve routing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user says squad, use Squad, set up a squad, or asks about squad commands or the Squad AI team.'

Include natural trigger variations and synonyms (squad help, squad commands, AI team, squad menu) so natural-language matching covers how users actually phrase requests.

Replace the generic 'How to use' framing with concrete actions, e.g. 'Invokes the Squad coordinator agent via task(agent_type="Squad") and distinguishes it from the squad menu skill and host-dependent /squad command.'

DimensionReasoningScore

Specificity

Names the domain ('Squad coordinator agent', 'squad menu skill') and 1-2 concrete aspects ('host-dependent discovery', 'slash-command support'), but 'How to use...' is generic meta-guidance rather than several specific actions, so it sits at anchor 3 rather than 4.

3 / 5

Completeness

The 'what' is clear (using the coordinator agent vs. the separate menu skill), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the distinctive natural keyword 'Squad' and 'slash-command', but omits common variations users would actually say such as 'squad help', 'squad commands', 'set up a squad', or 'AI team', matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Squad' is a specific named framework with a clear niche and distinct triggers; the description is unlikely to fire for unrelated skills, matching the minimal-conflict-risk anchor.

5 / 5

Total

14

/

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-help/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.