uinaf/skill-audit
Audit existing skills with Tessl scoring, metadata and trigger-coverage checks, repo conventions, and skill-authoring best practices. Use when creating or revising a skill, triaging weak self-activation, or comparing a skill against source-repo guidance such as `AGENTS.md`, `CLAUDE.md`, or repo rules, plus external skill guidance. Do not use to verify general application code or to rewrite unrelated docs.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly defines a specific niche (skill auditing), lists concrete actions, provides explicit 'Use when' and 'Do not use' clauses, and includes natural trigger terms. The negative boundary ('Do not use to verify general application code or to rewrite unrelated docs') is a particularly effective addition for disambiguation. Minor improvement could include mentioning file extensions like .md for skill files, but overall this is excellent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Tessl scoring', 'metadata and trigger-coverage checks', 'repo conventions', and 'skill-authoring best practices'. These are concrete, identifiable audit activities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (audit skills with scoring, metadata checks, conventions, best practices) and 'when' (creating/revising skills, triaging weak self-activation, comparing against repo guidance). Also includes explicit 'Do not use' guidance, which strengthens the 'when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'creating or revising a skill', 'weak self-activation', 'AGENTS.md', 'CLAUDE.md', 'repo rules', 'skill guidance'. Also includes negative triggers ('Do not use to verify general application code') which help with disambiguation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — auditing skills specifically with Tessl scoring and skill-authoring conventions. The explicit 'Do not use' clause further reduces conflict risk with general code review or documentation skills. Unlikely to be confused with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong authoring practices. It's concise yet comprehensive, with a clear multi-step workflow that includes validation checkpoints (Tessl scoring before and after edits). The progressive disclosure is well-executed with appropriate delegation to reference files, and the handoffs section cleanly bounds the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining concepts Claude already knows, uses terse bullet points, and every section earns its place. The principles, workflow steps, and output format are all stated without padding. | 3 / 3 |
Actionability | Provides concrete CLI commands (e.g., `npx tessl skill review --json skills/<name>`), specific file paths to check, concrete examples of weak vs. strong metadata, and explicit failure signs to look for. The guidance is specific and directly executable. | 3 / 3 |
Workflow Clarity | The six-step workflow is clearly sequenced with explicit validation (run Tessl first, then audit dimensions in order, synthesize changes, rerun Tessl). The feedback loop of fix → rerun → report is explicitly stated. The 'Before You Start' section provides clear prerequisites and decision points for which Tessl loop to use. | 3 / 3 |
Progressive Disclosure | Core workflow stays in SKILL.md while dense rubrics and best practices are properly delegated to `references/scorecard.md` and `references/best-practices.md` with clear one-level-deep links. The handoffs section cleanly directs adjacent concerns to other skills. Content is well-organized for discovery. | 3 / 3 |
Total | 12 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents