CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

model-cost-compare

Starter: compare model costs for a described task — maps task shape to the cheapest adequate seat and shows the price spread

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/octopus-starter-pack/model-cost-compare/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 instruction skill with a clearly sequenced workflow and concrete pricing data, decision rules, and guardrails. Its main defects are a dangling reference to a non-existent bundle file and the absence of an explicit validation/feedback step in the workflow.

Suggestions

Fix or remove the reference to `skills/blocks/fable5-prompting.md` — no such file exists in the bundle; either ship it under references/ or drop the pointer.

Inline the cost table (or state exactly where it lives) instead of deferring to "the cost table in CLAUDE.md", so the skill is self-contained.

Add an explicit validation checkpoint, e.g., after pricing: re-check the recommendation against the Guardrails list and confirm the estimate exceeds/undercuts the 1 USD disclosure threshold before presenting the spread.

DimensionReasoningScore

Conciseness

The 28-line body is lean and operational throughout — "Bucket it: mechanical (rename, format), standard coding, hard reasoning...", "files touched × average size; state the assumption", and the inline price roster carry information Claude does not already know, with zero padding or explanation of known concepts. Every token earns its place.

5 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: explicit classification buckets, per-seat prices (e.g., "Claude Sonnet 5 (2/10 USD)"), decision rules ("Mechanical work goes to included or budget seats"), and a specified three-row spread table. Minor gaps remain — pricing defers to "the cost table in CLAUDE.md" rather than being fully self-contained, and the volume-estimation formula is left as an assumption to state — so it is not a 5.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced (classify → estimate → price → recommend → check risks → show spread) with real checkpoints: the risk-surface escalation list and "If the estimate exceeds 1 USD, say so explicitly before any dispatch happens." It falls short of a 5 because there is no explicit validation or feedback step (e.g., sanity-checking the estimate or re-verifying the recommendation against the guardrails) — checkpoints are present but not looped.

4 / 5

Progressive Disclosure

Sections (When to use, Steps, Guardrails) are well organized and the body is appropriately short, but it references "`skills/blocks/fable5-prompting.md`" which does not exist in the bundle (no references/, scripts/, or assets/ directories), and it depends on an external CLAUDE.md cost table. A dangling, unresolvable reference path keeps this at "some structure but could be better organized" rather than good.

3 / 5

Total

16

/

20

Passed

Description

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

The description clearly states what the skill does with concrete action verbs, but lacks any explicit "Use when..." trigger clause and misses common natural synonyms like "pricing" or "which model should I use". It is a competent but incomplete description whose trigger guidance is only weakly implied.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks which model to use, what a task will cost, or wants the cheapest/budget option for a job."

Include natural synonyms users actually say — "model pricing", "budget", "which model should I use" — to broaden trigger term coverage.

Drop the "Starter:" label prefix or replace it with capability wording, since it conveys pack status rather than what the skill does.

DimensionReasoningScore

Specificity

Quotes like "compare model costs for a described task", "maps task shape to the cheapest adequate seat", and "shows the price spread" list several concrete actions with only minor gaps (no mention of budget checks or model-selection variants). It is not a 5 because coverage of the capability space is thin beyond the three named actions, and not a 3 because it clearly exceeds 1-2 actions.

4 / 5

Completeness

The "what" is clear (compare model costs, map task to cheapest adequate seat, show price spread), but there is no explicit "Use when..." clause or equivalent trigger guidance; "for a described task" only weakly implies when. Per the judging guidelines, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms present include "compare model costs", "cheapest", and "price spread", which a user might plausibly say. Common variations and synonyms are missing — e.g., "pricing", "model pricing", "budget", "which model should I use" — so keyword coverage is only partial rather than good.

3 / 5

Distinctiveness Conflict Risk

The niche — cost comparison and cheapest-adequate-seat selection — is mostly distinct, with specific triggers like "compare model costs" and "price spread". Minor overlap risk remains with generic model-selection or model-recommendation skills, keeping it below a 5.

4 / 5

Total

14

/

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

nyldn/claude-octopus

Path

skills/octopus-starter-pack/model-cost-compare/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.