skill-audit
Audit and score any skill against best practices. Use when: audit this skill, review this skill, check this skill, score this skill, is this skill good, skill health check, skill review, rate this skill. Takes a skill directory path, evaluates structure/content/patterns against a checklist, and outputs a scorecard with specific fixes.
Best use case
skill-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit and score any skill against best practices. Use when: audit this skill, review this skill, check this skill, score this skill, is this skill good, skill health check, skill review, rate this skill. Takes a skill directory path, evaluates structure/content/patterns against a checklist, and outputs a scorecard with specific fixes.
Teams using skill-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-audit Compares
| Feature / Agent | skill-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit and score any skill against best practices. Use when: audit this skill, review this skill, check this skill, score this skill, is this skill good, skill health check, skill review, rate this skill. Takes a skill directory path, evaluates structure/content/patterns against a checklist, and outputs a scorecard with specific fixes.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill Audit Evaluate a skill against the checklist in [references/checklist.md](references/checklist.md). Read that file first. ## Process 1. **Locate the skill.** Get the path from the user. Read the entire directory: SKILL.md, all subdirectories, all files. 2. **Run the checklist.** Score each of the 10 items (S1-S4, C1-C4, D1-D2). Each item is 1 point. Binary: pass or fail. 3. **Classify the skill type.** Determine which type it is (Library & API Reference, Product Verification, Data Fetching & Analysis, Business Process & Team Automation, Code Scaffolding & Templates). If it doesn't fit cleanly, note that. 4. **Generate the scorecard.** Use the format below. 5. **Offer to fix.** List recommended actions in priority order. Ask before making any changes. ## Scorecard Format ``` # Skill Audit: [skill-name] ## Type: [skill type] ## Score: [X]/10 ### ✅ Passing - [item]: [brief note on what's good] ### ⚠️ Warnings (technically passes but fragile or could be better) - [item]: [what's borderline and why] ### ❌ Failing - [item]: [what's wrong + specific fix] ### Recommended Actions (priority order) 1. [highest impact fix] 2. [next fix] 3. [next fix] ``` ## Scoring Rules - Be honest. A typical first-draft skill scores 4-6/10. - Don't inflate scores to be nice. The audit is useless if everything passes. - For D2 (Advanced Patterns): score as pass if the skill doesn't need those patterns. Only fail if it needs them and doesn't use them. - When in doubt, fail. It's better to flag something that turns out fine than miss a real issue. ## Gotchas - Don't confuse this with skill-improver. Skill-improver runs the skill repeatedly and evals output quality. This audits the skill's structure and design. - Don't confuse this with skill-creator. Skill-creator builds skills. This reviews them. - Some skills are intentionally minimal (a 20-line SKILL.md with no references). That's fine if the task is simple. Don't penalize brevity when the skill's job is small. - The description field is the #1 thing people get wrong. It's a routing instruction for the model, not a human-readable summary. Audit it critically.
Related Skills
audit
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
aso-audit
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
writer
Write content in Eric's voice — articles, blog posts, tweets, social media posts, marketing copy, newsletter drafts. Loads WRITING-STYLE.md and enforces kill phrases.
positioning-angles
Use when defining product positioning, choosing strategic angles, crafting value propositions, competitive positioning, product messaging, differentiation strategy, or go-to-market angles. Also use for 'how should I position my app', 'what angle should I use', 'painkiller vs vitamin', or 'market positioning'.
outline-generator
Use when generating outlines, article structures, content outlines, blog outlines, planning article sections, structuring posts, breaking down topics into sections, or organizing ideas for long-form content. Also use for 'outline this', 'structure this article', or 'plan the sections'.
last30days-open
Use only when the user explicitly asks for the open variant of last30days, including watchlists, briefings, and history queries. Sources: Reddit, X, YouTube, web.
last30days
Use when researching what happened in the last 30 days on a topic. Also triggered by 'last30'. Sources: Reddit, X, YouTube, web. Produces expert-level summary with copy-paste-ready prompts.
hooks
Use when generating hooks, headlines, titles, and scroll-stopping openers for content. Also use when analyzing viral posts, Reels, TikToks, YouTube Shorts, or successful social examples to extract reusable hook patterns and improve hook guidance.
evaluate-content
Use when judging content quality OR editing/improving existing copy: shareability, readability, voice, cuttability, angle, copy sweeps.
editor-in-chief
Use when a first draft is complete and all Phase 1 gates are done: topic selected (seo-research), title approved (hooks), outline approved (outline-generator), draft written (writer). Runs autonomous diagnosis-prescribe-rewrite loop before Substack.
copywriting
Write or improve marketing copy for any surface: pages, ads, app stores, landing pages, TikTok/Meta scripts, push notifications, UGC. Combines page copy frameworks with direct response principles.
content-strategy
Use when building content strategy: hooks, angles, and ideas from what's trending now. Covers organic and paid creative across TikTok, X, YouTube, Meta, LinkedIn.