This skill provides a complete reference for all GrepAI configuration options in .grepai/config.yaml.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongrepai-config-referenceExecute the skills CLI command in your project's root directory to begin installation:
Fetches grepai-config-reference 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-config-reference. Access via /grepai-config-reference 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
16
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
16
stars
This skill provides a complete reference for all GrepAI configuration options in .grepai/config.yaml.
/your/project/.grepai/config.yaml
version: 1
# ═══════════════════════════════════════════════════════════════
# EMBEDDER CONFIGURATION
# Converts code text into vector embeddings
# ═══════════════════════════════════════════════════════════════
embedder:
# Provider: ollama | openai | lmstudio
provider: ollama
# Model name (depends on provider)
# Ollama: nomic-embed-text, bge-m3, mxbai-embed-large
# OpenAI: text-embedding-3-small, text-embedding-3-large
# LM Studio: nomic-embed-text-v1.5, bge-small-en-v1.5
model: nomic-embed-text
# API endpoint URL
# Ollama default: http://localhost:11434
# LM Studio default: http://localhost:1234
# OpenAI: uses official API
endpoint: http://localhost:11434
# Vector dimensions (auto-detected if omitted)
# nomic-embed-text: 768
# text-embedding-3-small: 1536
# text-embedding-3-large: 3072
dimensions: 768
# API key (for OpenAI, supports env vars)
api_key: ${OPENAI_API_KEY}
# Parallel requests (OpenAI only, for speed)
parallelism: 4
# ═══════════════════════════════════════════════════════════════
# STORE CONFIGURATION
# Where vector embeddings are stored
# ═══════════════════════════════════════════════════════════════
store:
# Backend: gob | postgres | qdrant
backend: gob
# PostgreSQL configuration (when backend: postgres)
postgres:
dsn: postgres://user:password@localhost:5432/grepai
# Qdrant configuration (when backend: qdrant)
qdrant:
endpoint: localhost
port: 6334
use_tls: false
api_key: your-qdrant-api-key # Optional
# ═══════════════════════════════════════════════════════════════
# CHUNKING CONFIGURATION
# How code files are split for embedding
# ═══════════════════════════════════════════════════════════════
chunking:
# Tokens per chunk (smaller = more precise, larger = more context)
# Recommended: 256-1024
size: 512
# Overlap between chunks (preserves context at boundaries)
# Recommended: 10-20% of size
overlap: 50
# ═══════════════════════════════════════════════════════════════
# WATCH CONFIGURATION
# File watching daemon settings
# ═══════════════════════════════════════════════════════════════
watch:
# Debounce delay in milliseconds
# Groups rapid file changes together
debounce_ms: 500
# ═══════════════════════════════════════════════════════════════
# TRACE CONFIGURATION
# Call graph analysis settings
# ═══════════════════════════════════════════════════════════════
trace:
# Extraction mode: fast | precise
# fast: Uses regex, no dependencies, faster
# precise: Uses tree-sitter AST parsing, more accurate
mode: fast
# Languages to analyze for call graphs
enabled_languages:
- .go
- .js
- .ts
- .jsx
- .tsx
- .py
- .php
- .c
- .h
- .cpp
- .hpp
- .cc
- .cxx
- .rs
- .zig
- .cs
- .pas
- .dpr
# Patterns to exclude from trace analysis
exclude_patterns:
- "*_test.go"
- "*.spec.ts"
- "*.test.js"
# ═══════════════════════════════════════════════════════════════
# SEARCH CONFIGURATION
# Search result scoring and ranking
# ═══════════════════════════════════════════════════════════════
search:
# Score boosting configuration
boost:
enabled: true
# Reduce scores for certain paths
penalties:
- pattern: /tests/
factor: 0.5
- pattern: _test.
factor: 0.5
- pattern: .spec.
factor: 0.5
- pattern: /docs/
factor: 0.6
- pattern: /vendor/
factor: 0.3
- pattern: /node_modules/
factor: 0.3
# Increase scores for certain paths
bonuses:
- pattern: /src/
factor: 1.1
- pattern: /lib/
factor: 1.1
- pattern: /core/
factor: 1.2
- pattern: /app/
factor: 1.1
# Hybrid search (vector + keyword)
hybrid:
enabled: false
k: 60 # BM25 parameter
# ═══════════════════════════════════════════════════════════════
# IGNORE CONFIGURATION
# Files and directories to exclude from indexing
# ═══════════════════════════════════════════════════════════════
ignore:
# Directories
- .git
- .grepai
- .svn
- .hg
- node_modules
- vendor
- target
- __pycache__
- .pytest_cache
- dist
- build
- out
- .next
- .nuxt
# Files
- "*.min.js"
- "*.min.css"
- "*.bundle.js"
- "*.map"
- "*.lock"
- package-lock.json
- yarn.lock
- pnpm-lock.yaml
- go.sum
# Generated
- "*.generated.*"
- "*.pb.go"
- "*.d.ts"
version: 1
embedder:
provider: ollama
model: nomic-embed-text
store:
backend: gob
chunking:
size: 512
overlap: 50
version: 1
embedder:
provider: ollama
model: bge-m3 # Larger model
parallelism: 4
store:
backend: posPrerequisites
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.
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
sickn33/antigravity-awesome-skills
myzy-ai/dokie-ai-ppt
sickn33/antigravity-awesome-skills
grepai-config-reference is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
grepai-config-reference reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend grepai-config-reference for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
grepai-config-reference reduced setup friction for our internal harness; good balance of opinion and flexibility.
grepai-config-reference is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend grepai-config-reference for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in grepai-config-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in grepai-config-reference — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend grepai-config-reference for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
grepai-config-reference is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 26