Sign up
← all tools

cc-skill:error-handling-defaults

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill guides you on when to throw errors, when to catch them, and when to return result objects in your code. It helps you write error handling that fails loudly when something is actually wrong, but doesn't hide bugs under silent defaults.

who it is for

Any developer writing TypeScript or Python code who wants error handling that catches real problems instead of masking them.

when it fires

When you ask about error handling, try/catch blocks, exceptions, error boundaries, throwing errors, or how to handle failures in code.

say something like
  • "How should I handle errors in this API endpoint?"
  • "When should I throw an exception versus returning a result object?"
  • "Write a try/catch block for this scheduled job that won't swallow errors silently."
what you might get back
Instead of using 'campaign.budget ?? 0' which hides bugs, throw an error immediately: 'if (campaign.budget == null) { throw new Error(...) }'. This makes problems obvious at the boundary where you catch them. For expected failures like a missing database record, return a Result object: '{ ok: false, error: 'Asset not found' }' so the caller can decide what to do.
how to know it worked

Your error handling will catch real bugs early, every error will either be logged with context or intentionally suppressed with a comment explaining why, and there will be no silent failures.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/error-handling-defaults/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when writing TypeScript or Python code that involves error handling, try/catch blocks, exceptions, error boundaries, or recoverable failures in Jay's projects. Triggers on "error handling", "try catch", "exception", "error boundary", "

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/error-handling-defaults/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when writing TypeScript or Python code that involves error handling, try/catch blocks, exceptions, error boundaries, or recoverable failures in Jay's projects. Triggers on \"error handling\", \"try catch\", \"exception\", \"error boundary\", \"handle errors\", \"throw\", or any code where failure modes need to be considered. Applies Jay's conventions for when to throw, when to return, and when to log."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/error-handling-defaults/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.