Skip to content
TrustedSkillsbeta
Back to all skills

Errors

Checked
yonatangross·vlatest·agents·MIT

This skill identifies and flags potential errors in your prompts, ensuring clearer outputs and more reliable AI responses.

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 yonatangross/orchestkit --skill errors -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

yonatangross

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 yonatangross/orchestkit at 7784b90c05.

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

Commit
7784b90c05
Manifest
src/skills/errors/SKILL.md
Scanned
2 files, 254 lines
Copies in repo
2 — 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

The errors skill enables AI agents to detect, log, and report runtime failures within the Orchestrator framework. It captures execution context details when tasks fail, allowing for immediate troubleshooting and system stability monitoring.

When to use it

  • Debugging failed workflows: Automatically identify why a specific agent task or orchestration step did not complete successfully.
  • Production monitoring: Track error rates in real-time to alert developers of critical service disruptions.
  • Root cause analysis: Retrieve detailed stack traces and input data associated with specific failure events.
  • Audit logging: Maintain a historical record of system anomalies for compliance or post-mortem reviews.

Key capabilities

  • Captures raw error messages generated during agent execution.
  • Logs full stack traces for complex failures.
  • Associates errors with the specific task ID and context where they occurred.
  • Integrates seamlessly with the Orchestrator's existing logging infrastructure.

Example prompts

  • "Log an error indicating that the data retrieval step failed due to a timeout."
  • "Report a critical failure in the user authentication module with full stack details."
  • "Capture and store the exception thrown when the API response was malformed."

Tips & gotchas

Ensure your agent has write permissions to the designated error log directory or database endpoint. This skill does not automatically retry failed tasks; it only records the failure for human or external system intervention.