Skip to content
TrustedSkillsbeta
Back to all skills

Error Taxonomy

Checked
cleanexpo·vlatest·testing·MIT

This skill organizes errors into a structured taxonomy for efficient identification & resolution, boosting debugging speed and accuracy.

Install on your platform

This skill no longer installs under the name error-taxonomy. cleanexpo/nodejs-starter-v1 is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

cleanexpo

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 cleanexpo/nodejs-starter-v1 at 7b45925bd4.

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

Scanned
9 files, 1,314 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

The error-taxonomy skill provides a structured classification of errors. It allows AI agents to categorize and understand different types of errors, facilitating more targeted debugging and resolution strategies. This skill helps in organizing error messages into meaningful groups based on their root cause or impact.

When to use it

  • Debugging complex systems: When troubleshooting issues across multiple components, the skill can help organize and prioritize errors by type.
  • Analyzing application logs: Categorize log entries to identify recurring patterns and potential problem areas within an application.
  • Creating automated incident response workflows: Use error categories to trigger specific actions or notifications based on the severity and nature of the error.
  • Improving developer documentation: Organize common errors into a structured format for easier understanding by developers.

Key capabilities

  • Error categorization
  • Structured classification
  • Root cause analysis (implied)

Example prompts

  • "Categorize this error message: 'Connection refused on port 8080'."
  • "What are the common categories of HTTP errors?"
  • "Group these error logs by type and severity."

Tips & gotchas

The effectiveness of this skill depends on the quality and completeness of its internal error taxonomy. Consider providing specific examples or context for more accurate categorization.