CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-improver

Iteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards. Use when improving a skill with multiple quality issues, iterating on a new skill until it meets standards, or automated fix-review cycles instead of manual editing.

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-improver/SKILL.md

The canonical home for this skill is skill-improver in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured instruction-only skill with an exemplary workflow: clear loop, explicit verification step, feedback cycle, and unambiguous completion criteria. Its weaknesses are token efficiency (the completion-marker rule is stated three times) and a non-executable plugin installation instruction.

Suggestions

Consolidate the completion-marker guidance into the single 'Completion Criteria' section and state it once, removing the duplicate emphasis in 'Example Fix Cycle' and the closing repetition at the end of that section.

Make the plugin-dev installation instruction executable: provide the actual marketplace/command (e.g., the specific /plugin install command or repository URL) instead of 'install from the Trail of Bits plugin repository'.

Consider moving the detailed issue-categorization taxonomy and the example fix cycle into a reference file (e.g., references/severity-guide.md) to slim the main SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-scoped sections, but the completion-marker instruction is repeated across 'Example Fix Cycle', 'Completion Criteria', and again in the closing line ('The marker is the ONLY way to complete the loop. Natural language like "looks good"... will NOT stop the loop' appears twice nearly verbatim). Fits anchor 3 ('mostly efficient but could be tightened') rather than anchor 2, since the padding is confined to one repeated emphasis rather than several padded sections.

3 / 5

Actionability

Concrete, copy-paste-ready guidance: the quoted skill-reviewer request with the [SKILL_PATH] placeholder explained, the exact completion marker, a worked example fix cycle, and an explicit severity taxonomy. Minor gaps keep it below anchor 5: 'install from the Trail of Bits plugin repository' provides no command or URL, and the Core Loop's 'Call skill-reviewer' step is only operationalized later via a natural-language request rather than at the point of use.

4 / 5

Workflow Clarity

The Core Loop gives a clear 5-step sequence (Review, Categorize, Fix, Evaluate, Repeat) with an explicit validation checkpoint (re-run skill-reviewer to verify fixes, demonstrated in Iteration 2), a feedback loop, and a completion checklist with explicit when/when-not-to-exit conditions plus anti-rationalization guardrails. This matches anchor 5; the skill is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and the single ~135-line SKILL.md is organized into clear, logically ordered sections with no nested references. This fits anchor 4 ('good structure; minor organization gaps') rather than anchor 5, since the completion-marker instructions are spread across three sections and the issue taxonomy / example cycle could live in a reference file; it exceeds anchor 3 because the structure is genuinely good and nothing is buried.

4 / 5

Total

16

/

20

Passed

Description

78%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 that clearly and explicitly states both what the skill does and when to use it, with natural, distinct trigger phrases. Its main weakness is specificity: it describes the overall goal rather than enumerating the concrete actions in the improvement loop.

Suggestions

Enumerate the concrete loop actions in the description, e.g., 'Reviews the skill via the skill-reviewer agent, categorizes issues by severity, fixes critical/major issues, and re-verifies until the skill passes.'

Add one or two common synonyms for trigger coverage, such as 'refine' or 'polish a skill', to catch phrasings users might naturally use.

DimensionReasoningScore

Specificity

The description names the domain ('Iteratively improve a Claude Code skill') and 1-2 concrete actions ('using the skill-reviewer agent', 'until it meets quality standards'), but does not enumerate the several specific actions the loop performs (categorize issues by severity, fix critical/major issues, re-verify). This matches anchor 3 rather than 4, which requires a list of several specific actions, and exceeds anchor 2 because the concrete mechanism is named.

3 / 5

Completeness

The description explicitly answers 'what' ('Iteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards') and 'when' ('Use when improving a skill with multiple quality issues, iterating on a new skill until it meets standards, or automated fix-review cycles instead of manual editing') with three concrete trigger phrases. This clearly matches anchor 5.

5 / 5

Trigger Term Quality

Phrases like 'improving a skill with multiple quality issues', 'iterating on a new skill until it meets standards', and 'automated fix-review cycles instead of manual editing' are natural user language with good coverage, but common synonyms such as 'refine', 'polish', or 'make this skill better' are missing. Good coverage with a few natural terms missing fits anchor 4 rather than the synonym-level comprehensiveness of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (agent-driven iterative skill improvement) and its triggers are distinct, with only minor overlap risk against a one-off skill review or single manual edit request. Fits anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-improver/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.