Skip to content
TrustedSkillsbeta
Back to all skills

Error Tracking

Checked
jackspace·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 jackspace/claudeskillz --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

jackspace

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 jackspace/claudeskillz at aef4e299d1.

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

Commit
aef4e299d1
Manifest
skills/error-tracking_diet103/SKILL.md
Scanned
2 files, 374 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 provides error tracking capabilities, allowing you to monitor and analyze errors occurring within your applications. It aggregates error data from various sources, providing insights into error frequency, types, and potential root causes. The goal is to improve application stability and reduce debugging time by centralizing and simplifying error management.

When to use it

  • Debugging Production Issues: Quickly identify the source of errors reported by users in a live environment.
  • Monitoring Application Health: Track error rates over time to proactively detect potential problems before they impact users significantly.
  • Analyzing Crash Reports: Understand patterns and trends within crash reports to prioritize bug fixes effectively.
  • Improving Code Quality: Use error data to identify areas of code that require refactoring or improved testing.

Key capabilities

  • Error aggregation from multiple sources
  • Error type analysis
  • Frequency tracking
  • Centralized error management

Example prompts

  • "Show me the top 5 most frequent errors in the last 24 hours."
  • "Analyze crash reports for version 1.2.3 of our application."
  • "What are the common causes of 'NullPointerException' errors?"

Tips & gotchas

The skill requires proper integration with your application’s error reporting mechanisms to effectively collect and analyze data. Ensure that all relevant error events are being captured and transmitted to the error tracking system for accurate monitoring.