CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is high quality: concrete, actionable, well-structured, and token-efficient, with a copy-paste spawn template and clear decision logic including upgrade feedback rules. Little improvement is needed beyond optional tightening of the per-mode exemplar sections.

DimensionReasoningScore

Conciseness

The body is lean: a decision table, brief exemplar prompts, upgrade rules, and a single spawn template, with no explanations of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Guidance is fully executable — the table gives concrete When/How/Target columns with time budgets, and the Lightweight Spawn Template is a copy-paste-ready block with real fields and warnings.

3 / 3

Workflow Clarity

The selection flow is clearly sequenced (route → pick mode via table → spawn), and the upgrade rules provide an explicit feedback loop ('if a Lightweight task turns out to need history → treat as Standard'); no destructive validation is needed for a selection task.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is self-contained with well-organized header sections and a clear overview blockquote plus decision table up front, satisfying the simple-skill allowance.

3 / 3

Total

12

/

12

Passed

Description

70%

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 is specific, complete, and distinct, clearly stating both what the skill contains and when it loads. Its main weakness is trigger-term quality: it speaks in internal squad jargon rather than natural user-facing keywords, though this is partly inherent to a coordinator-internal satellite skill.

Suggestions

Add a brief natural-language trigger phrase (e.g., 'Use when picking how much ceremony a routed task needs') so the description echoes language a user or coordinator might actually say.

Consider including common surface variations like 'response mode', 'spawn ceremony', or 'Direct/Lightweight/Standard/Full' as explicit keywords to improve trigger discoverability.

DimensionReasoningScore

Specificity

Lists multiple concrete artifacts — "the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules" — rather than vague language, matching the anchor for listing several specific actions.

3 / 3

Completeness

It states what the skill contains and gives explicit when guidance ("Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task"), which is equivalent to a 'Use when' trigger, so it is not capped at 2.

3 / 3

Trigger Term Quality

The terms are internal squad jargon ("Routing table", "Response Mode", "ceremony level", "Lightweight spawn template") that a user would never naturally say; there are no natural user-facing keywords, matching the lowest anchor.

1 / 3

Distinctiveness Conflict Risk

It carves a clear niche by explicitly contrasting WHO (Routing) vs HOW (Response Mode), and the trigger (after routing, picking ceremony level) is specific enough to avoid firing for the wrong skill.

3 / 3

Total

10

/

12

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.

Validation15 / 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
bradygaster/squad
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.