Agent skill

Find Usages

by adamthewilliam in adamthewilliam/grepika

This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords…

MITAuto-check passedDevelopment

Install Find Usages

skills CLI
$ npx skills add adamthewilliam/grepika --skill find-usages -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install adamthewilliam/grepika find-usages --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/grepika/skills/find-usages .claude/skills/find-usages && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
find-usages
GitHub stars
138
Token cost
~1k tokens
SKILL.md length
287 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords…

  • Works in 5 steps: Find all references → Group results by ref_type → Build call hierarchy (for functions) → …
  • Asks to find usages of
  • SKILL.md covers Input, Pre-check, Usage Analysis Workflow and Output Format, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Find Usages is an agent skill from adamthewilliam/grepika. This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires grepika MCP server.

It sits in Development. It works with Model Context Protocol. The licence is MIT.

When your agent uses it

  • Asks to find usages of
  • Where is this used
  • What calls this function
  • Trace symbol usage

Example prompts

  • “find usages of”
  • “where is this used”
  • “what calls this function”
  • “/find-usages”

Requirements

  • Compatibility (from SKILL.md): Requires grepika MCP server.
  • Pre-approved tools (allowed-tools): mcp__grepika__refs, mcp__grepika__context, mcp__grepika__outline, mcp__grepika__get, mcp__grepika__search, mcp__grepika__graph, mcp__grepika__add_workspace

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Find all references
  2. Group results by ref_type
  3. Build call hierarchy (for functions)
  4. Get context for important usages
  5. Extract structure of heavy usage files

What it can do on your machine

Read from SKILL.md and the folder at commit f035a18. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • mcp__grepika__refs
    • mcp__grepika__context
    • mcp__grepika__outline
    • mcp__grepika__get
    • mcp__grepika__search
    • mcp__grepika__graph
    • mcp__grepika__add_workspace

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires grepika MCP server.

    From compatibility in the SKILL.md frontmatter.

Context cost

Find Usages loads about 1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 287 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from adamthewilliam/grepika at commit f035a18, republished under its MIT licence (© adamthewilliam). 287 words, ~1,016 tokens.

Download SKILL.mdSave it as .claude/skills/find-usages/SKILL.md (or your agent's skills folder).
name
find-usages
description
This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.
allowed-tools
mcp__grepika__refs, mcp__grepika__context, mcp__grepika__outline, mcp__grepika__get, mcp__grepika__search, mcp__grepika__graph, mcp__grepika__add_workspace
compatibility
Requires grepika MCP server.
version
1.0.0
disable-model-invocation
true
context
fork
agent
Explore
model
haiku

Find Usages Skill

You are a symbol reference analyst. Trace how symbols are used throughout the codebase and build call hierarchies.

Input

Symbol to trace: $ARGUMENTS

Expected formats:

  • functionName - Find usages of a function
  • ClassName - Find usages of a class
  • module:export - Find usages of a specific export
  • CONSTANT_NAME - Find usages of a constant

If no symbol provided, ask the user what they want to trace.

Pre-check

If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.

Usage Analysis Workflow

  1. Find all references

    • Use mcp__grepika__refs with the symbol name
    • Capture file paths, line numbers, and match context
  2. Group results by ref_type

    • The refs tool returns a ref_type field for each reference: definition, import, type_usage, usage
    • Group results by this field — do NOT manually re-categorize
    • Count references per type and per file
  3. Build call hierarchy (for functions)

    • Filter for references with ref_type: "usage" to find callers (skip definitions and imports)
    • Use mcp__grepika__refs on each caller to build the chain upward
    • Stop when reaching entry points or after 3 levels
  4. Get context for important usages

    • Use mcp__grepika__context for complex call sites
    • Understand how the symbol is being used
  5. Extract structure of heavy usage files

    • Use mcp__grepika__outline on files with many references
    • Understand the surrounding context

Output Format

## Symbol Usage Analysis: [symbol]

### Definition
- **File**: [path:line]
- **Type**: [function / class / constant / type / interface]
- **Signature**: [brief signature if applicable]

### Usage Summary
| ref_type | Count | Files |
|----------|-------|-------|
| definition | [count] | [unique file count] |
| import | [count] | [unique file count] |
| type_usage | [count] | [unique file count] |
| usage | [count] | [unique file count] |

### Call Hierarchy (if applicable)

[Entry Point A] └── [Caller 1] └── [Caller 2] └── [symbol] ← target [Entry Point B] └── [Direct Caller] └── [symbol] ← target


### Usage by File

| File | Usages | Primary Use |
|------|--------|-------------|
| [path] | [count] | [import/call/extend] |

### Detailed References

#### [Category: Imports]
| File | Line | Context |
|------|------|---------|
| [path] | [line] | [import statement] |

#### [Category: Call Sites]
| File | Line | Caller | Context |
|------|------|--------|---------|
| [path] | [line] | [function name] | [brief context] |

### Insights
- **Most common usage pattern**: [description]
- **Key dependencies**: [files that heavily depend on this symbol]
- **Refactoring considerations**: [notes about changing this symbol]

### Related Symbols
- [symbols commonly used alongside the target]
- [symbols that might need updating if target changes]

Tips

  • Distinguish between definition sites and usage sites clearly
  • For widely-used symbols, group by module/feature area
  • Watch for indirect usages through re-exports or barrel files
  • Note any dynamic usages that static analysis might miss
  • Consider test files separately from production code

Additional Resources

See references/ folder for:

  • Call hierarchy visualization patterns
  • Symbol categorization techniques

© adamthewilliam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/grepika/skills/find-usages of adamthewilliam/grepika.

Open the folder on GitHubat commit f035a18

Compare with similar skills

Find Usages next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Find Usages compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Find Usages this skilladamthewilliam/grepika138—~1kAutomated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Analyze Logsactivepieces/activepieces25k1 repos~1.6kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Claude Code Skillcodeaashu/claude-code3.4k1 repos~2.7kAutomated safety check: PassProprietary

Similar skills

  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Analyze Logs

    activepieces/activepieces

    Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.

    25k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes

More from adamthewilliam/grepika

All 9 skills in this repo
  • Impact

    adamthewilliam/grepika

    This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to…

    138 GitHub stars~794 tokensUpdated 1 mo ago
    Auto-check passed
  • Index Status

    adamthewilliam/grepika

    This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search…

    138 GitHub stars~696 tokensUpdated 1 mo ago
    Auto-check passed
  • Investigate

    adamthewilliam/grepika

    This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug…

    138 GitHub stars~762 tokensUpdated 1 mo ago
    Auto-check passed
  • Learn Codebase

    adamthewilliam/grepika

    This skill should be used when the user asks to "learn this codebase", "give me a codebase overview", "onboard me to this project", "explain the architecture", or mentions keywords related to…

    138 GitHub stars~922 tokensUpdated 1 mo ago
    Auto-check passed
  • Apply Pattern

    adamthewilliam/grepika

    This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or…

    138 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check: notes
  • Architecture

    adamthewilliam/grepika

    This skill should be used when the user asks to "map the architecture", "show module dependencies", "analyze coupling", "dependency graph", "how are modules connected", "module boundaries", or…

    138 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Find Usages

What does Find Usages do?

This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords…. Find Usages is an agent skill from adamthewilliam/grepika. This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.

When should I use Find Usages?

Find Usages fits situations like: asks to find usages of; where is this used; what calls this function; trace symbol usage.

How do I install Find Usages in Claude Code?

Run `npx skills add adamthewilliam/grepika --skill find-usages -a claude-code`. Or copy the skill folder (plugins/grepika/skills/find-usages in adamthewilliam/grepika) into .claude/skills/find-usages in your project. Claude Code loads it when a task matches its description.

How do I install Find Usages in Codex?

Run `npx skills add adamthewilliam/grepika --skill find-usages -a codex`. Or copy the skill folder (plugins/grepika/skills/find-usages in adamthewilliam/grepika) into .agents/skills/find-usages in your project. Codex loads it when a task matches its description.

Can I use Find Usages in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adamthewilliam/grepika --skill find-usages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-usages, .gemini/skills/find-usages, .github/skills/find-usages and .opencode/skills/find-usages in your project.

What does Find Usages need to run?

SKILL.md names no scripts, command-line tools or credentials: Find Usages is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__grepika__refs, mcp__grepika__context, mcp__grepika__outline, mcp__grepika__get, mcp__grepika__search, mcp__grepika__graph, mcp__grepika__add_workspace. Compatibility (from SKILL.md): Requires grepika MCP server..

Does Find Usages access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Find Usages safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Find Usages use?

Find Usages is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Find Usages use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Find Usages?

Skills that share tags, products or a category with Find Usages: Debugging Executions (n8n-io/n8n, 207k stars), ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars), Analyze Logs (activepieces/activepieces, 25k stars) and Release (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Find Usages?

adamthewilliam (a GitHub user) maintains it in adamthewilliam/grepika, which has 138 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 12, 2026.

Source: adamthewilliam/grepika on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.