Skip to content
TrustedSkillsbeta
Back to all skills

Error Tracking

Checked
aj-geddes·vlatest·devops·MIT

Error Tracking monitors application logs for recurring errors, proactively identifying and resolving issues to improve stability & performance.

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 aj-geddes/useful-ai-prompts --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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/error-tracking/SKILL.md
Scanned
9 files, 373 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

error-tracking

What it does

This skill enables AI agents to identify, log, and analyze errors within application logs or system outputs. It automatically categorizes issues based on severity levels and extracts relevant context to assist in rapid debugging.

When to use it

  • Production Monitoring: Continuously scan live server logs for unexpected exceptions or crashes.
  • Debugging Sessions: Isolate specific error patterns when a deployment fails or performance degrades.
  • Audit Trails: Maintain a structured record of incidents for post-mortem analysis and compliance.
  • Automated Alerts: Trigger immediate notifications when critical errors exceed defined thresholds.

Key capabilities

  • Parses unstructured log files to find error keywords (e.g., "Error", "Exception", "Failed").
  • Classifies issues by severity tags such as critical, warning, or info.
  • Extracts stack traces, timestamps, and associated user IDs from raw text.
  • Generates concise summaries of recurring failure patterns.

Example prompts

  • "Scan the attached server logs and list all critical errors occurring after 2:00 PM UTC."
  • "Extract every Python exception with a stack trace from this log dump and group them by error type."
  • "Identify any authentication failures in the access logs and summarize the frequency per IP address."

Tips & gotchas

Ensure your input logs are formatted consistently, as parsing accuracy depends heavily on standard log structures. For best results, provide context about the application environment so the agent can better interpret specific error codes.