CtrlK
BlogDocsLog inGet started
Tessl Logo

sig-audit

Measure Fallow maintainability using the repository's SIG system properties and update the evidence-backed audit report.

59

Quality

68%

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 ./.claude/skills/sig-audit/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.

The body is an efficient, well-sequenced audit workflow with a verification step, but it stops at high-level instructions without the specific commands or script paths that would make it copy-paste executable. As a simple instruction skill it organizes content well.

Suggestions

Include the concrete commands or script invocations for running measurements and repository verification so the steps are directly executable.

Add an explicit feedback loop (run measurement -> if it fails or lacks evidence -> fix -> rerun) around steps 2 and 6.

Specify where raw evidence is recorded and how current scores are persisted so step 3 is unambiguous.

DimensionReasoningScore

Conciseness

A lean ~10-line numbered workflow where every line carries actionable instruction and no tokens are spent explaining concepts Claude already knows.

5 / 5

Actionability

Steps state concrete intent ('Run every supported property measurement', 'Run repository verification') but lack the specific commands, script paths, or copy-paste detail needed to execute, leaving guidance high-level rather than fully executable.

3 / 5

Workflow Clarity

A clear numbered sequence with a terminal verification checkpoint (step 6) and a supported-claims guard (step 5), though an explicit validate-fix-retry feedback loop is only weakly implied rather than spelled out.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and organized as one coherent ordered list, which meets the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

57%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 identifies a specific niche and two concrete actions but omits any 'Use when' trigger guidance and relies on niche jargon rather than natural user terms. It is solid but not exemplary.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases users would say (e.g. 'Use when auditing Fallow maintainability, refreshing SIG scores, or updating the audit report').

Replace or supplement jargon with more common synonyms so users can trigger the skill with everyday phrasing.

List a few more concrete actions (e.g. 'compare revisions, record evidence locations, run repository verification') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain (Fallow maintainability, SIG system properties) plus two concrete actions ('Measure', 'update the...audit report') but does not enumerate several specific actions, matching the 1-2-concrete-actions anchor.

3 / 5

Completeness

States a clear 'what' (measure maintainability, update the audit report) but provides no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant but jargon-heavy keywords ('Fallow maintainability', 'SIG system properties', 'audit report') and is missing the natural phrasings or synonyms a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (SIG audit of Fallow maintainability) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.