How this skill is triggered — by the user, by Claude, or both
Slash command
/oastools:generate-codeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call `parse` to get an overview of the API:
Call parse to get an overview of the API:
{"spec": {"file": "<path>"}}
Report the API title, version, number of operations and schemas. This helps set expectations for what will be generated.
Ask the user what they need. The generate tool supports three output modes:
| Option | What it generates |
|---|---|
types | Go type definitions for all schemas |
client | HTTP client with methods for each operation (includes types) |
server | Server interface and handler stubs (includes types) |
Also determine:
output_dir (required) -- Where to write the generated filespackage_name (optional, default: api) -- Go package name for the generated codeCall the generate tool:
{
"spec": {"file": "<path>"},
"client": true,
"output_dir": "./generated",
"package_name": "petstore"
}
The tool returns a manifest of generated files with names and sizes. Review:
success is false, explain what went wrongRead the generated files and provide a summary of the key types and functions.
Based on what was generated, suggest next steps:
For types only:
interface{} fields)For client:
For server:
npx claudepluginhub erraggy/oastools --plugin oastoolsGenerates type-safe client SDKs in TypeScript, Python, Go, Java from OpenAPI specs with auth, retries, pagination, and tests.
Generates OpenAPI 3.0+ specs from existing API code, enhances with schemas/examples/errors, creates interactive docs/SDKs, and validates compliance.
Generates and maintains OpenAPI 3.1 specifications from code, design-first specs, and validation patterns for RESTful APIs. Use for API documentation, SDK generation, and contract compliance.