CtrlK
BlogDocsLog inGet started
Tessl Logo

review-fix-loop

This skill should be used when the user asks to "address review feedback", "fix PR comments", "close findings", "respond to reviewer notes", or "reduce review churn". Enforces a finding-to-evidence closure loop for every review round.

76

Quality

93%

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

92%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 body is a tight, well-structured process skill with clear sequencing, explicit validation checkpoints, and a feedback loop. The only gap is the absence of concrete executable command examples in the verification ladder.

Suggestions

Add one concrete example verification command per ladder tier (narrow/medium/broad) so the verification section is copy-paste ready.

Show a populated closure-table row as an example so the empty header is immediately usable.

Specify what counts as 'pass' evidence per finding (e.g., command exit code or test name) to tighten the handoff requirements.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section earns its place (execution loop, closure table, verification ladder, handoff).

5 / 5

Actionability

Provides concrete, specific guidance (closure-table schema, verification-ladder tiers, re-run control rules) but offers no copy-paste executable commands or templates, leaving minor gaps versus fully executable instruction.

4 / 5

Workflow Clarity

The 6-step execution loop is clearly sequenced with explicit verification checkpoints (steps 4 and 6), a feedback loop (re-run control), and pass/fail evidence in handoff; validation is present, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no need for external references (bundle dirs empty); per the simple-skill exception this warrants full marks for clear, navigable structure.

5 / 5

Total

19

/

20

Passed

Description

95%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 is concise yet complete: it states a concrete capability and supplies a rich set of natural user trigger phrases. It distinguishes itself clearly within the review-workflow domain. Only minor specificity gaps prevent a perfect specificity score.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Enforces a finding-to-evidence closure loop", "Parse findings into P1, P2, P3", "Build a closure table") with only minor coverage gaps, matching the anchor for listing several specific actions.

4 / 5

Completeness

Explicitly answers both what ("Enforces a finding-to-evidence closure loop for every review round") and when (the multiple quoted trigger phrases), matching the anchor for clearly answering both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say ("address review feedback", "fix PR comments", "close findings", "respond to reviewer notes", "reduce review churn"), including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (review-fix closure loop) with distinct, specific triggers that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

19

/

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
spacedriveapp/spacebot
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.