Skip to content
TrustedSkillsbeta
Back to all skills

Error Diagnostics Error Trace

Checked
rmyndharis·vlatest·testing·MIT

This skill meticulously traces and diagnoses errors in your system, pinpointing root causes for faster resolution and improved stability.

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 error-diagnostics-error-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/error-diagnostics-error-trace/SKILL.md
Scanned
2 files, 1,403 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 analyzes error traces to provide concise, actionable insights for debugging. It can parse complex stack traces and identify the root cause of errors, suggesting potential solutions or areas for investigation. The tool aims to reduce diagnostic time and improve overall system stability by providing clear explanations of error origins.

When to use it

  • When encountering unexpected application behavior and needing to quickly understand the source of an error.
  • During development and testing phases to identify and resolve bugs efficiently.
  • In production environments for rapid incident response and troubleshooting.
  • When dealing with third-party libraries or APIs where error messages are cryptic or unhelpful.

Key capabilities

  • Error trace parsing
  • Root cause identification
  • Actionable suggestions
  • Concise explanations

Example prompts

  • "Analyze this error trace: [paste error trace here]"
  • "What is the likely root cause of this error? [paste error trace here]"
  • "Explain this stack trace and suggest possible fixes. [paste error trace here]"

Tips & gotchas

The quality of the analysis depends on the completeness and clarity of the provided error trace. Ensure you provide the full, unedited error output for best results.