output-dev-http-client-create

Create shared HTTP clients in src/shared/clients using httpClient from @outputai/http.

430|12|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/growthxai/output --skill output-dev-http-client-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: output-dev-http-client-create
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-http-client-create
Command: npx skills add https://github.com/growthxai/output --skill output-dev-http-client-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create shared HTTP clients for Output SDK workflows to ensure consistent API usage, error handling, and credentials management across all projects.

Core Features & Use Cases

  • Centralized client creation in src/shared/clients/ using httpClient from @outputai/http.
  • Standardized import patterns, error handling rules, and credential usage across workflows.
  • Real-world applicability: wrapping external APIs, building reusable service wrappers, and enforcing consistent retry logic.

Quick Start

Create a new service client in src/shared/clients named {service}_client.ts using httpClient, then import and use it in your workflows.

Frequently Asked Questions about output-dev-http-client-create

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

FAQPage Schema
How do I standardize API calls and error handling across multiple TypeScript workflows?

You standardize API calls by creating shared HTTP clients in src/shared/clients/{service}_client.ts using httpClient from @outputai/http, ensuring consistent retry logic, typed interfaces, and credential management across all workflows.

What is the best way to share HTTP client configurations for external API integrations?

The best way to share HTTP client configurations is centralizing them in a dedicated src/shared/clients/ directory, wrapping external APIs with httpClient from @outputai/http to enforce standardized import patterns and error handling rules.

Can I use @outputai/http to build reusable service wrappers with typed response interfaces?

Yes, @outputai/http allows you to build reusable service wrappers by defining typed interfaces for responses within a centralized client file, standardizing how external service calls handle credentials and return data.

How do I set up consistent retry logic for external API calls in an SDK workflow?

You set up consistent retry logic by implementing a centralized HTTP client using @outputai/http, which standardizes the retry behavior and error handling rules across every workflow that imports the shared service client.

Do I need to create a separate client file for each external service I integrate?

Yes, you create a separate {service}_client.ts file within the src/shared/clients/ directory for each external service, ensuring credentials, error handling, and API call patterns remain isolated and maintainable.