Review and improve Claude Code skills against official best practices.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-reviewerExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-reviewer from daymade/claude-code-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-reviewer. Access via /skill-reviewer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
784
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
784
stars
Review and improve Claude Code skills against official best practices.
Before using this skill, ensure skill-creator is installed for automated validation.
Auto-install sequence:
# 1. Check if skill-creator exists
SKILL_CREATOR=$(find ~/.claude/plugins/cache -name "skill-creator" -type d 2>/dev/null | head -1)
# 2. If not found, install it
if [ -z "$SKILL_CREATOR" ]; then
claude plugin marketplace add https://github.com/daymade/claude-code-skills
claude plugin install skill-creator@daymade-skills
SKILL_CREATOR=$(find ~/.claude/plugins/cache -name "skill-creator" -type d 2>/dev/null | head -1)
fi
echo "skill-creator location: $SKILL_CREATOR"
Check your own skill before publishing.
Automated validation (run after setup):
# Quick validation
python3 "$SKILL_CREATOR"/*/quick_validate.py <target-skill>
# Security scan
python3 "$SKILL_CREATOR"/*/security_scan.py <target-skill> --verbose
Manual evaluation: See references/evaluation_checklist.md.
Evaluate someone else's skill repository.
Review Workflow:
- [ ] Clone repository to /tmp/
- [ ] Read ALL documentation first
- [ ] Identify author's intent
- [ ] Run evaluation checklist
- [ ] Generate improvement report
Fork, improve, and submit PR to external skill repository.
Auto-PR Workflow:
- [ ] Fork repository (gh repo fork)
- [ ] Create feature branch
- [ ] Apply additive improvements only
- [ ] Self-review: respect check passed?
- [ ] Create PR with detailed explanation
| Category | Check | Status |
|---|---|---|
| Frontmatter | name present? | |
| description present? | ||
| description in third-person? | ||
| includes trigger conditions? | ||
| Instructions | imperative form? | |
| under 500 lines? | ||
| workflow pattern? | ||
| Resources | no hardcoded paths? | |
| scripts have error handling? |
Full checklist: references/evaluation_checklist.md
When improving external skills, NEVER:
ALWAYS:
❌ "Removed metadata.json (non-standard)"
✅ "Added marketplace.json (metadata.json preserved)"
❌ "Rewrote README in English"
✅ "Added README.en.md (Chinese preserved as default)"
# Before
description: Browse YouTube videos and summarize them.
# After
description: Browses YouTube videos and generates summaries. Use when...
# Before
description: Processes PDF files.
# After
description: Extracts text from PDFs. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
Add checklist for complex tasks:
## Workflow
Copy this checklist:
\`\`\`
Task Progress:
- [ ] Step 1: ...
- [ ] Step 2: ...
\`\`\`
mkdir -p .claude-plugin
# Create marketplace.json from template
See references/marketplace_template.json.
When submitting PRs to external repos:
❌ "Your skill doesn't follow best practices"
✅ "This PR aligns with best practices for better discoverability"
❌ "Fixed the incorrect description"
✅ "Improved description with trigger conditions"
Template: references/pr_template.md
Before submitting any PR:
Respect Check:
- [ ] No files deleted?
- [ ] No functionality removed?
- [ ] Original language preserved?
- [ ] Author's design decisions respected?
- [ ] All changes are additive?
- [ ] PR explains the "why"?
references/evaluation_checklist.md - Full evaluation checklistreferences/pr_template.md - PR description templatereferences/marketplace_template.json - marketplace.json templateMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for skill-reviewer matched our evaluation — installs cleanly and behaves as described in the markdown.
skill-reviewer reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: skill-reviewer is focused, and the summary matches what you get after install.
Registry listing for skill-reviewer matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in skill-reviewer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend skill-reviewer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: skill-reviewer is focused, and the summary matches what you get after install.
Registry listing for skill-reviewer matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in skill-reviewer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
skill-reviewer has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 74