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

Installs 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.
137 charsno explicit “when” trigger
Intermediate

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

You give it
API host or tool reference with method and path tokens
You get back
Validated OpenAPI JSON, list of operations, or dry-run request output

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

  1. Discover the tool spec source

    • Prefer manifest: https://<host>/.well-known/wacli.json
    • If absent, wacli may fall back to:
      • https://<host>/openapi.json
      • https://<host>/swagger.json
    • If you need custom aliases/headers/auth locally, create:
      • $XDG_CONFIG_HOME/wacli/tools/<tool>.json
  2. Validate OpenAPI JSON (internal check)

    • wacli oas validate <file_or_url>
    • Exit codes:
      • 0: ok
      • 2: unsupported OpenAPI version (valid JSON)
      • 3: invalid JSON or missing required fields
  3. List available operations

    • wacli help <tool_ref>
  4. 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-run
  • wacli example.org get repos alice demo issues page=2 --dry-run
  • wacli 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
  1. 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).

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.json manifest on the host, or ensure openapi.json/swagger.json exists at root.
  • 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.

SkillInstallsUpdatedSafetyDifficulty
wacli (this skill)06moNo flagsIntermediate
api-developer02moReviewIntermediate
api-tester01moReviewIntermediate
n8n-expression-syntax64moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry