skill-finder
Full-featured Agent Skills management tool.
Works with
4
total installs
4
this week
10
GitHub stars
0
upvotes
Install Skill
Run in your terminal
4
installs
4
this week
10
stars
Installation Guide
How to use skill-finder on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
skill-finder
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches skill-finder from aktsmm/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-finder. Access via /skill-finder in your agent's command palette.
Security Notice
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.
Documentation
Skill Finder
Full-featured Agent Skills management tool.
When to Use
- Find skill, search skill, install skill, スキル検索
- Looking for skills for a specific task or domain
- Finding and installing skills locally
- Managing favorites with star feature
Features
| Feature | Description |
|---|---|
| Search | Local index + GitHub API + Web fallback |
| Tags | Filter by category (#azure #bicep) |
| Install | Download to local directory |
| Star | Mark and manage favorites |
| Update | Sync all sources from GitHub |
Quick Start
# Search
python scripts/search_skills.py "pdf"
python scripts/search_skills.py "#azure #development"
# Management
python scripts/search_skills.py --info skill-name
python scripts/search_skills.py --install skill-name
python scripts/search_skills.py --star skill-name
# Index
python scripts/search_skills.py --update
python scripts/search_skills.py --add-source https://github.com/owner/repo
Command Reference
| Command | Description |
|---|---|
<query> |
Search skills by keyword |
#tag |
Filter by category |
--info SKILL |
Show skill details |
--install SKILL |
Download skill locally |
--star SKILL |
Add to favorites |
--list-starred |
Show favorites |
--similar SKILL |
Find similar skills |
--update |
Update index from sources |
--add-source URL |
Add new source repository |
--stats |
Show index statistics |
--check |
Verify dependencies |
Files
| File | Description |
|---|---|
scripts/search_skills.py |
Python script |
scripts/Search-Skills.ps1 |
PowerShell script |
references/skill-index.json |
Skill index (220+ skills) |
references/starred-skills.json |
Your starred skills |
Requirements
→ references/setup-guide.md for installation
| Tool | Required |
|---|---|
GitHub CLI (gh) |
2.0+ |
| curl | Any |
| Python or PowerShell | One of them |
Agent Instructions
→ references/agent-instructions.md for complete guide
Core Rules
- Use "Do it? Yes/No?" style proposals
- NEVER show commands to users - execute silently
- ALWAYS include proposal block after search results
Search Response Format
{N} repos, {M} skills searched (last updated: {date})
| Skill | Description | Source | Trust |
| ----- | ----------- | ------ | ----- |
| ... | ... | ... | ... |
**Next?**
1. Install?
2. Details?
3. Update index? (last: {date})
4. Web search?
Trust Levels
| Type | Badge | Description |
|---|---|---|
official |
Official | Anthropic / GitHub 公式 |
awesome-list |
Curated | キュレーションリスト |
community |
Community | コミュニティ製（自己責任） |
Done Criteria
- Search query returns results
- Skill installed to local directory (if requested)
- Index updated successfully (if requested)
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
349mattpocock/skills
premortem
193parcadei/continuous-claude-v3
deslop
113cursor/plugins
framer-motion
92pproenca/dot-skills
write-a-prd
87mattpocock/skills
wordpress-elementor
82jezweb/claude-skills
Reviews
- SSoo Malhotra★★★★★Dec 24, 2024
Keeps context tight: skill-finder is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNia Abbas★★★★★Dec 20, 2024
We added skill-finder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- NNoah Wang★★★★★Dec 4, 2024
skill-finder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- HHenry Malhotra★★★★★Dec 4, 2024
skill-finder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- HHiroshi Martinez★★★★★Dec 4, 2024
skill-finder has been reliable in day-to-day use. Documentation quality is above average for community skills.
- NNia Rahman★★★★★Dec 4, 2024
Solid pick for teams standardizing on skills: skill-finder is focused, and the summary matches what you get after install.
- DDev Thompson★★★★★Nov 23, 2024
Solid pick for teams standardizing on skills: skill-finder is focused, and the summary matches what you get after install.
- OOlivia Mensah★★★★★Nov 23, 2024
Keeps context tight: skill-finder is the kind of skill you can hand to a new teammate without a long onboarding doc.
- BBenjamin Sanchez★★★★★Nov 23, 2024
skill-finder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- BBenjamin Ramirez★★★★★Nov 15, 2024
skill-finder has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 62
Discussion
Comments — not star reviews- No comments yet — start the thread.