Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alexknowshtml/api2cli
Generate a working CLI from any API, then wrap it in a Claude Code skill. Point it at API docs, a live URL, or a peek-api capture and get a dual-mode Commander.js CLI (human + agent output) plus a ready-to-use skill folder.
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
and 8 more in the full report
10 fixed8 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are generating the main entry file for `inventory-service` at `scripts/inventory.ts`. What executable shebang header line should be placed at line 1 so the TypeScript script runs directly without manual build steps?
| Checked | Without skill | With skill |
|---|---|---|
| Specify `#!/usr/bin/env npx tsx` as the top-line shebang. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate a working Node.js CLI from any API, then wrap it in a Claude Code skill. Discovers endpoints, scaffolds a dual-mode Commander.js CLI with a full-featured API client, and creates a skill folder so Claude knows how to use it.
Ask the user:
Determine which discovery paths to use based on what they provide:
| Input | Discovery Path |
|---|---|
Docs URL (e.g., https://docs.stripe.com/api) | Docs parsing + active probing |
Base URL (e.g., https://api.example.com/v1) | Active probing |
peek-api capture dir (e.g., ./peek-api-linkedin/) | Read existing catalog |
| Live website URL | Suggest running peek-api first, then active probing |
Also ask:
Use all applicable discovery paths. Combine results into a single catalog.
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.