init-mode

Team initialization flow (Phase 1 proposal + Phase 2 creation)

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/init-mode/SKILL.md

Quality

Content

77%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-sequenced, actionable two-phase orchestration workflow with strong validation checkpoints and an anti-patterns checklist. Its main weakness is a dangling reference to the Casting & Persistent Naming algorithm, which is cited as a core step but not included or clearly linked to a real file.

Suggestions

Inline the Casting & Persistent Naming algorithm or link it to a concrete, existing file (e.g. `[casting-algorithm.md](casting-algorithm.md)`) so step 3 is self-contained.

Verify referenced paths like `.squad/templates/casting/` and `.squad/templates/casting-policy.json` resolve to real bundle files, or mark them as created-on-demand.

Tighten the PII and union merge-driver rationale to one line each to lift conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete commands, file paths, and exact headers, though a few rationale passages (PII explanation, union merge driver mechanics) could be trimmed slightly; it assumes Claude's competence rather than padding.	4 / 5
Actionability	Mostly executable guidance with concrete commands (`git config user.name`), exact `## Members` headers, `.gitattributes` content, and `ask_user` choice examples, but the core Casting & Persistent Naming algorithm in step 3 is only referenced ('see that section') and not present in the file, leaving a key gap.	4 / 5
Workflow Clarity	A clearly sequenced two-phase workflow with explicit checkpoints ('⚠️ STOP. Your response ENDS here'), trigger conditions, and a feedback loop (re-propose on 'add someone/change a role'); file creation is gated on user confirmation, satisfying the destructive-operation validation requirement.	5 / 5
Progressive Disclosure	Section headers (Context, Patterns, Examples, Anti-Patterns) give reasonable structure, but references like 'see that section' for the casting algorithm and `.squad/templates/` are not clearly signaled one-level-deep pointers and no bundle files exist to back them, leaving navigation ambiguous.	3 / 5
	Total	16 / 20 Passed

Description

46%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 states a clear purpose and niche but is terse and lacks explicit 'when to use' trigger guidance and natural user keywords. Adding a 'Use when...' clause with common trigger phrases would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when no team exists yet or the roster is empty and a new squad must be proposed and created.'

Add natural trigger terms users would actually say ('set up a team', 'create a squad', 'initialize the team') instead of 'Phase 1/Phase 2' jargon.

Optionally name one or two more concrete actions (propose roster, confirm with user, scaffold .squad/ structure) to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('Team initialization flow') and two concrete phases ('Phase 1 proposal + Phase 2 creation'), but lists only two actions rather than comprehensive coverage, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	A clear 'what' is present (team initialization with two phases) but there is no 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the missing-trigger-clause guideline.	3 / 5
Trigger Term Quality	Only a couple of generic keywords ('initialization flow') appear and the parenthetical 'Phase 1 proposal + Phase 2 creation' is technical jargon rather than natural user phrasing; common variations like 'set up', 'create', or 'squad' are absent.	2 / 5
Distinctiveness Conflict Risk	'Team initialization flow' occupies a clear, narrow niche unlikely to fire for unrelated skills, with only minor overlap risk against other team/squad-management skills.	4 / 5
	Total	12 / 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: .copilot/skills/init-mode/SKILL.md
Commit: a0d2563

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.