CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-hygiene

Read before writing or editing any SKILL.md, or any research/audit doc in .gemini/internal-docs/research/. Covers the two standing rules for living-reference prose - state current behavior only, and prefer plain, short wording - plus the grep sweep to run before calling a doc clean. PRDs are the deliberate exception (they keep a correction trail).

62

Quality

73%

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/skill-hygiene/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 lean, highly actionable reference with a concrete grep sweep and smell/fix table, well-organized into clear sections. Its main weakness is the sweep workflow lacking an explicit validation/re-verify checkpoint for a batch operation.

Suggestions

Add an explicit validation step to the sweep workflow, e.g. re-run the grep after fixes to confirm zero remaining violations before calling the skill clean.

Trim the prd-writing contrast paragraph in 'What a skill is, and isn't' to a single sentence referencing prd-writing, since the exception is already restated later.

Consider a one-line 'verify the three paired copies match' checkpoint after the sync guidance, since check_skill_pairs.py only flags some-but-not-all changes.

DimensionReasoningScore

Conciseness

Dense with real information, a compact smell-to-fix table, and a lean copy-paste grep command; minor philosophical justifications (the prd-writing contrast paragraph) could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Fully executable copy-paste grep sweep, a concrete smell/fix table with real example phrases, specific archive steps (research_old/), and a real script reference (scripts/check_skill_pairs.py) cover the common cases.

5 / 5

Workflow Clarity

The sweep is sequenced (run grep, read hits in context, fix) but lacks an explicit validate/re-verify checkpoint, and the grep sweep is a batch operation across skill trees, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

A self-contained, well-sectioned document under ~50 lines with clear headers and no nested reference chains, only one-level contextual pointers to related skills; meets the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

67%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 conveys both the skill's purpose and its trigger conditions, with concrete actions and a distinct niche. It is held back from the top band by some jargon ("living-reference prose") and rule-framed rather than action-enumerated phrasing.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("state current behavior only", "prefer plain, short wording", "grep sweep to run before calling a doc clean"), with only minor coverage gaps; not a 5 because the actions are framed as rules rather than a fully enumerated capability list.

4 / 5

Completeness

Explicitly answers both what (two rules plus the grep sweep) and when ("Read before writing or editing any SKILL.md, or any research/audit doc...") with concrete triggers; not a 5 because the what is stated as rules rather than a crisp capability statement.

4 / 5

Trigger Term Quality

Natural phrases like "writing or editing any SKILL.md" and "research/audit doc" appear, but "living-reference prose" and "standing rules" are jargon and common synonyms are missing; not a 4 because keyword coverage is incomplete.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (skill/doc hygiene) with specific paths and explicitly carves out the PRD exception to avoid overlap with prd-writing; not a 5 because it shares the broader "living-reference prose" framing with adjacent doc skills.

4 / 5

Total

15

/

20

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
netalertx/NetAlertX
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.