CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

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/coordinator-init-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-sequenced two-phase protocol with a strong user-confirmation gate and much copy-paste-ready detail (commands, verbatim prompts, directory structure, .gitattributes content). Its weaknesses are repetition used as emphasis, delegation of the casting algorithm to a reference that cannot exist yet at load time, inlined project-specific governance policy, and no verification step after the batch file creation in Phase 2.

Suggestions

Add a post-creation verification step at the end of Phase 2 (e.g., confirm team.md contains the exact '## Members' header and the casting registry/history were initialized by the locked SDK writer) before announcing '✅ Team hired', closing the feedback loop on the batch scaffolding operation.

Fix the circular reference in Phase 1 step 3: '.squad/templates/casting-reference.md' cannot exist when Init Mode triggers (no .squad/ yet). Either inline a minimal casting algorithm or point to a file actually shipped with this skill's bundle.

Move the three Waza-specific governance override paragraphs (casting-state repair and reviewer seeding) into a separate reference file, and collapse the repeated roster-copy rules and the four per-agent 'exempt from casting' lines into single statements.

DimensionReasoningScore

Conciseness

The body is operational rather than explanatory, but repeats itself noticeably: the roster-copy requirement is stated three ways ("Do not regenerate, summarize, truncate, omit, or replace any roster row", the shape block, then "Never use a bare 'Look right?' question"), "genuinely empty new target" appears twice nearly verbatim, and the four always-on agents each get a separate "exempt from casting" line that could be one sentence. This is mostly-efficient-but-could-be-tightened rather than anchor 2's padded sections, since there is no explanation of concepts Claude already knows beyond one justifiable line about the union merge driver.

3 / 5

Actionability

Most guidance is copy-paste ready: exact command ("git config user.name"), verbatim questions, the full .squad/ directory list, the complete .gitattributes block, the exact choices array, and the hard-coded "## Members" header requirement. The gap is that the core casting step delegates to "the canonical Casting reference at .squad/templates/casting-reference.md" — a file that cannot exist during Phase 1 since .squad/ is only created in Phase 2 — and seeding sources ("Rai-charter.md", "rai-policy.md", "fact-checker-charter.md") are named without paths.

4 / 5

Workflow Clarity

Sequencing is excellent — numbered steps across two phases, a hard "⚠️ STOP" gate before any file creation, an explicit Phase 2 trigger, and a re-propose feedback loop for "add someone"/"change a role". However, Phase 2 performs a batch operation (creating the whole .squad/ tree plus updating .gitattributes) with no post-creation verification step — e.g., no check that team.md actually contains the required "## Members" header or that casting state initialized atomically — so the rubric's cap for batch operations missing validation/verification applies.

3 / 5

Progressive Disclosure

The two-phase structure with headers and numbered steps is clear, but three dense Waza governance-override paragraphs (casting-state repair, reviewer seeding) are inlined policy that belongs in a separate reference file, and the references the body does cite (.squad/templates/casting-reference.md, squad.agent.md sections, charter templates) are neither bundle files nor clearly resolvable at load time. This matches the anchor for structure present but content that should be separate kept inline with references not clearly signaled.

3 / 5

Total

13

/

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, covers both phases of the protocol, and includes an explicit on-demand load trigger tied to a detectable condition. The only weakness is modest natural-language trigger coverage — it relies on domain jargon ("Init Mode", ".squad/team.md") more than the phrases a user would naturally say when asking to initialize a team.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named artifacts across both phases: "propose the team", "create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker)". Coverage is comprehensive for this protocol, matching the anchor for multiple specific concrete actions rather than the anchor-4 case with minor gaps.

5 / 5

Completeness

It explicitly answers both questions: what ("The complete two-phase Init Mode protocol the Squad coordinator runs", with per-phase actions) and when ("Loaded on demand when the coordinator detects no .squad/team.md exists"). The trigger is concrete and explicit, matching the anchor requiring both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage within the domain — "Init Mode", "team", "no team exists yet", ".squad/team.md", "Squad coordinator" — but common natural variations users would say are missing (e.g., "set up", "initialize", "create a team", "new squad"). This sits clearly at good-coverage-with-a-few-missing-terms rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — Squad Init Mode triggered by a specific filesystem state (no .squad/team.md) — which is unlikely to collide with other skills. The state-based trigger condition is highly distinct, matching the minimal-conflict-risk anchor.

5 / 5

Total

19

/

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/coordinator-init-mode/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.