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:
Quick answer
Skill review is a free Muse skill for auditing a Claude Code skill's quality under one Iron Law: be specific and actionable, never say something could be improved without stating exactly what to change and why it matters. Its three steps load the target, analyze five dimensions including structure, description quality, workflow design, token efficiency and anti-patterns, then report.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 08b6572Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/sanyuan0704/sanyuan-skills/08b6572ef108f22d4e8a3ecf9182a4bbef097744/skills/skill-review/SKILL.md Pinned version: install the code at commit 08b6572ef108f22d4e8a3ecf9182a4bbef097744 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 08b6572 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.