Skip to content
TrustedSkillsbeta
Back to all skills

Error Diagnostics Error Trace

Checked
liuchiawei·vlatest·testing

This skill automatically traces and diagnoses errors in code, pinpointing issues quickly for faster debugging and resolution.

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 liuchiawei/agent-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

liuchiawei

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 liuchiawei/agent-skills at f5a7853d0d.

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

Commit
f5a7853d0d
Manifest
skills/debug/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 identify the root cause of software errors. It can parse stack traces, extract relevant information like file names and line numbers, and provide a concise summary of the problem. The goal is to accelerate debugging and reduce time spent manually sifting through complex error reports.

When to use it

  • When you receive an error report with a lengthy stack trace that's difficult to understand.
  • To quickly identify the source file and line number where an error occurred in a large codebase.
  • For automated analysis of errors occurring in production environments, allowing for proactive issue resolution.
  • During software development to efficiently debug complex issues.

Key capabilities

  • Stack trace parsing
  • Error summary generation
  • File name extraction
  • Line number identification

Example prompts

  • "Analyze this error trace: [paste stack trace here]"
  • "What file and line number caused this error? [paste stack trace here]"
  • "Summarize the root cause of this error based on the following trace. [paste stack trace here]"

Tips & gotchas

The accuracy of the analysis depends heavily on the quality and format of the provided error trace. Ensure the input is a valid, complete stack trace for best results.