Skip to content
TrustedSkillsbeta
Back to all skills

Distributed Debugging Debug Trace

Checked
rmyndharis·vlatest·testing·MIT

Trace distributed system behavior across multiple services to pinpoint errors and performance bottlenecks during testing.

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 rmyndharis/antigravity-skills --skill distributed-debugging-debug-trace -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

rmyndharis

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 rmyndharis/antigravity-skills at 3eff4af253.

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

Commit
3eff4af253
Manifest
skills/distributed-debugging-debug-trace/SKILL.md
Scanned
2 files, 1,331 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

This skill enables distributed debugging and trace analysis for AI agents. It allows you to pinpoint the source of errors across multiple components or services within a larger system, providing detailed insights into execution flow. The tool facilitates identifying performance bottlenecks and understanding complex interactions between different parts of an application.

When to use it

  • Troubleshooting complex workflows: When an agent's actions result in unexpected outcomes involving multiple tools or APIs.
  • Performance optimization: To identify slow steps within a multi-stage process and optimize execution time.
  • Debugging interactions between services: When issues arise from the communication or data exchange between different microservices used by the AI agent.
  • Understanding agent behavior in distributed environments: When an agent operates across multiple machines or cloud regions, this skill helps track its progress and identify potential problems.

Key capabilities

  • Distributed trace analysis
  • Debugging across multiple components
  • Performance bottleneck identification
  • Execution flow visualization

Example prompts

  • "Trace the execution of my order processing workflow and highlight any steps taking longer than 5 seconds."
  • "Debug why my agent failed to complete the payment process, showing me all interactions with the payment API."
  • "Show me a detailed trace of how data flows between the inventory service and the shipping module during order fulfillment."

Tips & gotchas

This skill requires access to logs and metrics from all relevant components. Ensure proper instrumentation is in place before attempting to use it for debugging.