CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pick-model

Recommend the cheapest Claude model tier (Haiku, Sonnet, Opus) that still meets a task's quality bar, using a task-type matrix plus complexity escalators (scope, stakes, ambiguity, stakeholders). Use when asked "which model", "pick model", "model for", or before starting a costly task. Covers technical, business, creative work.

Quality

92%

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%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.

The body is an exemplar decision-routing skill: a complete, executable procedure with tie-breaks, justification and confidence checkpoints, a copy-paste output template, calibrated anti-patterns and worked examples, and a clean split between the inline overview and four well-signaled reference files. No dimension shows more than minor room for improvement.

DimensionReasoningScore

Conciseness

The body is lean throughout: a 4-bullet Mindset, a compact tier table, one-line escalator checks, terse 'Why:' clauses on anti-patterns, and three tight worked examples. It explains no concepts Claude already knows and every section carries decision-relevant signal, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Fully executable guidance for an instruction-only skill: a 6-step procedure with exact rules ('Move up exactly one tier when any escalator fires, capped at Opus'), a tie-break list, a copy-paste output template with a filled example, and worked examples covering all three tiers. As an instruction-only skill, the absence of code is not penalized and the guidance is maximally specific.

5 / 5

Workflow Clarity

The procedure is a clearly sequenced loop with explicit checkpoints: step 1 handles missing input ('Ask for it when the argument is empty'), step 6 enforces justification ('Always name the escalator or matrix row that decided it'), and the confidence rule provides an error-recovery feedback loop ('Ask one clarifying question instead of guessing when confidence is low'). The validation cap for destructive/batch operations does not apply to this recommendation skill.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview: the base-tier matrix, escalator summaries, tie-breaks, output format and calibrating examples are inline, while deeper material sits in four real one-level-deep files (references/decision-matrix.md, escalators.md, examples.md, reference.md), each clearly signaled inline ('Read the full matrix', 'See escalators for edge cases', 'More cases are in worked examples') and catalogued in a descriptive References section.

5 / 5

Total

20

/

20

Passed

Description

83%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, names the method and its signals, covers task domains, and gives explicit quoted trigger phrases for both interactive and automated use. Its only weaknesses are a single-action framing and slightly incomplete synonym coverage for triggers.

DimensionReasoningScore

Specificity

Concrete action ('Recommend the cheapest Claude model tier (Haiku, Sonnet, Opus)') with a stated method ('task-type matrix plus complexity escalators (scope, stakes, ambiguity, stakeholders)') and covered domains ('Covers technical, business, creative work'). It is one primary action with rich supporting specifics rather than the multiple distinct concrete actions of the 5 anchor, but well above the 1-2-action coverage of the 3 anchor.

4 / 5

Completeness

Explicitly answers what ('Recommend the cheapest Claude model tier... using a task-type matrix plus complexity escalators') and when ('Use when asked "which model", "pick model", "model for", or before starting a costly task') with concrete trigger phrases, matching the 5 anchor exactly. The 'when' clause is specific and quoted, not the merely-present 'when' of the 4 anchor.

5 / 5

Trigger Term Quality

Explicit quoted triggers 'which model', 'pick model', 'model for' are phrases users naturally say, plus 'before starting a costly task'. Common synonyms such as 'choose a model', 'model selection', or 'cheap model' are missing, so coverage is good but not comprehensive as the 5 anchor requires.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Claude tier recommendation) with distinct triggers, but 'model for' is broad enough to fire on cross-vendor or general model-choice questions that the skill itself excludes, and it sits near model/API/pricing skills. Minor overlap risk matches the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 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

pantheon-org/tekhne

Path

skills/agentic-harness/pick-model/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.