output-error-http-client

Migrate Output SDK steps from axios or fetch to httpClient from @outputai/http.

430|12|Updated Mar 13, 2026

Search Tags:#fetch #tracing #http #error-handling #retry #axios #http-client

Ready to run

npx skills add https://github.com/growthxai/output --skill output-error-http-client

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: output-error-http-client
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-error-http-client
Command: npx skills add https://github.com/growthxai/output --skill output-error-http-client

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and fix issues caused by using axios, fetch, or other HTTP clients directly instead of Output SDK's httpClient from @outputai/http. The Output SDK client provides tracing, automatic retries, and better error handling.

Core Features & Use Cases

Ensures requests are traced in workflow history with timing and context.
Enforces standardized error handling and automatic retries for transient failures.
Guides migration from plain HTTP calls to the Output SDK httpClient in common integration scenarios.

Quick Start

Replace direct HTTP calls (axios or fetch) with the httpClient from @outputai/http in your Output SDK steps.

Frequently Asked Questions about output-error-http-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why are my HTTP requests not showing up in workflow tracing history?▼

Untraced requests occur when using axios or fetch directly instead of the Output SDK httpClient from @outputai/http, which automatically records timing and context in workflow history.

How do I migrate axios calls to the Output SDK httpClient in my steps?▼

Replace direct axios calls with httpClient from @outputai/http to enforce standardized error handling, automatic retries for transient failures, and request tracing across Output SDK steps.

What is the best way to handle HTTP error handling and retries in Output SDK steps?▼

Use httpClient from @outputai/http for HTTP error handling in Output SDK steps, which provides standardized error details and automatic retries for transient failures out of the box.

Does fetch work with Output SDK tracing and retry mechanisms?▼

Plain fetch calls bypass Output SDK tracing, retries, and standardized error handling; you must migrate to httpClient from @outputai/http to ensure all requests are traced and retried properly.

Why does my Output SDK step fail with missing error details on HTTP failures?▼

Missing error details happen when using raw fetch or axios instead of the Output SDK httpClient, which standardizes error responses with full context for diagnosing HTTP failures in workflow steps.