CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

86%

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

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 tight, self-contained satellite skill: an unambiguous decision table with tie-break rules, concrete exemplars for every mode, and a complete spawn template. The only weaknesses are minor — mixed placeholder conventions and an unexplained Jinja conditional in the template, and a large inline template that could live in a bundle file.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: a dense selection table, one-line exemplars ("Fix the typo in README → Spawn one agent, no charter, no history read"), compact upgrade rules, and a template with no filler or explanation of concepts Claude already knows. Only trivially trimmable fragments ("A user favorite — make it instant") exist, which does not drop it to the 4 anchor's "minor instances of over-explanation".

5 / 5

Actionability

Highly actionable: the decision table gives concrete criteria and targets, each mode has copy-ready exemplar prompts, and the Lightweight Spawn Template is a complete fill-in prompt including the read-only variant ("agent_type: 'explore' with 'You are {Name}...'"), covering the common cases. Not a 5 because of minor gaps: the Jinja "{% if WORKTREE_MODE %}" block is used without explanation, and placeholder conventions are inconsistent ("{resolved_model}" vs "<resolved CURRENT_DATETIME literal>") with no resolution guidance.

4 / 5

Workflow Clarity

The procedure is fully determined and unambiguous: "After routing determines WHO handles work, select the response MODE based on task complexity", the table fixes base selection, the upgrade rules act as explicit tie-break checkpoints ("If uncertain between Lightweight and Standard → choose Standard"), and "Never downgrade mid-task" closes the loop. No destructive or batch operations are involved, so no validation cap applies; the decision checkpoints match the 5 anchor.

5 / 5

Progressive Disclosure

Good structure with clear sections (selection table, per-mode exemplars, upgrade rules, spawn template) and no nested references — the only external mention, the "1-line stub in squad.agent.md", is clearly signaled as awareness-only. Not a 5 because the ~28-line spawn template is inlined where a references/ file could carry it, and the body exceeds the under-50-lines simple-skill case; not a 3 because nothing that clearly belongs elsewhere is buried and navigation is easy.

4 / 5

Total

18

/

20

Passed

Description

78%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, specific description that clearly bounds its niche against the Routing table and enumerates its concrete contents. Its main weakness is trigger phrasing: the when-clause is an internal load condition rather than natural trigger terms a user would say, which keeps completeness and trigger quality at 4.

DimensionReasoningScore

Specificity

The description enumerates concrete contents — "the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules" — several specific items with only minor gaps. It is not a 5 because the enumeration describes what the file contains rather than a comprehensive list of concrete actions performed (the action itself, "pick the right ceremony level", is stated only once), and part of the text is meta-framing about the Routing table.

4 / 5

Completeness

Both halves are present: the "what" is explicit ("complete decision table, exemplar prompts... spawn template, and the upgrade rules") and the "when" is explicit ("loads this on demand once routing has identified the agent"). It falls short of a 5 because the when-clause describes an internal load condition rather than concrete trigger phrases a user or coordinator would say, and it could be more specific about which situations call for it.

4 / 5

Trigger Term Quality

Good keyword coverage of the domain's natural terms: "Response Mode", all four mode names "Direct, Lightweight, Standard, Full", "spawn", and "ceremony level" — exactly the terms a squad coordinator would use when needing this skill. Not a 5 because it includes no synonyms or variations (e.g., task-size or urgency phrasings) and leans on internal jargon without any user-side phrasing.

4 / 5

Distinctiveness Conflict Risk

The opening sentence is an explicit disambiguation against the nearest competing skill — "Selecting WHO handles work is the Routing table; selecting HOW they handle it... is Response Mode" — establishing a clear niche with distinct mode-name triggers and minimal conflict risk. It is not a 4 because the overlap with the routing skill is not just minor but actively resolved in the text itself.

5 / 5

Total

17

/

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

bradygaster/squad

Path

.squad-templates/skills/coordinator-response-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.