CtrlK
BlogDocsLog inGet started
Tessl Logo

vannifr/nfr-gap-audit

Use when running a systematic, self-directed skill-and-NFR audit on a website/web-app project — discovering skills from Tessl and VoltAgent, identifying non-functional-requirement gaps (performance, accessibility, security, SEO, testing, privacy, i18n, ...), and planning/implementing improvements in small, verified, committed phases. Trigger on "skill audit", "NFR audit", "audit this project for skills/gaps", "what skills am I missing", or before starting a multi-phase quality-improvement effort on a site.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%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 well-structured, multi-phase audit skill with strong workflow sequencing, explicit validation gates, and clean progressive disclosure via real reference files. The main room for improvement is tightening a few rationale clauses and inlining a concrete example command or two for copy-paste readiness.

Suggestions

Trim guard-rail rationale clauses (e.g. 'without a baseline you can't check Phase 5 against "no regression."') or move them into the relevant reference, keeping the body purely directive.

Inline one concrete example — e.g. a sample `tessl_search` query or the exact VoltAgent grep pattern — in Phase 1 so the body is copy-paste executable without opening a reference.

Consider collapsing the 'Recheck mode' and 'Phase 6 — Retrospective' subsections, which partially restate Phase ordering, to further reduce token weight.

DimensionReasoningScore

Conciseness

The body is lean and directive, assuming Claude's competence without explaining basics, but a few guard-rail rationale clauses (e.g. 'without a baseline you can't check Phase 5 against "no regression."') could be trimmed — efficient with minor over-explanation.

4 / 5

Actionability

Gives concrete file targets (package.json, tessl.json), commands (npm audit, tessl_search/install), a fetchable URL, and a commit format, but much is 'or equivalent' and the literal query/grep patterns are delegated to references, leaving minor gaps for copy-paste execution.

4 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced, and Phase 5 provides explicit validation checkpoints with a feedback loop (make change → test → build → check vs. baseline 'no regression allowed' → commit → 'all gates green before moving'), satisfying the batch/destructive validation requirement.

5 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled, one-level-deep markdown links to five real reference files (nfr-domains, project-type-reference, skill-discovery-searches, gap-checklists, improvement-plan-template), each holding content appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: it states concrete capabilities, gives multiple natural trigger phrases, answers both what and when explicitly, and carves out a distinct niche. Third-person/standard 'Use when...' voice matches the good examples and incurs no penalty.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'discovering skills from Tessl and VoltAgent', 'identifying non-functional-requirement gaps (performance, accessibility, security, SEO, testing, privacy, i18n, ...)', and 'planning/implementing improvements in small, verified, committed phases' — with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (discover skills, identify NFR gaps, plan/implement improvements) and 'when' ('Trigger on ... before starting a multi-phase quality-improvement effort') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'skill audit', 'NFR audit', 'audit this project for skills/gaps', 'what skills am I missing' — covering synonyms and common variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (systematic skill-and-NFR audit) with distinct triggers unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

20

/

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.

Reviewed

Table of Contents