CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-skills-audit

Audit the installed skill library for overlapping triggers, repeated or conflicting rules, stale references, context cost, usefulness, and dependencies when reviewing built-in, extension, and third-party skills.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A dense, well-sequenced audit workflow with strong actionability, explicit validation checkpoints, and a clean one-level reference to the report contract. The main cost is token efficiency: boundary rules and key definitions are repeated across sections and generic policy material is inlined in the main body.

Suggestions

Consolidate the read-only/no-modification rules stated in "Boundaries", "Artifact Ownership and Config Policy", and Step 5 into a single section, referencing it from the other two instead of restating it.

Define "not measured" once in Boundaries and use the label without re-explaining it in Steps 1 and 3.

Move the generic "Runtime-aware questions" delivery policy to a shared reference, or trim it to the few rules specific to this skill's questions, to reduce main-body tokens.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but it repeats rules across sections: read-only boundaries appear in "Boundaries" ("Never edit, disable, merge, move, or remove installed skills"), again in "Artifact Ownership" ("Skills, injections, manifests, settings, overrides, context, plans, evolution logs and cursors remain read-only"), and again in Step 5 ("No audited inputs may change"), while "not measured" is defined in Boundaries and re-explained in Steps 1 and 3. The long generic "Runtime-aware questions" policy adds further tighten-able material, matching the 3 anchor better than 4.

3 / 5

Actionability

Concrete guidance throughout: explicit $ARGUMENTS parsing with three flags and their semantics, invocation examples, config keys with defaults ("paths.rules_file (default .ai-factory/RULES.md)"), the layer-trace diagram, the injection-marker format "aif-ext:<extension>:<skill>:<position>:start/end", enumerated dependency-edge types, and a pre-delivery checklist. It stops short of 5 because some directives remain abstract ("Screen related groups, then compare across groups") and no worked finding example is shown inline.

4 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit validation and error-recovery paths: unknown flags mean "report valid usage and stop before analysis", missing config means "report the gap and use defaults", an unreadable file "stops dependent work with its path", and Step 5 closes with a pre-delivery checklist ("Before presenting/saving check that composition comes first; every finding has evidence and a verification task"). As a read-only analysis skill, the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

A single clearly-signaled, one-level-deep reference exists and is real ("Use [the report contract](references/aif-skills-audit/REPORT.md)" → references/aif-skills-audit/REPORT.md), and the body is well-sectioned. It is not 5 because the 226-line body inlines generic policy sections ("Runtime-aware questions", "Shared project skill-context") that read as orthogonal boilerplate, and parts of the six-dimension analysis detail could live in a reference.

4 / 5

Total

16

/

20

Passed

Description

83%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 specific, actionable, and clearly scoped to a distinct niche, enumerating six concrete audit dimensions. Its main weaknesses are the missing natural-language synonyms for trigger terms and a when-clause that describes skill scope rather than explicit user triggers.

DimensionReasoningScore

Specificity

"Audit the installed skill library for overlapping triggers, repeated or conflicting rules, stale references, context cost, usefulness, and dependencies" enumerates six concrete audit actions, comprehensively covering the domain. It exceeds the 4 anchor because the action list has no meaningful coverage gaps for a skill-library audit.

5 / 5

Completeness

Both parts are present: the what is the six enumerated audit dimensions, and the when is "when reviewing built-in, extension, and third-party skills". It is not 5 because the when-clause describes the scope of skills rather than concrete user trigger phrases (e.g., "Use when the user asks to review their installed skills").

4 / 5

Trigger Term Quality

Natural keywords like "audit", "skill library", "overlapping triggers", "stale references", and "dependencies" map well to what a user would say. It falls short of the 5 anchor because common synonyms and variations (e.g., "review my skills", "duplicate skills", "clean up skills") are missing.

4 / 5

Distinctiveness Conflict Risk

"Audit the installed skill library" is a clear niche with triggers ("overlapping triggers", "built-in, extension, and third-party skills") unlikely to fire for unrelated skills. Meta-auditing installed skills is distinct even from closely related review skills, so the 5 anchor fits better than 4.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-skills-audit/SKILL.md

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.