Fetches grepai-trace-callees from yoanbernabeu/grepai-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/grepai-trace-callees
Restart Cursor to activate grepai-trace-callees. Access via /grepai-trace-callees 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.
# What does this complex function do?grepai trace callees "handleRequest"# Map the data flowgrepai trace callees "processPayment"
Finding Dependencies
# What external services does this call?grepai trace callees "syncData"# What database operations happen?grepai trace callees "saveUser"
Code Review
# What side effects does this function have?grepai trace callees "updateProfile"# Is this function doing too much?grepai trace callees "doEverything"# Lots of callees = code smell
Documentation
# Generate dependency list for docsgrepai trace callees "initialize"--json| jq '.results[].callee'
Callers vs Callees
Command
Question
Use Case
trace callers
Who calls me?
Impact analysis
trace callees
What do I call?
Behavior analysis
# Combined analysisgrepai trace callers "processOrder"# Who uses this?grepai trace callees "processOrder"# What does it do?
Filtering Results
By File Type
# Get callees and filter to only .go filesgrepai trace callees "main"--json| jq '.results[] | select(.file | endswith(".go"))'
# Count how many database vs. API callsgrepai trace callees "processOrder"--json| jq '.results[].callee'|grep-c"db"
What Callees Includes
The trace finds:
Direct function calls
Method calls
Built-in function calls (depending on mode)
Example
funcProcessOrder(order Order)error{// Direct callvalidateOrder(order)// Method call order.Validate()// Package function utils.Log("processing")// Built-in (may or may not be captured) fmt.Println("done")returnnil}
Callees found:
validateOrder
Validate (method)
Log (from utils)
Println (depending on mode)
Limitations
What Callees Might Miss
Dynamic/runtime calls
Callbacks and closures
Interface method calls (may show interface, not implementation)
Reflection-based calls
Example of Undetected Call
funcprocess(fn func()){fn()// Callee is unknown at static analysis time}
Combining with Trace Graph
For recursive dependency analysis, use trace graph:
# Direct callees onlygrepai trace callees "main"# Full dependency tree (recursive)grepai trace graph "main"--depth3
#!/bin/bashecho"# Function Dependencies Report"echo""forfnin main initialize processOrder;do
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ 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.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
