Create and automatically share new Claude skills with your team via Slack.
Works with
Generates properly structured skill directories with standardized SKILL.md templates, metadata, and organized subdirectories (scripts/, references/, assets/)
Validates skill format, naming conventions, and metadata completeness before packaging
Creates distributable zip files and automatically posts skill summaries to designated Slack channels using Rube integration
Enforces hyphen-case naming and YAML fron
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-shareExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-share from composiohq/awesome-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-share. Access via /skill-share 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
51.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
51.7K
stars
Use this skill when you need to:
Also use this skill when:
This skill is ideal for:
When you ask Claude to create a skill called "pdf-analyzer":
1. Creates /skill-pdf-analyzer/ with SKILL.md template
2. Generates structured directories (scripts/, references/, assets/)
3. Validates the skill structure
4. Packages the skill as a zip file
5. Posts to Slack: "New Skill Created: pdf-analyzer - Advanced PDF analysis and extraction capabilities"
This skill leverages Rube for:
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
skill-share is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in skill-share — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: skill-share is focused, and the summary matches what you get after install.
skill-share has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend skill-share for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
skill-share fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend skill-share for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
skill-share has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: skill-share is focused, and the summary matches what you get after install.
Useful defaults in skill-share — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 74