eval-skills
FeaturedAudit all skills in the current project for frontmatter completeness, effort level appropriateness, allowed-tools scoping, and content quality. Produces a scored report with effort-level recommendations for each skill. Use when onboarding to a new project, reviewing skill quality before shipping, or adding effort fields to an existing skill library.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- FlorianBruniaux
- Repository
- FlorianBruniaux/claude-code-ultimate-guide
- Created
- 7 months ago
- Last Updated
- today
- Language
- Python
- License
- CC-BY-SA-4.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
skills-eval
Evaluate Claude skill quality through auditing. Use when reviewing or auditing skills.
skill-auditor
Audit a SKILL.md or REFERENCE file, score it 0–10, identify major and minor findings, and generate copy-paste improvements. Use when reviewing a new skill before merging, auditing an existing skill for gaps, checking cross-skill consistency, or validating that a skill meets the Quality-Engineering-Skills framework standards. Triggers: audit this skill, score this SKILL.md, review reference file, check skill quality, find gaps in skill, validate skill before PR.
skill-evaluator
Audit an existing SKILL.md for rule adherence — does the text actually land when Claude runs it? Use when the user wants a behavioral review of a shipped skill. Outputs: failure classification by fix layer (skill text / rubric / brief / fixture) and targeted rule-text diffs. Trigger ON: "audit this skill", "stress-test my skill", "does this skill actually work", "find gaps in this skill", "what's broken in this skill", "validate rule adherence", "review this skill end-to-end", or uploading a SKILL.md for behavior review. Do NOT trigger on: "build a skill", "create a skill from scratch", "benchmark this skill", "evaluate skill quality", "compare versions", "optimize trigger phrases", or "measure variance" — those are all `skill-creator`. If the request mixes both, start with `skill-creator` and chain here. Hard boundary: `skill-creator` builds, benchmarks, measures variance, and optimizes triggering; this skill does NONE of those — it asks "does the text land?".