CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-refine

Score and improve an artifact with a frozen rubric, independent models, implemented edits, and bounded rescoring

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-refine/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers a well-validated, phase-structured workflow with concrete commands and strong safety checkpoints, and its reference bundle is real and well-signaled. Its main weaknesses are repetition of budget and contract rules within the body and significant duplication of references/phase-3.md content inline, which hurt both conciseness and progressive disclosure.

Suggestions

Move the detailed phase-3 judging contract rules (blind rubric construction, pair dispatch mechanics, disagreement limit) out of SKILL.md and into references/phase-3.md, keeping only a one-line summary per phase in the body.

Deduplicate repeated policy statements: state the budget-consumption rules, "never reset counters", and concurrent-edit preservation once each instead of two to three times.

Consolidate the scattered stop/resume conditions into a single checklist near the budget section so the sequence is traceable without cross-referencing later sections.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes competence (no basic-concept explanations), but policy statements repeat within the body ("never reset counters" twice, budget-consumption rules stated three ways, concurrent-edit preservation twice) and the fixed judging contract section substantially duplicates content in references/phase-3.md. Mostly efficient but needs meaningful tightening, which fits anchor 3 rather than the minor-trimming level 4.

3 / 5

Actionability

It provides one fully executable bash block for root resolution, exact flags for preflight ("preflight.sh --providers claude,codex"), and named subcommands for refinement-run.py begin/prepare/record and refinement-pair.py, with full invocation syntax deferred to the phase reference files. Mostly executable guidance with minor gaps, short of copy-paste-ready coverage across the common cases.

4 / 5

Workflow Clarity

Five phases are numbered with explicit load order, and validation is pervasive (check time and calls before every dispatch, verify findings before edits, stop after two stalled rounds, confirm the original is unchanged before publishing). It falls short of 5 because the sequence is scattered: the body interleaves detailed phase-3 judging contract rules into the overview, so a reader must cross-reference to know which instructions apply when.

4 / 5

Progressive Disclosure

The bundle references (references/phase-2.md through phase-5.md) all exist, are one level deep, and are clearly signaled with per-phase load instructions, but the body inlines the phase-3 judging contract (blind rubric, hidden target/prior scores, pair dispatch, disagreement limit) that already lives in references/phase-3.md. Content that should be separate is duplicated inline, which is beyond the minor organization gaps of level 4.

3 / 5

Total

14

/

20

Passed

Description

53%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 is concise, third-person, and describes a distinctive rubric-based refinement workflow, but it has no trigger guidance for when the skill should be used and its keyword coverage omits natural synonyms in favor of method jargon. Adding an explicit "Use when..." clause would materially raise its score.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to score, evaluate, review, or iteratively refine an artifact against a rubric or quality criteria."

Include natural user phrasings and synonyms ("review", "evaluate", "refine", "grade") alongside the current method jargon ("frozen rubric", "bounded rescoring").

Name the accepted artifact types concretely (text, files, plans, code) instead of the generic "an artifact" to sharpen specificity.

DimensionReasoningScore

Specificity

"Score and improve an artifact" names two concrete actions, while "frozen rubric, independent models, implemented edits, and bounded rescoring" are method qualifiers rather than additional actions. This matches the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage, and falls short of the several-distinct-actions level above.

3 / 5

Completeness

The "what" is clear (score and improve an artifact via rubric-based judging), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms like "score", "improve", and "rubric" are relevant, but "frozen rubric", "bounded rescoring", and "independent models" lean technical, and natural variations users would say ("review", "evaluate", "refine", "critique", "iterate") are missing. Some relevant keywords with missing common synonyms fits this level.

3 / 5

Distinctiveness Conflict Risk

The method specification (frozen rubric, independent models, bounded rescoring) carves a distinct niche that is unlikely to fire for unrelated skills, with only minor overlap risk against generic review or improvement skills. It stops short of 5 because "score and improve an artifact" alone is fairly broad phrasing shared with general review skills.

4 / 5

Total

13

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

skills/skill-refine/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.