Execute API requests for platforms with OpenAPI specs, including discovery and auth.
Install
mkdir -p .claude/skills/wacli-kogeletey && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16233" && unzip -o skill.zip -d .claude/skills/wacli-kogeletey && rm skill.zipInstalls to .claude/skills/wacli-kogeletey
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use wacli to make API requests to any platform that exposes OpenAPI/Swagger JSON; includes discovery, auth, dry-run, and troubleshooting.Key capabilities
- →Discover tool spec sources from well-known or swagger endpoints
- →Validate OpenAPI JSON documents
- →List available API operations
- →Perform dry-run requests before real API calls
- →Handle bearer token authentication
- →Apply local overrides for custom aliases, headers, or auth
How it works
The skill discovers API schemas, validates them, lists available operations, and allows dry-run requests. It also manages authentication and local overrides for API interactions.
Inputs & outputs
When to use wacli
- →Testing API endpoints
- →Validating OpenAPI schemas
- →Debugging API integration workflows
About this skill
wacli: API Requests To Platforms
Use this skill when you want to call a platform API via wacli (list endpoints, test routing, make a request, handle auth).
Quick Workflow
-
Discover the tool spec source
- Prefer manifest:
https://<host>/.well-known/wacli.json - If absent,
waclimay fall back to:https://<host>/openapi.jsonhttps://<host>/swagger.json
- If you need custom aliases/headers/auth locally, create:
$XDG_CONFIG_HOME/wacli/tools/<tool>.json
- Prefer manifest:
-
Validate OpenAPI JSON (internal check)
wacli oas validate <file_or_url>- Exit codes:
0: ok2: unsupported OpenAPI version (valid JSON)3: invalid JSON or missing required fields
-
List available operations
wacli help <tool_ref>
-
Dry-run a request (recommended before real calls)
wacli <tool_ref> [method] <path_tokens...> [key=value...] --dry-run
Examples:
wacli example.org get health --dry-runwacli example.org get repos alice demo issues page=2 --dry-runwacli example.org post repos alice demo issues --json '{"title":"hi"}' --dry-run
Shell Mode
If you want to call tools directly as commands:
eval "$(wacli shell bash example.org)"- Then run:
example.org get health --dry-run
- Auth (bearer)
- Store token:
wacli auth <tool_ref> --bearer TOKEN - Then run the request normally (token will be applied in both manifest mode and fallback mode).
- Store token:
Local Overrides
If you need custom aliases/headers/auth for a platform without publishing a .well-known/wacli.json, create:
$XDG_CONFIG_HOME/wacli/tools/<tool>.json
Then wacli will use your local settings and prefer any cached spec from wacli ain <tool_ref>.
Troubleshooting
manifest not found ...and no fallback:- Provide a
.well-known/wacli.jsonmanifest on the host, or ensureopenapi.json/swagger.jsonexists at root.
- Provide a
missing or invalid 'paths':- The JSON is not an OpenAPI document usable for routing.
ambiguous operation match:- Your token sequence matches multiple templates; add more path tokens or use a different aliasing strategy in the manifest.
When not to use it
- →When a manifest is not found and no fallback exists
- →When the OpenAPI JSON is missing or has invalid 'paths'
- →When an ambiguous operation match occurs due to token sequence
Limitations
- →Requires a `.well-known/wacli.json` manifest or `openapi.json`/`swagger.json` at the root for discovery.
- →An OpenAPI document must have valid 'paths' for routing.
- →Ambiguous operation matches can occur if path tokens are insufficient.
How it compares
This skill automates API interaction by discovering schemas, validating them, and enabling dry-run requests, providing a structured approach compared to manual API testing.
Compared to similar skills
wacli side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| wacli (this skill) | 0 | 6mo | No flags | Intermediate |
| api-developer | 0 | 2mo | Review | Intermediate |
| api-tester | 0 | 1mo | Review | Intermediate |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
api-developer
Vinix24
API developer specializing in clean, well-documented REST APIs
api-tester
criptogus
Test and document API endpoints - validate responses, check status, generate examples
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
claude-in-chrome-troubleshooting
trailofbits
Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
openrouter-common-errors
jeremylongshore
Execute diagnose and fix common OpenRouter API errors. Use when troubleshooting failed requests. Trigger with phrases like 'openrouter error', 'openrouter not working', 'openrouter 401', 'openrouter 429', 'fix openrouter'.
linear-common-errors
jeremylongshore
Diagnose and fix common Linear API errors. Use when encountering Linear API errors, debugging integration issues, or troubleshooting authentication problems. Trigger with phrases like "linear error", "linear API error", "debug linear", "linear not working", "linear authentication error".