
Component Search
- 1 installs
- 27 repo stars
- Updated April 25, 2026
- girijashankarj/cursor-handbook
Searches across cursor-handbook rules, agents, commands, and skills for a term or topic using a bundled grep-based script.
About
Searches all cursor-handbook component types (rules, agents, commands, skills) for a keyword via a bundled shell script. A developer uses it to locate where a topic is defined in the handbook.
- Bundled search-components.sh runs a grep across the .cursor directory
- Finds rules, agents, skills, and commands matching a term
Component Search by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,476 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 22, 2026 (Skillselion catalog sync)
npx skills add https://github.com/girijashankarj/cursor-handbook --skill component-searchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 27 |
| Last updated | April 25, 2026 |
| Repository | girijashankarj/cursor-handbook ↗ |
What it does
Searches across cursor-handbook rules, agents, commands, and skills for a term or topic using a bundled grep-based script.
Files
Skill: Component Search
Search across all cursor-handbook component types (rules, agents, commands, skills) to find files matching a term or topic.
Trigger
When the user asks to find a rule, agent, skill, or command by keyword — or wants to know where a specific topic is covered in the handbook.
Prerequisites
- [ ] cursor-handbook
.cursor/directory exists - [ ]
grepcommand available (standard on macOS/Linux)
Usage
Run the bundled script:
scripts/search-components.sh <search-term>Examples
Find all components related to "security":
scripts/search-components.sh securityFind components mentioning "database":
scripts/search-components.sh databaseFind components referencing "correlationId":
scripts/search-components.sh correlationIdSteps
Step 1: Identify Search Term
- [ ] Determine what the user is looking for
- [ ] If vague, suggest specific terms or ask for clarification
Step 2: Run Search
- [ ] Execute
scripts/search-components.sh <term>using the Shell tool - [ ] Capture output grouped by component type
Step 3: Present Results
- [ ] Format results as a table grouped by type (rules, agents, commands, skills)
- [ ] Include file paths and brief descriptions where available
- [ ] Highlight the most relevant matches
Step 4: Suggest Actions
- [ ] Offer to read the most relevant file(s)
- [ ] Suggest related search terms if few results found
- [ ] Recommend creating a new component if nothing exists for the topic
How It Works
The script searches recursively through .cursor/rules/, .cursor/agents/, .cursor/commands/, and .cursor/skills/ using case-insensitive grep. Results are grouped by component type.
Rules
- Search is case-insensitive by default
- Only searches within
.cursor/subdirectories - Large result sets are not truncated — filter with a more specific term if needed
Completion
List of matching files grouped by component type, with suggestions for next steps.
If a Step Fails
- No results: Suggest alternative search terms, check spelling, or broader keywords
- `.cursor/` not found: Verify the user is in the correct project root
- Too many results: Suggest a more specific search term
#!/bin/bash
# Search for a term across rules, agents, commands, and skills.
set -e
QUERY="${1:-}"
if [ -z "$QUERY" ]; then
echo "Usage: $0 <search-term>"
exit 1
fi
ROOT=".cursor"
echo "Searching for: $QUERY"
echo ""
for dir in rules agents commands skills; do
if [ -d "$ROOT/$dir" ]; then
echo "=== $dir ==="
grep -ril "$QUERY" "$ROOT/$dir" 2>/dev/null || true
echo ""
fi
done