CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pick-agent

Use when dispatching a subagent and choosing which one — mapping a task and its declared complexity to an agent definition, and so to a model and an effort level. Invoked by orchestrate when it hands off a task; also the answer to "should this run on a cheaper model" and "is general-purpose right here".

Quality

90%

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

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.

An unusually tight, high-signal routing skill: concrete decision tables, an executable verification command, explicit defaults, and well-handled edge cases (unconfirmed ratings, stale sessions, plugin templates). The main costs are time-sensitive statistics embedded in the main flow and a decision procedure distributed across many sections that the reader must assemble into an order.

Suggestions

Move the September–October 2026 dispatch statistics and the pointer to analyse-sessions into a short evidence/reference section (or separate file) so the main decision flow stays evergreen.

Add a brief ordered checklist of the decision checks (task demands → confirmed complexity label → DESIGN.md question → definition availability in this session → output format) so the reader doesn't have to infer precedence across sections.

DimensionReasoningScore

Conciseness

The body is dense and purposeful — "Defaulting up is cheap and recoverable; defaulting down produces a subagent that quietly does a worse job and reports success" — with no explanations of concepts Claude already knows. It misses anchor 5 because time-sensitive statistics ("Over September and October 2026, about half of all dispatches...") sit in the main flow rather than an old-patterns section, and a few table cells (the reviewer row) carry more context than the decision needs.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: a decision table mapping each agent definition to concrete task types, an executable check (`grep -n '"<package>"' <workspace>/package.json`), an explicit default ("default to `implementer`"), a defined output format ("One name... and one sentence saying why"), and precise exception rules (e.g. the effort:xhigh carve-out on the full check tier). Concrete specific guidance covers the common cases, matching anchor 5 under the instruction-only scoring note.

5 / 5

Workflow Clarity

The single action (pick a definition, justify it in one sentence) is unambiguous and carries built-in checkpoints — "Read the file of the one you choose rather than assuming either" and "Check the semver delta before you choose, do not infer it". It stops short of anchor 5 because the decision procedure is spread across many sections (rubric table, complexity table, design-agent rules, the general-purpose ban, the plugin exception, the stale-session fallback) with no explicit ordering, so the reader must synthesize the sequence themselves.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and tables, and there are no nested or buried references — the cross-references to other skills (orchestrate, prep-pr, analyse-sessions) are clearly signaled. Anchor 4 fits rather than 5 because the skill exceeds the under-50-line simple-skill case and inlines contextual material (the dispatch-site map, historical dispatch statistics) that could live in a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

95%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: it states a concrete capability chain, gives an explicit "Use when" clause with additional trigger questions phrased exactly as a user would ask them, and carves out a distinct niche unlikely to mis-trigger. The only gap is that it describes one mapping pipeline rather than a broader set of capabilities, which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Concrete actions are named — "mapping a task and its declared complexity to an agent definition, and so to a model and an effort level" — covering the full mapping chain plus invocation context. It stays at 4 because it describes one pipeline rather than enumerating multiple distinct capabilities (anchor 5), but exceeds the 1–2 concrete actions of anchor 3.

4 / 5

Completeness

Both halves are explicit: the what ("mapping a task and its declared complexity to an agent definition, and so to a model and an effort level") and the when ("Use when dispatching a subagent and choosing which one", "Invoked by orchestrate when it hands off a task", plus two concrete trigger questions). This matches anchor 5's requirement of concrete trigger phrases for both what and when.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present, including the colloquial trigger questions "should this run on a cheaper model" and "is general-purpose right here", alongside "dispatching a subagent" and "choosing which one". Coverage of the niche's vocabulary (dispatch, subagent, agent definition, model, effort, general-purpose) is comprehensive, matching anchor 5 rather than the few-missing-terms profile of anchor 4.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — choosing among agent definitions at subagent dispatch time — with distinct triggers that name its sibling orchestrate skill and the specific question "is general-purpose right here". Overlap risk with other skills is minimal, matching anchor 5; anchor 4's "minor overlap risk with closely related skills" does not fit better.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.claude/skills/pick-agent/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.