coordinator-init-mode

The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.

Quality

90%

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

The canonical home for this skill is coordinator-init-mode in github/gh-aw

Quality

Content

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

A highly actionable, well-sequenced protocol body: every step has concrete commands, file names, or exact output shapes, and the user-confirmation gate is unmissable. The residual slack is minor repetition in the casting exemptions and seeding details that sit inline rather than in a reference file.

Suggestions

Collapse the four 'exempt from casting' bullets (Scribe, Ralph, Rai, Fact Checker) into a single line such as 'Scribe, Ralph, Rai, and Fact Checker keep their fixed names — exempt from casting' to cut repetition.

State the confirmation-gate rule once (either the header blockquote or the Phase-1 STOP marker) rather than twice, keeping the STOP as the single authoritative checkpoint.

Move the per-agent seeding details (Rai/Fact Checker charter and policy template names) into a short seeding reference under a templates path so Phase 2 step 6 stays a compact checklist.

Dimension	Reasoning	Score
Conciseness	The body is dense and instructional with no explanation of known concepts, but the four repeated 'exempt from casting' bullets (Scribe/Ralph/Rai/Fact Checker) and the confirmation-gate warning appearing in both the header blockquote and the Phase-1 STOP line could be tightened.	4 / 5
Actionability	Fully executable throughout: exact command (`git config user.name`), exact directory list, exact `.gitattributes` lines, exact `## Members` header, exact choices array, and a copy-paste question template with the full roster shape.	5 / 5
Workflow Clarity	The two phases are clearly sequenced with an explicit validation checkpoint (mandatory user confirmation before any file creation) and a feedback loop ('add someone' returns to Phase 1 step 3), so the batch-write cap does not apply.	5 / 5
Progressive Disclosure	Well-organized into two phase sections with external material (casting algorithm, charters, templates) correctly referenced one level deep at `.squad/templates/*`, but the seeding/template details in Phase 2 step 6 are inlined where a short reference file could carry them, and pointers to sections of `squad.agent.md` live outside this skill.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong description: third-person, concrete, and explicit about both the two-phase behavior and the exact detection condition that loads the skill. The only weakness is trigger phrasing limited to the coordinator's detection condition rather than natural user vocabulary.

Dimension	Reasoning	Score
Specificity	Names concrete actions across both phases — 'propose the team (no files created, wait for user confirm)', 'create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins' — with comprehensive coverage and no gaps, matching the multiple-specific-actions anchor.	5 / 5
Completeness	Explicitly answers both what (two-phase protocol with concrete artifacts: scaffolding, casting state, .gitattributes, built-ins) and when (twice: 'when no team exists yet in the current repo' and 'when the coordinator detects no .squad/team.md exists'), matching the clear-what-and-when-with-triggers anchor.	5 / 5
Trigger Term Quality	Explicit, file-anchored triggers ('when no team exists yet in the current repo', 'when the coordinator detects no .squad/team.md exists') plus 'Init Mode' and 'Squad coordinator', but natural user phrasings like 'set up a team', 'create a squad', or 'squadify' are missing — good coverage, a few natural terms absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche with distinct triggers — 'Init Mode', '.squad/team.md', 'Squad coordinator', and named built-ins (Scribe, Ralph, Rai, Fact Checker) — making it unlikely to fire for the wrong skill.	5 / 5
	Total	19 / 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-templates/skills/coordinator-init-mode/SKILL.md
Commit: 29e69f5

Reviewed: 5 days 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.