squad-help

How to actually use Squad — Squad is a custom Copilot agent (invoked via the task tool with agent_type='Squad'), not a skill. This file explains the right invocation paths for setting up a team, listing squad commands, and initializing Squad in a new project.

Quality

83%

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

85%

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

Highly actionable and well-structured routing guidance with clear intent-matched paths and clean navigation, held back only by a few sections of unnecessary provenance detail.

Suggestions

Remove or trim the "How this skill was discovered" section — it explains provenance rather than how to use Squad.

Cut the parenthetical "There's no way to map a skill name to a slash command without a Copilot CLI feature change" since it does not change what Claude should do.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but sections like "How this skill was discovered" and the parenthetical about CLI feature changes add provenance/explanation Claude does not need to act.	2 / 3
Actionability	Provides copy-paste-ready, executable guidance — a concrete task() call with named parameters, the squad init shell command, and explicit natural-language trigger phrases.	3 / 3
Workflow Clarity	The intent-based decision tree ("Pick the path that matches the user's intent" → A/B/C, with A labeled "most common") gives an unambiguous routing sequence, and no destructive/batch operation requires validation here.	3 / 3
Progressive Disclosure	Well-organized into focused sections with a clearly signaled one-level-deep "See also" list pointing to related agent and skill files; no nested reference chains and no bundle files to misroute.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 clear, specific description that names concrete actions and distinct Squad triggers, but it is missing an explicit "Use when..." clause that would push completeness to the top level.

Suggestions

Append an explicit trigger clause such as "Use when the user says 'use squad', 'set up a squad', or asks about squad commands" to reach full completeness.

Lead with the "what" before the meta-explanation that Squad is an agent, so the capability statement lands first.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "setting up a team, listing squad commands, and initializing Squad in a new project" — matching the anchor for naming several specific capabilities rather than vague abstractions.	3 / 3
Completeness	It clearly answers "what" (explains invocation paths for three tasks) but lacks an explicit "Use when..." trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Covers natural terms users would say — "Squad", "team", "squad commands", "initializing Squad" — giving good coverage of the phrases a user would naturally utter when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The Squad agent name is a distinct niche and the description actively disambiguates ("not a skill"), making conflicts with other skills unlikely.	3 / 3
	Total	11 / 12 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-help/SKILL.md
Commit: e23dd92

Reviewed: 1 day 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.