CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-improver

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

63

Quality

74%

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 ./internal/assets/skills/skill-improver/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-structured, lean, instruction-only skill that follows the LLM-first contract: clear sections, concrete paths and commands, a decision table, and one-level-deep references to a real bundled file. Its only gaps are minor redundancy and the absence of an explicit post-edit validation step.

DimensionReasoningScore

Conciseness

The ~45-line body is lean, imperative, and free of tutorial fluff, assuming Claude's competence; the only redundancy is the style-guide fallback rule restated in both Hard Rules and Execution Step 1.

4 / 5

Actionability

Concrete file paths (.atl/skill-registry.md, references/skill-style-guide.md), an exact command (gentle-ai skill-registry refresh), and a specific audit checklist make the guidance executable; no report template is given, which is a minor gap for an instruction-only skill.

4 / 5

Workflow Clarity

Execution Steps give a clear 5-step sequence with a Decision Gates table for branching and a 'rerun' verification loop in apply mode, but there is no explicit post-edit validation checkpoint before recommending a registry refresh.

4 / 5

Progressive Disclosure

The body is a compact overview that defers detail to one-level-deep, clearly signaled references (references/skill-style-guide.md, which exists as a real bundled file), with content appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

70%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 has strong trigger terms and clear what/when coverage in the repo's 'Trigger:' convention, but its action verbs are generic and overlapping rather than concrete and distinct. It distinguishes itself well from unrelated skills while flagging one sibling overlap.

Suggestions

Replace the overlapping generic verbs (improve/audit/refactor/upgrade) with distinct concrete operations, e.g. 'normalize frontmatter, restructure sections, trim body budget, relocate examples to references/'.

Add a full 'Use when...' sentence beyond the 'Trigger:' keyword list so the activation condition is unambiguous rather than implied by a comma-separated list.

DimensionReasoningScore

Specificity

It lists several actions ('improve skills, audit skills, refactor skills', 'Audit and upgrade'), but these are overlapping generic verbs applied to a single noun rather than the distinct concrete operations the score-4 anchor expects.

3 / 5

Completeness

It answers both what ('Audit and upgrade existing LLM-first skills') and when (a 'Trigger:' keyword list), but the 'when' is a keyword list rather than a full explicit 'Use when...' sentence, so it sits just below the score-5 anchor.

4 / 5

Trigger Term Quality

'improve skills, audit skills, refactor skills, skill quality' are natural phrases a user would actually say, with good coverage, though a few common synonyms ('review', 'clean up') are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (auditing/upgrading existing LLM-first skills) is distinct with specific triggers, but there is acknowledged overlap with the sibling 'skill-creator' skill, keeping it just below a 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Gentleman-Programming/gentle-ai
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.