http-client

Detect axios, ky, or fetch and apply matching TypeScript API templates.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/opzero1/op1 --skill http-client
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-client
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/http-client
Command: npx skills add https://github.com/opzero1/op1 --skill http-client

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to standardize HTTP client usage by detecting and aligning API calls with the project's chosen client (axios, ky, or native fetch).

Core Features & Use Cases

  • Client detection and automatic pattern selection for axios, ky, or fetch.
  • Per-client pattern templates: Axios instance creation, request/response interceptors; Ky hooks; Native fetch wrapper with types.
  • Error handling and retries: Unified error handling patterns and retry strategies per client.
  • Type-safe interfaces: TypeScript generics for request/response data.

Use case: When migrating a codebase to a single HTTP client or when adding new API calls, this skill provides consistent templates and adapters to reduce boilerplate and bugs.

Quick Start

Detect the project's HTTP client automatically, then scaffold a sample API call using the detected client patterns. Integrate the generated patterns into your API utilities and run tests.

Frequently Asked Questions about http-client

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

FAQPage Schema
How do I standardize HTTP client usage across a TypeScript codebase?

To standardize HTTP client usage, you can apply pattern templates that align API calls with your project's chosen client, ensuring consistent request handling, interceptors, and type-safe responses. This reduces boilerplate and bugs across teams.

How do I set up axios request and response interceptors with TypeScript?

Setting up axios interceptors with TypeScript involves applying client-specific pattern templates for instance creation and request/response interceptors. This provides type-safe API definitions and unified error handling for your HTTP requests.

What's the best way to add retry logic and error handling to native fetch?

Adding retry logic and error handling to native fetch requires using a typed fetch wrapper with unified error patterns. This approach applies consistent retry strategies per client while maintaining type-safe interfaces for requests and responses.

Does this HTTP client skill automatically detect whether I am using axios, ky, or fetch?

Yes, the skill automatically detects the project's HTTP client, whether it is axios, ky, or native fetch. It then applies the corresponding per-client pattern templates to scaffold API calls, hooks, and adapters.

How do I migrate a codebase to a single HTTP client like ky?

Migrating to a single HTTP client like ky involves detecting the current client and applying consistent templates and adapters. This standardizes API calls, hooks, and error handling, reducing boilerplate during the transition.

Can I get type-safe API definitions for requests and responses with ky hooks?

Yes, you can achieve type-safe API definitions for requests and responses using TypeScript generics. The skill applies per-client templates for ky hooks, ensuring unified error handling and retry strategies maintain type safety.