Tools for creating, auditing, and maintaining Claude Code skills. Essential for anyone building skills or forking this repository.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-developmentExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-development from jezweb/claude-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-development. Access via /skill-development 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
697
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
697
stars
Tools for creating, auditing, and maintaining Claude Code skills. Essential for anyone building skills or forking this repository.
/create-skill <name>Scaffold a new skill from templates.
What it does:
templates/skill-skeleton/ to skills/<name>/Usage: /create-skill my-new-skill
/review-skill <name>Quality review and audit of an existing skill.
What it does:
Usage: /review-skill cloudflare-worker-base
/audit [name]Multi-agent audit swarm for parallel skill verification.
What it does:
Usage:
/audit - Audit all skills/audit cloudflare-* - Audit matching skills/audit-skill-deep <name>Deep content validation against official documentation.
What it does:
Usage: /audit-skill-deep tailwind-v4-shadcn
/deep-audit <name>Extended deep audit with comprehensive doc scraping.
What it does:
archive/audit-cache/Usage: /deep-audit openai-api
/scrape-api <docs-url> [skill-name]Generate a skill from API documentation URL.
What it does:
Usage:
/scrape-api https://api.example.com/docs my-api/scrape-api https://rocketdotnet.readme.io/ (auto-detects name: rocket-net-api)Supported Platforms:
This skill includes templates for creating new skills:
| Template | Purpose |
|---|---|
templates/skill-skeleton/ |
Complete skill directory to copy |
templates/SKILL-TEMPLATE.md |
SKILL.md with TODOs to fill |
templates/README-TEMPLATE.md |
README.md with keywords section |
templates/skill-metadata-v2.yaml |
YAML frontmatter reference |
templates/RESEARCH_FINDINGS_TEMPLATE.md |
Research output format |
templates/CONTENT_AUDIT_TEMPLATE.md |
Audit checklist |
# Option 1: Use /create-skill (recommended)
/create-skill my-new-skill
# Option 2: Manual copy
cp -r skills/skill-development/templates/skill-skeleton/ skills/my-new-skill/
# Then fill in the TODOs
Skills should meet these criteria before publishing:
name and descriptionFull checklist: See ONE_PAGE_CHECKLIST.md in repo root.
This skill provides agents for automated skill maintenance:
| Agent | Purpose |
|---|---|
skill-creator |
Scaffold new skills with proper structure |
api-doc-scraper |
Generate skills from API documentation URLs |
version-checker |
Verify package versions are current |
content-accuracy-auditor |
Compare skill content vs official docs |
code-example-validator |
Validate code examples are syntactically correct |
api-method-checker |
Verify documented API methods exist |
doc-validator |
Check documentation quality |
bulk-updater |
Apply changes across multiple skills |
These agents are in .claude/agents/ (repo-level) and agents/ (skill-bundled) and used by the commands.
1. /create-skill my-skill
2. Fill in TODOs in SKILL.md
3. Add templates, references, scripts as needed
4. /review-skill my-skill
5. Fix any issues
6. Test: /plugin install ./skills/my-skill
7. Commit and push
1. /audit # Quick check all skills
2. /audit-skill-deep my-skill # Deep check specific skill
3. Review findings
4. Fix issues or document as known limitations
5. Update metadata.last_verified date
1. Run: ./scripts/check-all-versions.sh
2. Review VERSIONS_REPORT.md
3. /audit for all skills needing updates
4. Update package versions
5. Test affected skills
6. Commit: "chore: quarterly version updates"
If you've forked this repo to maintain your own skills:
/plugin install ./skills/skill-development.claude/agents/ for your needsgit fetch upstream && git merge upstream/mainThe tooling is designed to work standalone - you don't need the full repo to use these commands.
Make 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.
jezweb/claude-skills
greedychipmunk/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
skill-development reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: skill-development is focused, and the summary matches what you get after install.
Registry listing for skill-development matched our evaluation — installs cleanly and behaves as described in the markdown.
skill-development is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: skill-development is focused, and the summary matches what you get after install.
skill-development has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added skill-development from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
skill-development fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: skill-development is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend skill-development for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 71