CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-library-health

Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.

65

Quality

78%

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 ./skills/audit-library-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a tight, executable workflow with copy-paste commands and a useful health checklist. It is well-structured and lean, with only minor opportunities to tighten and add an explicit re-validation feedback loop.

Suggestions

Add an explicit feedback loop after 'build-docs' regeneration, e.g. re-run 'build-docs --dry-run' to confirm currentlyInSync is true before declaring the library healthy.

Trim the 'This checks:' enumeration or fold it into the validate step to reduce tokens where Claude can derive the detail from the command itself.

Consider moving the detailed Health Checklist into a short reference file if the skill grows, to keep the SKILL.md overview lean.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; minor sentences like the 'This checks:' enumeration and gotchas could be trimmed but are useful, so not a clean 5.

4 / 5

Actionability

Every step is a copy-paste-ready executable command (e.g. 'npx ai-agent-skills validate', 'build-docs --dry-run --format json') with flag variations covering the common cases.

5 / 5

Workflow Clarity

A clear numbered 1–5 sequence with a health checklist and a conditional regenerate checkpoint; lacks an explicit re-validate-after-regenerate feedback loop, so it stops at 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized single-file sections (Goal, Guardrails, Workflow, Checklist, Gotchas) with no nesting and no external references needed; at ~67 lines it exceeds the under-50-line simple-skill exception, so not a 5.

4 / 5

Total

17

/

20

Passed

Description

75%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 cleanly answers both what and when with a natural 'Use when' trigger and a list of concrete actions. It is specific and distinct, with only minor gaps in trigger synonyms and trigger-scenario enumeration.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Run doctor, validate, check for stale skills, and verify generated docs are in sync'), with only minor coverage gaps; not a fully comprehensive 5.

4 / 5

Completeness

Explicit 'Use when checking the overall health of a skills library' (when) plus the concrete action list (what); the 'when' is present but could enumerate more concrete trigger scenarios for a 5.

4 / 5

Trigger Term Quality

Good natural keywords ('health of a skills library', 'stale skills', 'generated docs are in sync') plus tool names; a few natural synonyms are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

'skills library health' is a clear niche with distinct triggers, with only minor overlap risk against generic validation skills; not perfectly minimal conflict so not 5.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
MoizIbnYousaf/ai-agent-skills
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.