Skip to content
TrustedSkillsbeta
Back to all skills

Error Boundaries

Checked
yanko-belov·vlatest·backend·MIT

Error Boundaries proactively prevents unexpected errors by gracefully handling invalid user input or API responses, ensuring a smoother experience.

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 yanko-belov/code-craft --skill error-boundaries -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

yanko-belov

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 yanko-belov/code-craft at ca5e2ff60e.

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

Commit
ca5e2ff60e
Manifest
skills/error-boundaries/SKILL.md
Scanned
1 file, 359 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 provides a mechanism to gracefully handle errors within React component trees. It prevents JavaScript errors from crashing your entire application by catching them and displaying a fallback UI instead. Error boundaries define a tree of React components that will catch errors anywhere in their child component tree, including those nested deep within.

When to use it

  • Protecting user interfaces: Prevent unexpected crashes when third-party libraries or complex logic throws an error.
  • Displaying fallback content: Show a friendly error message or placeholder UI instead of a broken application state.
  • Debugging production issues: Error boundaries can help identify and isolate errors that might be difficult to track down in live environments.
  • Handling data fetching failures: Display an appropriate message when data fails to load from an API, preventing the entire app from freezing.

Key capabilities

  • Catches JavaScript errors within a component tree.
  • Renders a fallback UI upon error detection.
  • Provides context for debugging by storing error information.
  • Allows graceful degradation of functionality in case of errors.

Example prompts

  • "Wrap this section of the application with an error boundary."
  • "Create an error boundary component that displays a 'Something went wrong' message."
  • “Implement error handling for the user profile component using an error boundary.”

Tips & gotchas

  • Error boundaries only catch errors during rendering, in lifecycle methods, and in constructors of the class components they encapsulate. They don’t prevent exceptions from being thrown in event handlers or top-level applications code.