Skip to content
TrustedSkillsbeta
Back to all skills

Extract Errors

Official
facebook·vlatest·testing·MIT

Identifies and categorizes error messages from logs or text to aid in debugging and 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 react/react --skill extract-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

facebook

Matched to the vendor's own GitHub organisation.

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 facebook/react at d083ec1da1.

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

Commit
d083ec1da1
Manifest
.claude/skills/extract-errors/SKILL.md
Scanned
1 file, 13 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 extract-errors skill identifies and extracts error messages from code or logs, helping developers quickly pinpoint issues in their applications. It is particularly useful for parsing verbose output and isolating relevant error information.

When to use it

  • Debugging a failing test suite where the console output contains multiple errors.
  • Analyzing server logs that include mixed content of warnings and errors.
  • Parsing build or compilation outputs from tools like Babel, TypeScript, or Webpack.

Key capabilities

  • Parses error messages from text logs or code outputs.
  • Extracts relevant stack traces and error codes.
  • Filters out non-error information for clarity.

Example prompts

  • "Extract all errors from this log file."
  • "Find the most recent error in the build output."
  • "List all error messages from the last test run."

Tips & gotchas

  • Ensure logs or code outputs are provided in a clear, text-based format for best results.
  • This skill may not work well with highly obfuscated or minified code.