CtrlK
BlogDocsLog inGet started
Tessl Logo

minimal-fix

Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured instruction-only skill with a clear process and output scaffold. Its main weakness is workflow robustness: verification is mentioned but lacks an explicit fix→re-run feedback loop, and concrete command examples would raise actionability.

Suggestions

Add an explicit feedback loop to the Process: after running tests/lint, add 'If failures, fix and re-run until green' to turn the implicit checkpoint into a real validation loop.

Provide one concrete example invocation for the test/lint step (or note where to find project commands, e.g. AGENTS.md) to make the guidance copy-paste ready.

Specify what 'Summarize: what changed, why, what you ran' should contain beyond the Output template, or remove redundancy between the Process step and the Output section.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section (Inputs, Process, Output, Rules) earns its place.

3 / 3

Actionability

Gives concrete instruction-style guidance and a usable output template, but lacks specific executable commands or copy-paste examples (e.g. example test/lint invocations), leaving key details incomplete.

2 / 3

Workflow Clarity

A clear five-step sequence is present, but verification (step 4 'Run tests/lint') is a single flat step with no explicit fix-and-retry feedback loop, matching the 'validation gaps; checkpoints implicit' anchor.

2 / 3

Progressive Disclosure

Under 50 lines, single-task, with no external references needed; the body is cleanly organized into well-signaled sections, which the rubric notes allow to score 3.

3 / 3

Total

10

/

12

Passed

Description

100%

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 tight and well-scoped: it states a concrete capability, lists natural trigger terms, gives an explicit 'Use when' clause, and includes guardrails that distinguish it from broader refactoring skills. It exemplifies the rubric's good-overall pattern.

DimensionReasoningScore

Specificity

Names a concrete action ('smallest possible code change') plus multiple specific concrete issue types (CI failure, reviewer comment, typo), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does (produce the smallest code change for a well-scoped issue) and when to use it ('Use only when the fix target is explicit'), satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural terms users actually say — 'CI failure', 'reviewer comment', 'typo' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

A clear niche (smallest diff for one explicit issue) with guardrails ('Never refactor unrelated code', 'Use only when the fix target is explicit') making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation15 / 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
cobusgreyling/loop-engineering
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.