CtrlK
BlogDocsLog inGet started
Tessl Logo

sig-audit-loop

Iteratively improve Fallow maintainability using measured SIG audit deltas, retaining only changes that improve the targeted property without regressions.

60

Quality

69%

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 ./.agents/skills/sig-audit-loop/SKILL.md
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 an exemplary lean, well-sequenced audit loop with explicit validation and feedback gating. The only minor gap is that the measurement commands beyond `sig-audit` are not fully spelled out.

DimensionReasoningScore

Conciseness

Nine lean lines with no padding or explanation of concepts Claude already knows; every line carries an instruction and the token budget is respected.

5 / 5

Actionability

Names concrete commands (`sig-audit`, `review`) and gives specific, actionable steps (measure before/after with identical settings, keep only when target improves and verification is green), though the exact measurement invocation beyond `sig-audit` is left implicit.

4 / 5

Workflow Clarity

A clear numbered sequence with an explicit validation checkpoint ("verification remains green"), a keep/discard feedback loop, and a repeat-until-termination condition; the closing guard against mixing unrelated cleanup reinforces the loop.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and organized as a clean numbered list with a closing constraint — meeting the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

46%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 domain-specific and clear about what it does, but lacks an explicit use-when trigger and leans on technical jargon over natural user phrasing. Distinctiveness is strong thanks to the narrow Fallow/SIG niche.

Suggestions

Add a "Use when..." clause with natural triggers (e.g., "Use when improving Fallow maintainability or when SIG audit results show a weak property").

Surface more concrete actions (e.g., "select a weak SIG property, make a bounded change, re-measure, keep only improvements") to lift specificity.

Include common user phrasings or synonyms ("maintainability", "SIG rating", "audit") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("Fallow maintainability", "SIG audit deltas") and a couple concrete actions (measure deltas, retain only improving changes), but the verbs "improve" and "retaining" stay abstract and coverage is not comprehensive.

3 / 5

Completeness

It clearly states what the skill does (iteratively improve maintainability via measured deltas, retaining only non-regressing changes) but provides no explicit "when to use it" trigger, capping completeness at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

The terms ("SIG audit", "Fallow maintainability", "audit deltas") are domain jargon with no natural "Use when..." phrasing a user would say; it leans technical rather than covering common user phrasings.

2 / 5

Distinctiveness Conflict Risk

The Fallow/SIG-audit niche is specific and unlikely to fire for unrelated skills, though the broad "improve maintainability" framing leaves minor overlap with general refactoring skills.

4 / 5

Total

12

/

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
fallow-rs/fallow
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.