Skip to content
TrustedSkillsbeta
Back to all skills

Error Tracking

Checked
diet103·vlatest·devops·MIT

This "Error Tracking" skill automatically monitors and logs application errors, providing crucial insights for rapid debugging 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 diet103/claude-code-infrastructure-showcase --skill error-tracking -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

diet103

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 diet103/claude-code-infrastructure-showcase at 07f75ce3c3.

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

Commit
07f75ce3c3
Manifest
.agents/skills/error-tracking/SKILL.md
Scanned
2 files, 670 lines
Copies in repo
2 — all of them scanned
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 error-tracking skill provides automated collection and analysis of application errors. It can gather detailed error reports, including stack traces and context information, to facilitate debugging and issue resolution. This allows for proactive identification and remediation of software defects, improving overall system stability and user experience.

When to use it

  • Debugging Production Issues: Quickly identify the root cause of unexpected behavior in a live application by analyzing collected error reports.
  • Monitoring Application Health: Track error rates over time to detect performance regressions or emerging issues.
  • Reproducing User-Reported Bugs: Gather context around user-reported errors to simplify reproduction and debugging.
  • Automated Incident Response: Integrate with incident management systems to automatically create tickets based on detected errors.

Key capabilities

  • Error report collection
  • Stack trace analysis
  • Contextual data gathering
  • Integration with error reporting services (implied)

Example prompts

  • "Show me the most recent 10 error reports."
  • "Analyze errors related to user authentication in the last 24 hours."
  • "Summarize the frequency of 'NullPointerException' errors."

Tips & gotchas

This skill likely requires configuration with an existing error reporting system. Ensure proper integration and data mapping for optimal results.