Skills error-handling

📦

error-handling

Name: error-handling
Author: Doyajin174

v1.0 Content revision r1 Medium Risk ⚙️ External commands🌐 Network access🔑 Env variables

Improve Error Handling in Apps

Weak error handling hides failures and exposes technical messages to users. This skill guides Claude, Codex, and Claude Code toward safer recovery patterns.

Supports: Claude Codex Code(CC)

📊 71 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "error-handling" from https://skillstore.io/skills/doyajin174-error-handling.md and its manifest at https://skillstore.io/api/skills/doyajin174-error-handling/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/doyajin174-error-handling.md Signed manifest GET /api/skills/doyajin174-error-handling/manifest Signed lockfile GET /api/skills/doyajin174-error-handling/lockfile

Test it

Using "error-handling". A data loader leaves the page blank when a request fails.

Expected outcome:

Add a catch path that stores an error state and logs the failure.
Show a user-safe message with a retry action.
Return cached or empty fallback data when possible.

Using "error-handling". A React dashboard crashes when one chart throws an error.

Expected outcome:

Wrap the chart area in a scoped Error Boundary.
Display a chart-specific fallback instead of replacing the whole page.
Send the captured error and component context to the tracking service.

Using "error-handling". An app shows raw technical errors to users.

Expected outcome:

Map internal error codes to clear user messages.
Keep stack traces in developer logs only.
Use a default message for unexpected failures.

Security Audit

Medium Risk

v8 • 7/6/2026 Open versioned report

The static command findings are false positives from Markdown fences and TypeScript or TSX template literals. The hardcoded URLs are documentation references, and NODE_ENV access is a non-secret sample check. One semantic issue remains because the community skill grants Bash without a demonstrated need.

Files scanned

417

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:4

Overbroad Bash Tool Permission

The skill frontmatter allows Bash even though the instructions only provide error-handling guidance and examples. This unnecessarily expands command execution exposure for a community skill.

The allowed-tools metadata directly lists Bash on line 4, and no workflow in the skill requires shell commands.

Risk Factors

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/doyajin174-error-handling/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/doyajin174-error-handling/security.svg)](https://skillstore.io/skills/doyajin174-error-handling?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/doyajin174-error-handling?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-error-handling/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/doyajin174-error-handling.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Doyajin174. (2026). error-handling security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-error-handling/audits/8

BibTeX citation

@techreport{doyajin174-doyajin174-error-handling-2026,
  author = {Doyajin174},
  title = {error-handling security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/doyajin174-error-handling/audits/8},
  note = {Author version 1.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "error-handling security audit report (audit version 8)"
version: "1.0"
type: report
authors:
  - name: "Doyajin174"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doyajin174-error-handling/audits/8"
identifiers:
  - type: other
    value: "skillstore:doyajin174-error-handling:audit:8"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

Doyajin174 Recommended Current

doyajin174-error-handling

Skillstore Score 71

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

Awais68

awais68-error-handling

Skillstore Score 67

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Harden API Calls

Review request code for missing catch paths, user-safe messages, and fallback behavior.

Add React Boundaries

Plan where to place Error Boundaries so one component failure does not break the full app.

Standardize Error Responses

Create consistent error classes, message maps, and logging rules for a team codebase.

Try These Prompts

Review Basic Error Handling

Review this async function for missing error handling. Suggest try-catch, user feedback, logging, and a simple fallback.

Improve API Failure Paths

Audit this API call flow. Separate network, not found, authentication, validation, and unexpected errors with user-safe messages.

Design React Error Boundaries

Recommend Error Boundary placement for this React screen. Include fallback UI behavior and logging for component failures.

Create Error Strategy

Design an application error handling strategy. Cover custom error types, message mapping, graceful degradation, telemetry, and review checklist items.

Best Practices

Handle expected error types separately before using a generic fallback path.
Log enough context for developers while showing users simple recovery guidance.
Use scoped fallbacks so one failed feature does not break the whole screen.

Avoid

Do not leave catch blocks empty or silently ignore rejected promises.
Do not show stack traces or raw exception messages to end users.
Do not fail an entire page when a smaller fallback can keep useful content available.

Frequently Asked Questions

Does this skill write production error handling code automatically?

It provides patterns and review guidance. The assistant can draft code when you provide project context.

Which languages does it focus on?

The examples focus on TypeScript and TSX, with React and async JavaScript patterns.

Can it help with React Error Boundaries?

Yes. It includes boundary structure, fallback UI, and placement guidance for whole apps and smaller sections.

Does it cover user-facing error messages?

Yes. It recommends mapping internal errors to clear messages and avoiding technical details in the UI.

Does it configure error tracking tools?

No. It assumes an error tracking service exists and shows where logging or capture calls belong.

What should teams review before adopting it?

Teams should review logging privacy, telemetry redaction, and whether the Bash tool permission is necessary.

Developer Details

Author

Doyajin174

License

MIT

Author version

v1.0

Skillstore revision

Version notice

The author-declared version is not valid SemVer.

Repository

https://github.com/Doyajin174/myskills/tree/main/.public/skills/error-handling

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

6 downloads · 271 views

File structure

📄 SKILL.md