Modern file and content search.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfile-searchExecute the skills CLI command in your project's root directory to begin installation:
Fetches file-search from 0xdarkmatter/claude-mods 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 file-search. Access via /file-search 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
16
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
16
stars
Modern file and content search.
# Find by name
fd config # Files containing "config"
fd -e py # Python files
# By type
fd -t f config # Files only
fd -t d src # Directories only
# Exclude
fd -E node_modules # Exclude directory
fd -E "*.min.js" # Exclude pattern
# Execute command
fd -e py -x wc -l # Line count per file
# Simple search
rg "TODO" # Find TODO
rg -i "error" # Case-insensitive
# By file type
rg -t py "import" # Python files only
rg -t js -t ts "async" # JS and TS
# Context
rg -C 3 "function" # 3 lines before/after
# Output modes
rg -l "TODO" # File names only
rg -c "TODO" # Count per file
# Find and select
fd | fzf
# With preview
fd | fzf --preview 'bat --color=always {}'
# Multi-select
fd -e ts | fzf -m | xargs code
# Find files, search content
fd -e py -x rg "async def" {}
# Search, select, open
rg -l "pattern" | fzf --preview 'rg -C 3 "pattern" {}' | xargs vim
| Task | Command |
|---|---|
| Find TS files | fd -e ts |
| Find in src | fd -e ts src/ |
| Search pattern | rg "pattern" |
| Search in type | rg -t py "import" |
| Files with match | rg -l "pattern" |
| Count matches | rg -c "pattern" |
| Interactive | fd | fzf |
| With preview | fd | fzf --preview 'bat {}' |
| Tip | Why |
|---|---|
Both respect .gitignore |
Auto-skip node_modules, dist |
Use -t over -g |
Type flags are faster |
| Narrow the path | rg pattern src/ faster |
Use -F for literals |
Avoids regex overhead |
For detailed patterns, load:
./references/advanced-workflows.md - Git integration, shell functions, power workflowsMake 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.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added file-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend file-search for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for file-search matched our evaluation — installs cleanly and behaves as described in the markdown.
file-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: file-search is the kind of skill you can hand to a new teammate without a long onboarding doc.
file-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in file-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
file-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
file-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
file-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 75