Skip to content
TrustedSkillsbeta
Back to all skills

Grepai Trace Callers

Checked
yoanbernabeu·vlatest·other·MIT

This skill identifies and lists all users who have called a specific phone number, useful for contact tracing or outreach efforts.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add yoanbernabeu/grepai-skills --skill grepai-trace-callers -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

yoanbernabeu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned yoanbernabeu/grepai-skills at 382d40261c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
382d40261c
Manifest
skills/trace/grepai-trace-callers/SKILL.md
Scanned
1 file, 317 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The grepai-trace-callers skill allows you to trace the callers of a given function within your code. It provides insights into which parts of your application are invoking specific functions, aiding in debugging and understanding program flow. This capability is particularly useful for complex systems where identifying dependencies can be challenging.

When to use it

  • Debugging: Quickly pinpoint the origin of unexpected behavior by tracing the callers of a function exhibiting issues.
  • Code Understanding: When onboarding to a new codebase or trying to understand how different components interact, trace function calls to visualize relationships.
  • Impact Analysis: Before refactoring or removing a function, determine which parts of your application rely on it.
  • Performance Optimization: Identify frequently called functions and their callers to focus optimization efforts effectively.

Key capabilities

  • Function Caller Tracing: Identifies the lines of code that call a specified function.
  • Code Dependency Analysis: Reveals dependencies between different modules or components within your application.
  • Debugging Assistance: Helps isolate and resolve issues by tracing execution paths.

Example prompts

  • "Trace callers for process_payment."
  • "Show me who calls the calculate_total function."
  • "What functions call send_email?"

Tips & gotchas

The skill requires access to your codebase and may need appropriate permissions to analyze the code. Ensure that the specified function exists within the scope of the analysis for accurate results.