Agent skill

Output Dev HTTP Client Create

by growthxai in growthxai/output

Create shared HTTP clients in src/shared/clients/ for Output SDK workflows.

Apache-2.0Auto-check passedBackend & APIs

Install Output Dev HTTP Client Create

skills CLI
$ npx skills add growthxai/output --skill output-dev-http-client-create -a claude-code

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

GitHub CLI
$ gh skill install growthxai/output output-dev-http-client-create --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-dev-http-client-create .claude/skills/output-dev-http-client-create && 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-dev-http-client-create
GitHub stars
440
Token cost
~4.9k tokens
SKILL.md length
896 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create shared HTTP clients in src/shared/clients/ for Output SDK workflows.

  • Works in 5 steps: Use Credentials for API Keys → Document Functions with JSDoc → Use Consistent Timeouts → …
  • Integrating external APIs
  • SKILL.md covers Overview, When to Use This Skill, Location Convention and Other Shared Code Locations, plus 8 more sections
  • Calls npx; reaches api.service.com and r.jina.ai; needs API_KEY and JINA_API_KEY

What it does

Output Dev HTTP Client Create is an agent skill from growthxai/output. Create shared HTTP clients in src/shared/clients/ for Output SDK workflows. Use when integrating external APIs, creating service wrappers, or standardizing HTTP operations.

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

It sits in Backend & APIs, covering Third-party API integration. 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

  • Integrating external APIs
  • Creating service wrappers
  • Standardizing HTTP operations

Example prompts

  • “/output-dev-http-client-create”

Requirements

  • Node.js
  • A credential in SERVICE_API_KEY
  • A credential in API_KEY
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Use Credentials for API Keys
  2. Document Functions with JSDoc
  3. Use Consistent Timeouts
  4. Consume or Cancel Response Bodies
  5. Export TypeScript Interfaces

What it can do on your machine

Read from SKILL.md and the folder at commit 52b51ac. 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:

    • Read
    • Write
    • Edit
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.service.com
    • r.jina.ai

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY
    • JINA_API_KEY
    • SERVICE_API_KEY

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

Context cost

Output Dev HTTP Client Create loads about 4.9k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 896 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 52b51ac, republished under its Apache-2.0 licence (© growthxai). 896 words, ~4,937 tokens.

Download SKILL.mdSave it as .claude/skills/output-dev-http-client-create/SKILL.md (or your agent's skills folder).
name
output-dev-http-client-create
description
Create shared HTTP clients in src/shared/clients/ for Output SDK workflows. Use when integrating external APIs, creating service wrappers, or standardizing HTTP operations.
allowed-tools
Read, Write, Edit, Glob

Creating HTTP Clients

Overview

This skill documents how to create shared HTTP clients for Output SDK workflows. Clients are stored in src/shared/clients/ and shared across all workflows to ensure consistent error handling, retry logic, and API integration patterns.

When to Use This Skill

  • Integrating a new external API service
  • Creating a reusable HTTP wrapper for a service
  • Standardizing error handling for API calls
  • Moving inline HTTP logic to a shared client

Location Convention

HTTP clients are stored in the shared clients folder:

src/shared/clients/
├── gemini_client.ts     # Google Gemini API client
├── jina_client.ts       # Jina AI client
├── perplexity_client.ts # Perplexity API client
└── {service}_client.ts  # Your new client

Important: Clients are shared across ALL workflows. Do NOT create per-workflow HTTP clients.

Other Shared Code Locations

src/shared/
├── clients/     # API clients (this skill)
├── utils/       # Utility functions & helpers
├── services/    # Business logic services
├── steps/       # Shared step definitions (optional)
└── evaluators/  # Shared evaluators (optional)

Import Pattern in Workflows

Use relative imports from workflow files to shared clients:

typescript
// CORRECT - Relative path from workflow steps.ts
import { GeminiImageService } from '../../shared/clients/gemini_client.js';
import { parseResumeWithJina } from '../../shared/clients/jina_client.js';

// From shared steps (if used)
import { JinaClient } from '../clients/jina_client.js';

Critical Import Rules

HTTP Client Import
typescript
// CORRECT - Use @outputai/http wrapper
import { createKyClient } from '@outputai/http';

// WRONG - Never use axios directly
import axios from 'axios';
Error Types Import
typescript
// CORRECT - Import error types from @outputai/core
import { FatalError, ValidationError } from '@outputai/core';

// WRONG - Custom error classes
class MyCustomError extends Error { ... }
Credentials Import
typescript
// CORRECT - Use @outputai/core/credentials for secrets
import { credentials } from '@outputai/core/credentials';
const apiKey = credentials.require('service.api_key');

// WRONG - Never use process.env for secrets
const apiKey = process.env.SERVICE_API_KEY;
Cost Tracking Import
typescript
// CORRECT - Attach spend to paid API calls with @outputai/http
import { addRequestCost, createKyClient } from '@outputai/http';

// WRONG - Tracking cost yourself in a side table, or skipping it for paid APIs

Basic Client Structure

Simple Function-Based Client
typescript
import { FatalError, ValidationError } from '@outputai/core';
import { createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';

const API_KEY = credentials.require('service.api_key');
const BASE_URL = 'https://api.service.com';

const client = createKyClient({
  prefix: BASE_URL,
  headers: {
    Authorization: `Bearer ${API_KEY}`,
    Accept: 'application/json'
  },
  timeout: 30000,
  retry: {
    limit: 3,
    statusCodes: [408, 429, 500, 502, 503, 504]
  }
});

/**
 * Fetch data from the service
 *
 * @param query - Search query string
 * @returns Processed response data
 * @throws {FatalError} If authentication fails or resource not found
 * @throws {ValidationError} If temporary error occurs
 */
export async function fetchServiceData(query: string): Promise<ServiceResponse> {
  const response = await client.get('endpoint', {
    searchParams: { q: query }
  });

  const data = await response.json();

  if (!data.results) {
    throw new FatalError('No results returned from service');
  }

  return data;
}
Class-Based Client
typescript
import { FatalError, ValidationError } from '@outputai/core';
import { createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';

export interface ServiceOptions {
  model?: string;
  timeout?: number;
}

export class ServiceClient {
  private readonly client: ReturnType<typeof createKyClient>;
  private readonly model: string;

  constructor(apiKey?: string) {
    const key = apiKey ?? credentials.require('service.api_key');

    this.client = createKyClient({
      prefix: 'https://api.service.com',
      headers: {
        Authorization: `Bearer ${key}`,
        'Content-Type': 'application/json'
      },
      timeout: 30000,
      retry: {
        limit: 3,
        statusCodes: [408, 429, 500, 502, 503, 504]
      }
    });

    this.model = 'default-model';
  }

  async process(input: ProcessInput): Promise<ProcessOutput> {
    try {
      const response = await this.client.post('process', {
        json: {
          model: this.model,
          input
        }
      });

      return await response.json();
    } catch (error: unknown) {
      const err = error as { status?: number; message?: string };

      if (err.status === 429) {
        throw new ValidationError(`Rate limit exceeded: ${err.message}`);
      }

      if (err.status === 401 || err.status === 403) {
        throw new FatalError(`Authentication failed: ${err.message}`);
      }

      throw new ValidationError(`Service call failed: ${err.message}`);
    }
  }
}

Real-World Examples

Example 1: Jina Client (Function-Based)
typescript
import { FatalError } from '@outputai/core';
import { createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';

const JINA_API_KEY = credentials.require('jina.api_key');
const JINA_BASE_URL = 'https://r.jina.ai';

const client = createKyClient({
  prefix: JINA_BASE_URL,
  headers: {
    Authorization: `Bearer ${JINA_API_KEY}`,
    Accept: 'application/json'
  },
  timeout: 30000,
  retry: {
    limit: 3,
    statusCodes: [408, 413, 429, 500, 502, 503, 504]
  }
});

/**
 * Parse PDF resume using Jina Reader API
 */
export async function parseResumeWithJina(base64Pdf: string): Promise<string> {
  const response = await client.post('', {
    json: { pdf: base64Pdf },
    headers: {
      'Content-Type': 'application/json'
    }
  });

  const data: {
    data: {
      content: string;
      title?: string;
    };
  } = await response.json();

  if (!data.data?.content) {
    throw new FatalError('No content returned from Jina PDF parser');
  }

  return data.data.content;
}

/**
 * Scrape text content from URL using Jina Reader
 */
export async function scrapeTextWithJina(url: string): Promise<string> {
  const response = await client.get(url, {
    headers: {
      'X-Return-Format': 'text',
      'X-No-Cache': 'true',
      'X-Timeout': '30'
    }
  });

  const data: {
    data: {
      text?: string;
      content?: string;
    };
  } = await response.json();

  const textContent = data.data?.text || data.data?.content;

  if (!textContent) {
    throw new FatalError(`No text content returned from URL: ${url}`);
  }

  return textContent;
}
Example 2: Gemini Client (Class-Based)
typescript
import { GoogleGenerativeAI } from '@google/generative-ai';
import { FatalError, ValidationError } from '@outputai/core';
import { credentials } from '@outputai/core/credentials';

export interface GeminiImageGenerationOptions {
  prompt: string;
  referenceImages?: Array<{
    inlineData: {
      mimeType: string;
      data: string;
    };
  }>;
  aspectRatio?: string;
  resolution?: string;
  numberOfImages?: number;
}

export class GeminiImageService {
  private readonly client: GoogleGenerativeAI;
  // current as of 2026-05-04 — run output-dev-model-selection for the latest
  private readonly model: string = 'gemini-3-pro-image';

  constructor(apiKey = credentials.require('google.api_key')) {
    if (!apiKey) {
      throw new FatalError(
        'GeminiImageService: No API Key provided (google.api_key credential).'
      );
    }
    this.client = new GoogleGenerativeAI(apiKey);
  }

  async generateImage(options: GeminiImageGenerationOptions): Promise<string[]> {
    const { prompt, referenceImages = [], aspectRatio = '1:1', resolution = '1K', numberOfImages = 1 } = options;

    try {
      const model = this.client.getGenerativeModel({ model: this.model });

      const parts: Array<{ text: string } | { inlineData: { mimeType: string; data: string } }> = [];

      if (referenceImages.length > 0) {
        referenceImages.forEach(img => parts.push(img));
      }

      const finalPrompt = `${prompt}\n\nGenerate this as a ${aspectRatio} aspect ratio image at ${resolution} resolution.`;
      parts.push({ text: finalPrompt });

      const result = await model.generateContent({
        contents: [{ role: 'user', parts }],
        generationConfig: {
          temperature: 1.0,
          topP: 0.95,
          candidateCount: numberOfImages,
          maxOutputTokens: 8192
        }
      });

      const images: string[] = [];
      const candidates = result.response.candidates || [];

      for (const candidate of candidates) {
        if (candidate.content?.parts) {
          for (const part of candidate.content.parts) {
            if (part.inlineData?.data) {
              images.push(part.inlineData.data);
            }
          }
        }
      }

      if (images.length === 0) {
        throw new ValidationError('No images were generated by Gemini');
      }

      return images;
    } catch (error: unknown) {
      const err = error as { status?: number; message?: string };

      if (err.status === 429) {
        throw new ValidationError(`Gemini rate limit exceeded: ${err.message}`);
      }

      if (err.status === 401 || err.status === 403) {
        throw new FatalError(`Gemini authentication failed: ${err.message}`);
      }

      throw new ValidationError(`Gemini image generation failed: ${err.message}`);
    }
  }
}

Error Handling Patterns

HTTP Status Code Handling
typescript
const RETRY_STATUS_CODES = [408, 429, 500, 502, 503, 504];
const FATAL_STATUS_CODES = [401, 403, 404];

const client = createKyClient({
  retry: {
    limit: 3,
    statusCodes: RETRY_STATUS_CODES
  },
  hooks: {
    beforeError: [
      ( { error } ) => {
        const status = error.response?.status;
        const message = error.message;

        if (status && FATAL_STATUS_CODES.includes(status)) {
          throw new FatalError(`HTTP ${status} error: ${message}`);
        }

        throw new ValidationError(`HTTP request failed: ${message}`);
      }
    ]
  }
});
Error Type Guidelines
Status CodeError TypeReason
401, 403FatalErrorAuth failures won't succeed on retry
404FatalErrorResource doesn't exist
408ValidationErrorTimeout, may succeed on retry
429ValidationErrorRate limit, will succeed after wait
500+ValidationErrorServer errors may be temporary

Attaching Request Cost (Paid APIs)

If the service a client wraps charges money per request, attach that cost to the request's trace so it shows up in npx output workflow cost (see output-dev-workflow-cost) and in any cost:http:request hook handlers (see output-dev-cost-hooks).

Do this on the client itself, in an afterResponse hook — not at each call site. That way every function or method that goes through the client is costed automatically, and nobody integrating with the client later has to remember to do it.

addRequestCost(response, totalUsd) only works on a response that came from outputFetch or createKyClient — including a response.clone() of one, so it's safe to call from inside an afterResponse hook (ky passes hooks a clone). If the response didn't originate from @outputai/http, addRequestCost no-ops with a console warning.

There are two common pricing shapes for paid third-party APIs:

Metered APIs (cost is in the response)

Some APIs report what a specific call cost — in a response header or a JSON field (credits used, units billed, etc). Read that field and pass it straight to addRequestCost. Guard against free or cached responses that legitimately report zero cost.

typescript
import { addRequestCost, createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';

const API_KEY = credentials.require('service.api_key');

const client = createKyClient({
  prefix: 'https://api.service.com',
  headers: { Authorization: `Bearer ${API_KEY}` },
  timeout: 30000,
  retry: { limit: 3, statusCodes: [408, 429, 500, 502, 503, 504] },
  hooks: {
    afterResponse: [
      async (_request, _options, response) => {
        // Errored responses (4xx/5xx) and retried attempts aren't billed the
        // same as a successful call — skip them rather than over-counting.
        if (!response.ok) {
          return;
        }

        try {
          const body = await response.clone().json() as { creditsUsed?: number; cached?: boolean };

          // Skip cached or free responses that legitimately cost nothing.
          if (body.cached || !body.creditsUsed) {
            return;
          }

          const usdPerCredit = 0.01;
          addRequestCost(response, body.creditsUsed * usdPerCredit);
        } catch {
          // Never let cost tracking break the request.
        }
      }
    ]
  }
});
Flat-rate / subscription APIs (assign a notional cost)

When a service is billed as a flat monthly fee or subscription tier, there's no true marginal cost per call — but recording some per-call figure keeps spend comparable across services in workflow cost and any cost dashboards. Assign a notional per-call USD rate as a constant, overridable by a non-secret environment variable so it can be tuned without a code change.

typescript
import { addRequestCost, createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';

const API_KEY = credentials.require('service.api_key');

// Notional per-call cost for a flat-rate subscription. Not a secret, so a
// plain env var is fine here — unlike API keys, which must go through
// @outputai/core/credentials.
const NOTIONAL_COST_USD = Number(process.env.SERVICE_NOTIONAL_COST_USD ?? 0.005);

const client = createKyClient({
  prefix: 'https://api.service.com',
  headers: { Authorization: `Bearer ${API_KEY}` },
  timeout: 30000,
  retry: { limit: 3, statusCodes: [408, 429, 500, 502, 503, 504] },
  hooks: {
    afterResponse: [
      (_request, _options, response) => {
        // Errored responses (4xx/5xx) and retried attempts aren't billed the
        // same as a successful call — skip them rather than over-counting.
        if (!response.ok) {
          return;
        }

        addRequestCost(response, NOTIONAL_COST_USD);
      }
    ]
  }
});

The constant above is a placeholder — config/costs.yml (see output-dev-workflow-cost) can override the actual dollar figure per service afterward, without another code change. Add a services.<name> entry with type: request, a matching url_pattern, and an endpoints.<name> block giving pattern + price for the call. (default_price only applies inside a models/model_path entry, for picking a fallback price when the request's model isn't in models — it does nothing paired with a bare url_pattern.) Prefer that file over inventing more env vars once you have more than one or two notional rates to tune.

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

Rules:

  • Never throw from an afterResponse cost hook — a throw there fails the request itself. Wrap body parsing in try/catch and silently skip on parse failure.
  • The hook fires once per attempt, including retries — skip !response.ok attempts unless you know the API bills failed requests too (the framework itself does count a recorded cost event "regardless of HTTP status" once one exists — the event is proof of a charge). When in doubt, check the provider's billing docs before adding the guard.
  • Only do this for paid third-party APIs. Free or internal services don't need it.
  • Skip this pattern for LLM providers — those costs are computed automatically from token usage via llm:generation:metering. addRequestCost is for non-LLM HTTP calls only.
  • To consume these costs elsewhere (forward to your own observability system, log them, alert on them), see output-dev-cost-hooks.

Best Practices

1. Use Credentials for API Keys

Prefer @outputai/core/credentials over process.env for secrets management. See output-dev-credentials skill for details.

typescript
import { credentials } from '@outputai/core/credentials';

// credentials.require() throws MissingCredentialError if not found
const apiKey = credentials.require('service.api_key');

// credentials.get() returns undefined or default if not found
const region = credentials.get('aws.region', 'us-east-1');
2. Document Functions with JSDoc
typescript
/**
 * Fetch user profile from external service
 *
 * @param userId - Unique user identifier
 * @returns User profile data
 * @throws {FatalError} If user not found or auth fails
 * @throws {ValidationError} If temporary error occurs
 *
 * @example
 * const profile = await fetchUserProfile('user-123');
 */
export async function fetchUserProfile(userId: string): Promise<UserProfile> {
  // ...
}
3. Use Consistent Timeouts
typescript
// Standard timeout: 30 seconds
timeout: 30000

// Long-running operations: 60 seconds
timeout: 60000
4. Consume or Cancel Response Bodies

createKyClient follows Fetch response-body semantics: callers own returned response bodies. Prefer body readers like .json() or .text() when the payload is needed. If a request only reads metadata such as response.url, response.status, or headers, cancel the unused body in a finally block.

typescript
const response = await client.get( url );

try {
  return response.url;
} finally {
  await response.body?.cancel();
}

HEAD requests do not have response bodies, so this is only needed for methods that can return one.

5. Export TypeScript Interfaces
typescript
// Export interfaces for consumers
export interface ServiceResponse {
  data: {
    id: string;
    content: string;
  };
  metadata: {
    processedAt: string;
  };
}

Verification Checklist

  • Client file located in src/shared/clients/ directory
  • File named {service}_client.ts
  • createKyClient imported from @outputai/http (not axios)
  • FatalError and ValidationError imported from @outputai/core
  • API key validation in constructor/initialization
  • Retry configuration for appropriate status codes
  • FatalError used for 401, 403, 404 responses
  • ValidationError used for 429, 5xx responses
  • Non-HEAD responses are consumed or cancelled when only metadata is used
  • JSDoc documentation for exported functions
  • TypeScript interfaces exported for response types
  • Paid third-party API calls attach cost via addRequestCost in an afterResponse hook
  • output-dev-step-function - Using clients in step functions
  • output-dev-evaluator-function - Using clients in evaluators
  • output-dev-folder-structure - Understanding project layout
  • output-dev-credentials - Encrypted secrets management
  • output-dev-cost-hooks - Subscribing to cost events (cost:http:request, llm:generation:metering) for observability
  • output-error-http-client - Troubleshooting HTTP issues
  • output-error-try-catch - Proper error handling patterns

© 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-dev-http-client-create of growthxai/output.

Open the folder on GitHubat commit 52b51ac

Compare with similar skills

Output Dev HTTP Client Create 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 Dev HTTP Client Create compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Dev HTTP Client Create this skillgrowthxai/output440—~4.9kAutomated safety check: PassApache-2.0
Sub2API AdminWei-Shaw/sub2api43k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
ToolJet Marketplace Plugin BuilderToolJet/ToolJet41k—~2.1kAutomated safety check: PassAGPL-3.0
Firecrawl Search Integrationfirecrawl/firecrawl190k1 repos~1.1kAutomated safety check: PassISC
CoinGecko API Reference2025Emma/vibe-coding-cn23k2 repos~646Automated safety check: PassMIT

Similar skills

  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    43k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed
  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes
  • Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.

    41k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • Firecrawl Search Integration

    firecrawl/firecrawl

    Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL.

    190k GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed
  • CoinGecko API Reference

    2025Emma/vibe-coding-cn

    CoinGecko API documentation - cryptocurrency market data API, price feeds, market cap, volume, historical data. Use when integrating CoinGecko API, building…

    23k GitHub starsUsed in 2 repos~646 tokens
    Backend & APIsAuto-check passed
  • NEAR Intents Swap Integration

    internet-court/internet-court-skill

    Builds cross-chain token swaps and bridge flows with the NEAR Intents 1Click API: quotes, deposit addresses, per-chain deposits and status polling.

    6.4k GitHub starsUsed in 2 repos~939 tokens
    Backend & APIsAuto-check passed

More from growthxai/output

All 52 skills in this repo
  • Zod schema constraints that Anthropic rejects or silently ignores when sent as structured-output tool definitions via aiSdk.Output.object().

    440 GitHub stars~597 tokensUpdated today
    Auto-check passed
  • Output Build Workflow

    growthxai/output

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

    440 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.

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

    440 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.

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

    growthxai/output

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

    440 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Output Dev HTTP Client Create

What does Output Dev HTTP Client Create do?

Create shared HTTP clients in src/shared/clients/ for Output SDK workflows. Output Dev HTTP Client Create is an agent skill from growthxai/output. Create shared HTTP clients in src/shared/clients/ for Output SDK workflows.

When should I use Output Dev HTTP Client Create?

Output Dev HTTP Client Create fits situations like: integrating external APIs; creating service wrappers; standardizing HTTP operations.

How do I install Output Dev HTTP Client Create in Claude Code?

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

How do I install Output Dev HTTP Client Create in Codex?

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

Can I use Output Dev HTTP Client Create 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-dev-http-client-create -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-dev-http-client-create, .gemini/skills/output-dev-http-client-create, .github/skills/output-dev-http-client-create and .opencode/skills/output-dev-http-client-create in your project.

What does Output Dev HTTP Client Create need to run?

Going by SKILL.md and its folder, Output Dev HTTP Client Create needs the command-line tools its instructions call (npx) and credentials named API_KEY, JINA_API_KEY and SERVICE_API_KEY. Our summary lists: Node.js; A credential in SERVICE_API_KEY; A credential in API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob.

Does Output Dev HTTP Client Create access the network?

SKILL.md names 2 domains. In commands or code: api.service.com and r.jina.ai; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Output Dev HTTP Client Create safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Output Dev HTTP Client Create use?

Output Dev HTTP Client Create 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 Dev HTTP Client Create use?

About 4.9k tokens (SKILL.md is roughly 20k 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 Dev HTTP Client Create?

Skills that share tags, products or a category with Output Dev HTTP Client Create: Sub2API Admin (Wei-Shaw/sub2api, 43k stars), Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars), ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars) and Firecrawl Search Integration (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Dev HTTP Client Create?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 440 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 7, 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.