Skill review: audit a skill's quality against best practices
Give the agent an Iron Law for skill audits: structure compliance, description quality, workflow design, token efficiency, anti-pattern detection — with a strict, quote-evidence review format
- What
- Give the agent an Iron Law for skill audits: structure compliance, description quality, workflow design, token efficiency, anti-pattern detection — with a strict, quote-evidence review format
- Cost
- Free
- Needs
- a skill to review (path, name, or the current skill folder) — the skill is an audit methodology, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @sanyuan0704's skill for auditing the quality of a Claude Code skill (your own or someone else's): a 3-step workflow under one Iron Law — be specific and actionable, never say "could be improved" without stating exactly what to change and why it matters for model output quality. Step 1, load the target (read the full SKILL.md, inventory every file, count SKILL.md lines — a key metric). Step 2, analyze across five dimensions against the criteria in references/review-criteria.md: structure compliance (standard layout, frontmatter hygiene, no placeholder files), description quality (trigger keywords, no "When to Use" hiding in the body, natural-language matchability), workflow design (trackable checklists, ⚠️ REQUIRED / ⛔ BLOCKING gates, confirmation before destructive ops), token efficiency (Iron Law on top, progressive reference loading, imperative form, scripts executed not loaded), and anti-pattern detection (vague directives, placeholder residue, over-specification, giant monolithic SKILL.md, WHAT-instead-of-HOW instructions). Step 3, report: strengths first (minimum 2, quoted lines), then impact-sorted suggestions each with What / Where / Fix — in a direct, constructive, collegial tone. Honest caveats: a review methodology, not an auto-fixer — it doesn't rewrite the skill for you; and it has its own anti-patterns section, so it judges itself by the same rules it applies. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a skill to review (path, name, or the current skill folder) — the skill is an audit methodology, not software to install Install "Skill review: audit a skill's quality against best practices" for me. It gives my agent @sanyuan0704's skill-review workflow: the Iron Law (be specific and actionable), load the target (read SKILL.md, inventory files, count lines), analyze across five dimensions (structure compliance, description quality, workflow design, token efficiency, anti-pattern detection per references/review-criteria.md), and report strengths plus impact-sorted What/Where/Fix suggestions. MIT-licensed. Repository: https://github.com/sanyuan0704/sanyuan-skills/blob/main/skills/skill-review/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "skill-review". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the skill to review; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.