coordinator-response-mode

Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task.

Quality

73%

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 ./.squad/skills/coordinator-response-mode/SKILL.md

Quality

Content

82%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 lean, highly actionable body whose decision table, per-mode exemplars, upgrade rules, and copy-paste spawn template give the coordinator everything needed to pick and execute a response mode; the only real gap is the absence of any progressive-disclosure split for the spawn template.

Dimension	Reasoning	Score
Conciseness	The body is efficient — a decision table, terse exemplars, short upgrade rules, and a copy-paste spawn template — with only minor trimmable chatter like 'A user favorite — make it instant' and 'This is the current default'; not a 5 because a few phrases could still be cut.	4 / 5
Actionability	Provides a copy-paste-ready Lightweight spawn template with parameterized placeholders, an inline explore-agent variant for read-only queries, and concrete exemplar prompts for every mode, covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The decision procedure is clear and unambiguous — route, pick a mode from the table, apply the upgrade rules, never downgrade mid-task — but it is a selection procedure rather than a multi-step workflow with explicit validation checkpoints, so it stops short of the 5 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Selection table, per-mode exemplars, upgrade rules, spawn template) with easy navigation and no nesting; not a 5 because everything is inlined at ~88 lines with no one-level-deep reference split for the sizable spawn template.	4 / 5
	Total	17 / 20 Passed

Description

63%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 distinct, well-scoped description that clearly separates Response Mode from Routing and enumerates its contents, but it relies on internal coordinator jargon rather than natural user trigger phrases and frames its 'when' as load behavior instead of an explicit Use-when clause.

Suggestions

Add an explicit 'Use when...' clause phrased as a natural trigger (e.g. 'Use after routing has picked an agent and you must choose how much ceremony the response needs').

Surface a couple of user-facing trigger terms beyond internal mode names so the skill is discoverable by what users actually say.

Lead with the action ('Picks the response mode...') in third person before the Routing-vs-Response-Mode framing, so the 'what' lands before the boundary explanation.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete contents — 'complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules' — giving comprehensive coverage with only minor gaps; not a 5 because it inventories contents rather than stating multiple discrete actions.	4 / 5
Completeness	It states both what ('contains the complete decision table... template... upgrade rules') and when ('loads this on demand once routing has identified the agent'), but the 'when' is framed as coordinator behavior rather than an explicit 'Use when...' trigger, so it could be more explicit.	4 / 5
Trigger Term Quality	The only candidate terms are internal jargon ('Response Mode', 'Direct, Lightweight, Standard, Full', 'ceremony level') that a user would never actually say; it lacks the natural phrases users invoke, sitting just above the all-jargon anchor.	2 / 5
Distinctiveness Conflict Risk	It draws an explicit boundary — 'Selecting WHO handles work is the Routing table; selecting HOW they handle it... is Response Mode' — carving a clear niche with minimal conflict risk against sibling skills.	5 / 5
	Total	15 / 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/skills/coordinator-response-mode/SKILL.md
Commit: a0d2563

Reviewed: about 16 hours 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.