CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-cost-projections

Project remaining workflow cost from per-phase averages — warns on budget ceiling overruns

52

Quality

59%

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 ./.claude/skills/skill-cost-projections/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 a well-structured, highly actionable walkthrough with executable code, formulas, and thorough error handling for a read-only projection task. Conciseness and progressive disclosure are strong but not maximal due to some repeated examples and inline density.

DimensionReasoningScore

Conciseness

Mostly efficient with executable bash, formulas, and compact display formats, but the 'Complete Display Examples' section repeats outputs already shown per-step and the Integration section lightly restates earlier points, so a little could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready jq/bc commands with formulas, env-var thresholds, and concrete display formats covering the common cases (within budget, over budget, insufficient data, zero steps, no metrics).

5 / 5

Workflow Clarity

Six clearly sequenced steps with data-validity checkpoints (<2 steps, missing/corrupted metrics, zero remaining steps); this is a read-only projection skill so the destructive/batch feedback-loop cap does not apply, but there is no explicit validate->fix->retry loop to reach 5.

4 / 5

Progressive Disclosure

Single self-contained file with clear section headers and no nested/multi-level references; no bundle files exist, so the well-organized inline structure is appropriate, though at ~210 lines it is denser than a minimal single-purpose skill.

4 / 5

Total

17

/

20

Passed

Description

46%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 but omits explicit 'when to use' trigger guidance and natural user phrasings, which live in the separate trigger block instead. Specificity and distinctiveness are reasonable; trigger-term quality and completeness are the weak spots.

Suggestions

Fold one concrete trigger phrase into the description itself (e.g. 'Use when the user asks to estimate remaining workflow cost or whether they are over budget') so 'what' and 'when' are both present.

Add natural user phrasings to the description ('how much will this cost', 'budget forecast') rather than only domain jargon like 'per-phase averages'.

Mention the HUD/statusline display output in the description to round out the action coverage beyond just projecting and warning.

DimensionReasoningScore

Specificity

Names the domain ('workflow cost projection') and two concrete actions ('Project remaining workflow cost from per-phase averages', 'warns on budget ceiling overruns'), but coverage is not comprehensive — missing display/HUD/integration actions.

3 / 5

Completeness

It gives a clear 'what' (project remaining workflow cost, warn on overruns) but no explicit 'when'/'Use when...' trigger guidance inside the description field; the trigger guidance lives only in the separate trigger block, capping completeness at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

The description field itself contains only domain terms ('workflow cost', 'per-phase averages', 'budget ceiling') and lacks the natural user phrases ('how much will this cost', 'am I over budget') that appear only in the separate trigger block, so it misses the common phrasings users actually say.

2 / 5

Distinctiveness Conflict Risk

The narrow niche (per-phase workflow cost projection with budget ceilings) is mostly distinct from other skills with only minor overlap risk against generic pricing/cost questions.

4 / 5

Total

12

/

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.

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
nyldn/claude-octopus
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.