Install any skill in seconds. Free to start, no credit card required.
Get Started Free →growthxai/output-error-http-client
Fix HTTP client misuse in Output SDK steps.
Passed 22 of 22 test cases with the skill, and 7 of 22 without it.
and 21 more in the full report
15 fixed7 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are migrating an update function from `axios.put('https://api.example.com/users/123', { name: 'Updated' })` to Output's standard HTTP client inside a workflow step. Provide the updated TypeScript step definition.
| Checked | Without skill | With skill |
|---|---|---|
| Uses client.put to send the request | Missed | Passed |
| Passes payload via the json option | Missed | Passed |
The instructions your model reads when the skill loads.
This skill helps diagnose and fix issues caused by using axios, fetch, or other HTTP clients directly instead of Output SDK's createKyClient from @outputai/core/http. The Output SDK client provides tracing, automatic retries, and better error handling.
You're seeing:
Using axios, fetch, or other HTTP clients directly bypasses Output SDK's:
// WRONG: Using axios
import axios from 'axios';
export const fetchData = step( {
name: 'fetchData',
fn: async input => {
const response = await axios.get( 'https://api.example.com/data' );
return response.data;
}
} );
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.