Skip to content
TrustedSkillsbeta
Back to all skills

Error Tracking

Checked
microck·vlatest·devops

This "Error Tracking" skill automatically monitors and reports 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 microck/ordinary-claude-skills --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

microck

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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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 microck/ordinary-claude-skills at 1056d293d4.

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

Commit
1056d293d4
Manifest
skills_all/error-tracking/SKILL.md
Scanned
6 files, 1,092 lines
Copies in repo
3 — 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 microck-error-tracking skill allows AI agents to collect, aggregate, and analyze application errors. It provides a structured way to understand error frequency, identify patterns, and ultimately improve application stability. This includes grouping similar errors together and providing basic metrics like count and last occurrence time.

When to use it

  • Debugging Production Issues: Quickly gather information about recurring errors in a live environment.
  • Monitoring Application Health: Track error rates over time to identify potential regressions or performance bottlenecks.
  • Triaging Incoming Reports: Consolidate user-reported issues into categorized and quantifiable data for efficient investigation.
  • Automated Incident Response: Integrate with other tools to automatically respond to specific error patterns, like restarting services.

Key capabilities

  • Error collection from various sources (unspecified)
  • Error aggregation based on similarity (unspecified criteria)
  • Basic metrics: count and last occurrence time
  • Grouping of similar errors

Example prompts

  • "Show me the top 5 most frequent errors in the past hour."
  • "What were the error trends for our checkout service yesterday?"
  • "List all errors related to 'payment processing' from the last 24 hours."

Tips & gotchas

The skill requires a configured data source for error reporting. Specific integration details and supported formats are not specified in the provided documentation, so ensure compatibility before deployment.