CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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.

The content delivers a clear, well-validated iterative workflow with concrete invocation guidance and an explicit feedback loop. Its weakness is conciseness, driven by repeated restatements of the completion marker and a motivational anti-rationalization section that could be trimmed.

Suggestions

Consolidate the completion-marker guidance into a single 'Completion Criteria' section; the marker is currently restated in the Example Fix Cycle, Completion Criteria, and closing paragraph, which can be reduced to one authoritative statement plus the checklist.

Trim or remove the 'Rationalizations to Reject' section, which is motivational padding rather than executable guidance; the 'When NOT to output the marker' checklist already enforces the same discipline.

Consider moving the detailed 'Issue Categorization' examples (Critical/Major/Minor bullet lists) into a references/ file referenced from the body, improving both conciseness and progressive disclosure for the ~140-line skill.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance, but the completion marker is restated across the Example Fix Cycle, Completion Criteria, and closing note, and the 'Rationalizations to Reject' section is motivational padding; this matches 'mostly efficient but includes some unnecessary explanation that could be tightened' rather than the lean anchor 5 or the heavily padded anchor 2.

3 / 5

Actionability

Provides a copy-paste invocation prompt ('Review the skill at [SKILL_PATH] using the plugin-dev:skill-reviewer agent...'), a concrete verification command ('/plugins'), and an exact completion marker ('<skill-improvement-complete>'); minor gaps in how to categorize issues keep it just below the fully-executable anchor 5.

4 / 5

Workflow Clarity

The Review→Categorize→Fix→Evaluate→Repeat loop has explicit validation checkpoints, an Iteration 2 re-review feedback loop for error recovery, and a checklist for when to/not to emit the marker, matching the 'clear sequence with explicit validation steps, feedback loops, and checklists' anchor; the batch-operation validation cap does not apply because verification is present.

5 / 5

Progressive Disclosure

The body is well-organized with clear section headers and no nested references, giving good structure and easy navigation; however it is a single ~140-line file with no bundle references and some inline material (issue categorization examples) that could be split out, so it sits below the one-level-deep-reference anchor 5 and above the loosely-organized anchor 3.

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.

The description clearly answers both what the skill does and when to use it, with an explicit 'Use when' clause and natural trigger terms. Its main limitation is specificity, as it names a single high-level action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Iteratively improve a Claude Code skill using the skill-reviewer agent') but does not list several specific actions, matching the 'names domain and 1-2 concrete actions' anchor; it is not a comprehensive action list (rule out 4) yet more concrete than purely generic (rule out 2).

3 / 5

Completeness

Explicitly states what it does ('Iteratively improve a Claude Code skill...until it meets quality standards') and gives an explicit 'Use when...' clause with three concrete trigger scenarios, matching the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('improving a skill', 'iterating on a new skill', 'automated fix-review cycles', 'manual editing'), giving good keyword coverage; a few natural synonyms (e.g. 'review', 'refine', 'audit') are missing, so it sits just below the comprehensive anchor 5 and above anchor 3.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (iterative skill improvement) with distinct triggers ('iteratively', 'automated fix-review cycles'), but overlaps slightly with the skill-reviewer skill it wraps; minor overlap risk with a closely related skill matches anchor 4 rather than the minimal-conflict anchor 5.

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