This skill provides a complete walkthrough to get GrepAI running and searching your code in 5 minutes.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongrepai-quickstartExecute the skills CLI command in your project's root directory to begin installation:
Fetches grepai-quickstart from yoanbernabeu/grepai-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 grepai-quickstart. Access via /grepai-quickstart 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
15
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
15
stars
This skill provides a complete walkthrough to get GrepAI running and searching your code in 5 minutes.
brew install yoanbernabeu/tap/grepai
curl -sSL https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.sh | sh
irm https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.ps1 | iex
Verify: grepai version
brew install ollama
ollama serve &
ollama pull nomic-embed-text
curl -fsSL https://ollama.com/install.sh | sh
ollama serve &
ollama pull nomic-embed-text
Verify: curl http://localhost:11434/api/tags
Navigate to your project and initialize GrepAI:
cd /path/to/your/project
grepai init
This creates .grepai/config.yaml with default settings:
nomic-embed-text modelStart the watch daemon to index your code:
grepai watch
What happens:
.gitignore).grepai/index.gobFirst indexing output:
🔍 GrepAI Watch
Scanning files...
Found 245 files
Processing chunks...
████████████████████████████████ 100%
Indexed 1,234 chunks
Watching for changes...
For long-running projects:
# Start in background
grepai watch --background
# Check status
grepai watch --status
# Stop when done
grepai watch --stop
Now search semantically:
# Basic search
grepai search "authentication flow"
# Limit results
grepai search "error handling" --limit 5
# JSON output for scripts
grepai search "database queries" --json
Score: 0.89 | src/auth/middleware.go:15-45
──────────────────────────────────────────
func AuthMiddleware() gin.HandlerFunc {
return func(c *gin.Context) {
token := c.GetHeader("Authorization")
if token == "" {
c.AbortWithStatus(401)
return
}
// Validate JWT token...
}
}
Score: 0.82 | src/auth/jwt.go:23-55
──────────────────────────────────────────
func ValidateToken(tokenString string) (*Claims, error) {
token, err := jwt.Parse(tokenString, func(t *jwt.Token) (interface{}, error) {
return []byte(secretKey), nil
})
// ...
}
Trace function relationships:
# Who calls this function?
grepai trace callers "Login"
# What does this function call?
grepai trace callees "ProcessPayment"
# Full dependency graph
grepai trace graph "ValidateToken" --depth 3
# 1. Install (once)
brew install yoanbernabeu/tap/grepai
brew install ollama && ollama serve & && ollama pull nomic-embed-text
# 2. Setup project (once per project)
cd /your/project
grepai init
# 3. Index (run in background)
grepai watch --background
# 4. Search (as needed)
grepai search "your query here"
# 5. Trace (as needed)
grepai trace callers "FunctionName"
| Command | Purpose |
|---|---|
grepai init |
Initialize project config |
grepai watch |
Start indexing daemon |
grepai watch --background |
Run daemon in background |
grepai watch --status |
Check daemon status |
grepai watch --stop |
Stop daemon |
grepai search "query" |
Semantic search |
grepai search --json |
JSON output |
grepai trace callers "fn" |
Find callers |
grepai trace callees "fn" |
Find callees |
grepai status |
Index statistics |
grepai version |
Show version |
Be descriptive, not literal:
Describe intent:
Use English:
After mastering the basics:
grepai-embeddings-* skillsgrepai-storage-* skillsgrepai-search-* skillsgrepai-mcp-* skillsSuccessful quickstart:
✅ GrepAI Quickstart Complete
Project: /path/to/your/project
Files indexed: 245
Chunks created: 1,234
Embedder: Ollama (nomic-embed-text)
Storage: GOB (local file)
Try these searches:
- grepai search "main entry point"
- grepai search "database connection"
- grepai search "error handling"
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
grepai-quickstart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: grepai-quickstart is focused, and the summary matches what you get after install.
We added grepai-quickstart from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend grepai-quickstart for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
grepai-quickstart reduced setup friction for our internal harness; good balance of opinion and flexibility.
grepai-quickstart fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in grepai-quickstart — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for grepai-quickstart matched our evaluation — installs cleanly and behaves as described in the markdown.
grepai-quickstart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: grepai-quickstart is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 30