audit
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%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 effectively communicates specific capabilities across multiple audit domains and outputs, demonstrating good specificity. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others. The trigger terms are technical but miss common user phrasings.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for UI audit, interface review, accessibility check, performance analysis, or mentions a11y, responsive issues, or theme problems.'
Include common user variations of trigger terms: 'a11y', 'UI review', 'UX audit', 'design review', 'mobile responsiveness', 'dark mode', 'light mode'.
Specify the input context (e.g., 'for web applications', 'for React components') to reduce potential conflicts with other audit-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'comprehensive audit', 'accessibility, performance, theming, and responsive design', 'generates detailed report', 'severity ratings and recommendations'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does well but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains relevant technical terms like 'accessibility', 'performance', 'theming', 'responsive design', and 'audit', but missing common user variations like 'a11y', 'UI review', 'interface check', 'UX audit', or 'design review'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of audit domains (accessibility, performance, theming, responsive) provides some specificity, but 'interface quality' is broad and could overlap with general code review, accessibility-specific, or performance-specific skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive audit framework with clear structure and good workflow sequencing. However, it lacks concrete executable examples (no actual diagnostic commands or code snippets) and relies heavily on referenced skills without clear navigation. The report template is well-designed but the diagnostic phase is more descriptive than actionable.
Suggestions
Add concrete diagnostic commands or code snippets (e.g., 'Run `npx axe-core` for accessibility' or specific contrast-checking code)
Provide a direct link or path to the frontend-design skill for the anti-patterns reference
Include at least one example of a properly formatted issue entry to make the report template more concrete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (e.g., repeating 'CRITICAL' emphasis, explaining what an audit is multiple times). The checklist format is appropriate but could be tighter in places. | 2 / 3 |
Actionability | Provides clear categories and criteria to check, but lacks concrete code examples or specific commands to run diagnostics. The guidance is descriptive ('check for contrast issues') rather than executable ('run axe-core with these flags'). | 2 / 3 |
Workflow Clarity | Clear multi-step workflow: run diagnostic scan across 5 dimensions, then generate structured report with specific sections. The report template provides explicit structure with severity levels, and the skill clearly states this is audit-only with handoff to other commands for fixes. | 3 / 3 |
Progressive Disclosure | References the 'frontend-design skill' for design principles but doesn't provide clear navigation to it. The content is well-structured internally but could better signal where to find the referenced anti-patterns skill and other commands mentioned. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.