CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-improve

Improve a skill via a test-fix-retest loop — static checks, targeted fixes, keep or revert on score change.

Quality

80%

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-improve/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 exemplary instruction-only skill: dense, executable, and self-validating, with an explicit test-fix-retest loop and careful edge-case handling (NOT ASSESSED, revert semantics). The only structural refinement available is moving the static-check and category-rubric mappings into a references file.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no concept-explanation padding; every line carries project-specific rules or rationale (e.g. "0 FAILs from a file nobody could read is not a clean result") that Claude could not infer.

5 / 5

Actionability

Fully concrete for an instruction-only skill: exact commands ("/skill-test static [name]"), exact display templates, exact ask prompts, and exact gap-to-fix mappings ("Check 4 fail → Write or Edit in allowed-tools but no ask-before-write").

5 / 5

Workflow Clarity

The 7-phase sequence is a genuine feedback loop (test → fix → retest → keep or revert) with explicit validation checkpoints, NOT ASSESSED handling at both baseline and retest, and a guarded restore path (record content, never git checkout).

5 / 5

Progressive Disclosure

A single well-sectioned file with clearly signaled one-level-deep pointers to project files (studio-tests/catalog.yaml, the target skill's references/ folder); however, inlined check-gap mappings and category examples (G2/A2/T3) are detail that could live in a references/ file for this skill's own bundle.

4 / 5

Total

19

/

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.

A crisp, specific one-liner that clearly states what the skill does, but it omits any explicit "when to use it" trigger guidance and lacks natural keyword variations. Adding a Use-when clause and trigger synonyms would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to improve a skill's quality score, fix failing skill-test checks, or iterate on skill quality."

Add natural trigger terms users would actually say, such as "skill quality", "failing checks", "skill score", or "skill audit", to improve keyword coverage.

Optionally mention the category-check and revert behavior ("reverts changes if the score does not improve") to round out capability coverage.

DimensionReasoningScore

Specificity

"test-fix-retest loop", "static checks", "targeted fixes", "keep or revert" name several concrete actions in third person, but coverage is incomplete — category checks, diagnosis, and the audit/next-steps loop are unmentioned.

4 / 5

Completeness

The "what" is clear (test-fix-retest improvement loop) but there is no "Use when..." clause or any explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Improve a skill" is a natural phrase, but the description misses common variations users would say such as "skill quality", "failing checks", "skill score", or "skill audit".

3 / 5

Distinctiveness Conflict Risk

The niche (improving an existing skill against static/category checks) is distinct with specific triggers like "test-fix-retest loop"; minor overlap risk with a sibling skill-testing or skill-authoring skill.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

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