Agent skill

Output Error Try Catch

by growthxai in growthxai/output

Handle errors caught in Output workflows without losing failure context.

Apache-2.0Auto-check: notes

Install Output Error Try Catch

skills CLI
$ npx skills add growthxai/output --skill output-error-try-catch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthxai/output output-error-try-catch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-error-try-catch .claude/skills/output-error-try-catch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
output-error-try-catch
GitHub stars
442
Token cost
~1.1k tokens
SKILL.md length
368 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Handle errors caught in Output workflows without losing failure context.

  • Adding workflow try/catch logic
  • SKILL.md covers Understand when workflow catch…, Let unexpected failures…, Check specific error types… and Valid try/catch patterns, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Partial-failure handling

What it does

Output Error Try Catch is an agent skill from growthxai/output. Handle errors caught in Output workflows without losing failure context. Use when adding workflow try/catch logic, fallbacks, partial-failure handling, custom Error classes, or typed checks for errors thrown by steps and evaluators.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already… The licence is Apache-2.0.

When your agent uses it

  • Adding workflow try/catch logic
  • Partial-failure handling
  • Custom Error classes
  • Typed checks for errors thrown by steps and evaluators

Example prompts

  • “/output-error-try-catch”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit

What it can do on your machine

Read from SKILL.md and the folder at commit 99ee298. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Output Error Try Catch loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 368 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 368 words, ~1,114 tokens.

Download SKILL.mdSave it as .claude/skills/output-error-try-catch/SKILL.md (or your agent's skills folder).
name
output-error-try-catch
description
Handle errors caught in Output workflows without losing failure context. Use when adding workflow try/catch logic, fallbacks, partial-failure handling, custom Error classes, or typed checks for errors thrown by steps and evaluators.
allowed-tools
Bash, Read, Write, Edit

Handle Errors in Workflows

Understand when workflow catch blocks run

Steps and evaluators run as Temporal Activities. Temporal applies their configured retry policy before returning a successful result or throwing a final failure to workflow code.

A workflow catch around a step therefore runs only after the step has exhausted its Activity retries. Catching that failure does not disable or bypass the Activity retry policy.

The catch block decides what the workflow does with the final failure:

  • Return a fallback value.
  • Run an alternative step.
  • Record a partial failure and continue.
  • Handle an expected error type.
  • Rethrow the error and fail the workflow.

Let unexpected failures propagate

Do not add a catch block that only wraps or logs an error. It can discard Temporal's failure type, cause chain, and retry metadata.

typescript
// Avoid: replaces the original Temporal failure chain.
try {
  return await fetchData( input );
} catch ( error ) {
  throw new Error( `Fetch failed: ${error.message}` );
}

When the workflow cannot recover, let the step failure propagate:

typescript
export default workflow( {
  name: 'fetch_workflow',
  fn: async input => fetchData( input )
} );

If a catch block handles only known failures, always rethrow everything else.

Check specific error types with hasErrorType

Errors crossing from a step or evaluator into workflow code are serialized into a Temporal failure cause chain. The original JavaScript object identity is not preserved, so error instanceof CustomError is unreliable.

Use hasErrorType from @outputai/core. It walks the cause chain and matches native instances and Temporal's serialized type and name fields.

typescript
import { hasErrorType, workflow } from '@outputai/core';
import { lookupCompany } from './steps.js';
import { CompanyNotFoundError } from './types.js';

export default workflow( {
  name: 'company_lookup',
  fn: async input => {
    try {
      return await lookupCompany( input );
    } catch ( error ) {
      if ( hasErrorType( error, CompanyNotFoundError ) ) {
        return null;
      }

      throw error;
    }
  }
} );

Define custom Error classes in a shared module imported by both the workflow and step:

typescript
export class CompanyNotFoundError extends Error {}

Do not inspect a fixed number of .cause levels or check only the outer ActivityFailure.

Show full SKILL.md (127 more words)Show less

Valid try/catch patterns

Fallback step
typescript
const fetchWithFallback = async input => {
  try {
    return await fetchFromPrimarySource( input );
  } catch {
    return fetchFromSecondarySource( input );
  }
};

Use this only when every primary-source failure should trigger the fallback. Use hasErrorType when only specific failures are recoverable.

Partial failures
typescript
const results = await Promise.all( input.items.map( async item => {
  try {
    return { item, value: await processItem( item ), ok: true };
  } catch ( error ) {
    const message = error instanceof Error ? error.message : String( error );
    return { item, error: message, ok: false };
  }
} ) );

Ensure the workflow output schema supports both successful and failed entries. Do not silently omit failures.

Configure Activity retries separately

Configure step and evaluator retry behavior through workflow Activity options. The workflow catch block handles only the failure that remains after this policy is exhausted.

typescript
export default workflow( {
  name: 'company_lookup',
  fn: async input => lookupCompany( input ),
  options: {
    activityOptions: {
      retry: {
        initialInterval: '1s',
        maximumAttempts: 3
      }
    }
  }
} );

Review checklist

  • Catch only when the workflow has a defined recovery path.
  • Use hasErrorType for specific errors originating in steps or evaluators.
  • Rethrow unmatched errors unchanged.
  • Do not replace an existing failure with a generic Error.
  • Keep custom Error class names stable because Temporal serializes them as failure types.
  • Configure retries independently from workflow catch behavior.

© growthxai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-error-try-catch of growthxai/output.

Open the folder on GitHubat commit 99ee298

Compare with similar skills

Output Error Try Catch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Output Error Try Catch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Error Try Catch this skillgrowthxai/output442—~1.1kAutomated safety check: NotesApache-2.0
Error Handlingaffaan-m/ECC276k1 repos~2.7kAutomated safety check: PassMIT
Handle PR CI FailureDataDog/datadog-agent3.8k—~2.9kAutomated safety check: PassApache-2.0
Python Error Handlingwshobson/agents40k—~1.5kAutomated safety check: PassMIT
Error Handlingthedaviddias/Front-End-Checklist74k—~416Automated safety check: PassMIT
Error Handlingaffaan-m/ECC276k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Error Handling

    affaan-m/ECC

    Patterns for robust error handling across TypeScript, Python, and Go.

    276k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Handle PR CI Failure

    DataDog/datadog-agent

    Official

    Handle a CI failure that is reliably attributed to the current PR's own code changes.

    3.8k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Python Error Handling

    wshobson/agents

    Python error handling patterns including input validation, exception hierarchies, and partial failure handling.

    40k GitHub stars~1.5k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Error Handling

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling.

    74k GitHub stars~416 tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Error Handling

    affaan-m/ECC

    TypeScript、Python、Goにわたる堅牢なエラー処理のパターン。型付きエラー、エラー境界、リトライ、サーキットブレーカー、ユーザー向けエラーメッセージをカバーします。

    276k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • N8n Error Handling

    sickn33/agentic-awesome-skills

    Design visible, structured, recoverable n8n failures using error outputs, retries, Error Trigger workflows, and HTTP error responses.

    47k GitHub starsUsed in 1 repo~4.9k tokens
    Productivity & AutomationAuto-check passed

More from growthxai/output

All 50 skills in this repo
  • Output Build Workflow

    growthxai/output

    Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.

    442 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Output Credentials Edit

    growthxai/output

    View, edit, and set encrypted credentials in an Output.ai project.

    442 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes
  • Wire encrypted credentials to environment variables using the credential: convention.

    442 GitHub stars~930 tokensUpdated today
    Auto-check: notes
  • Output Credentials Init

    growthxai/output

    Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.

    442 GitHub stars~803 tokensUpdated today
    Auto-check: notes
  • Output Debug Workflow

    growthxai/output

    Debug Output SDK workflow issues. An agent skill from growthxai/output.

    442 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Output Dev Agent Class

    growthxai/output

    Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.

    442 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Questions about Output Error Try Catch

What does Output Error Try Catch do?

Handle errors caught in Output workflows without losing failure context. Output Error Try Catch is an agent skill from growthxai/output. Handle errors caught in Output workflows without losing failure context.

When should I use Output Error Try Catch?

Output Error Try Catch fits situations like: adding workflow try/catch logic; partial-failure handling; custom Error classes; typed checks for errors thrown by steps and evaluators.

How do I install Output Error Try Catch in Claude Code?

Run `npx skills add growthxai/output --skill output-error-try-catch -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-error-try-catch in growthxai/output) into .claude/skills/output-error-try-catch in your project. Claude Code loads it when a task matches its description.

How do I install Output Error Try Catch in Codex?

Run `npx skills add growthxai/output --skill output-error-try-catch -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-error-try-catch in growthxai/output) into .agents/skills/output-error-try-catch in your project. Codex loads it when a task matches its description.

Can I use Output Error Try Catch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-error-try-catch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output-error-try-catch, .gemini/skills/output-error-try-catch, .github/skills/output-error-try-catch and .opencode/skills/output-error-try-catch in your project.

What does Output Error Try Catch need to run?

SKILL.md names no scripts, command-line tools or credentials: Output Error Try Catch is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit.

Does Output Error Try Catch access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Output Error Try Catch safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Output Error Try Catch use?

Output Error Try Catch is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Output Error Try Catch use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Output Error Try Catch?

Skills that share tags, products or a category with Output Error Try Catch: Error Handling (affaan-m/ECC, 276k stars), Handle PR CI Failure (DataDog/datadog-agent, 3.8k stars), Python Error Handling (wshobson/agents, 40k stars) and Error Handling (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Error Try Catch?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

Source: growthxai/output on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.