Skip to content
TrustedSkillsbeta
Back to all skills

Error Classification

Checked
j5ik2o·vlatest·testing·MIT

This skill automatically classifies errors based on their type, streamlining debugging and troubleshooting efforts for faster issue resolution.

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 j5ik2o/okite-ai --skill error-classification -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

j5ik2o

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 j5ik2o/okite-ai at f1bc1c3783.

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

Commit
f1bc1c3783
Manifest
skills/error-classification/SKILL.md
Scanned
1 file, 148 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 classifies errors based on provided descriptions. It can categorize errors into predefined types and assign severity levels, aiding in debugging and issue resolution. The skill is designed to help users understand the nature of errors quickly and efficiently.

When to use it

  • Analyzing application logs to identify recurring error patterns.
  • Triaging support tickets by automatically categorizing reported issues.
  • Prioritizing bug fixes based on severity classifications assigned by the skill.
  • Automating initial diagnostics for software failures.

Key capabilities

  • Error categorization
  • Severity level assignment
  • Description analysis

Example prompts

  • "Classify this error: 'Connection refused - unable to connect to database server.'"
  • "What is the severity of this error? 'NullPointerException in module X'"
  • "Categorize and assign a severity level to this error description: 'Failed to authenticate user due to invalid credentials.'"

Tips & gotchas

The skill's accuracy depends on the clarity and detail provided in the error descriptions. Ensure that error messages are complete and contain relevant information for optimal classification.