Use when combining multiple OpenAPI specs, or have microservices with separate spec files
Installation
$skills install @speakeasy-api/merge-openapi-specs
Claude Code
Cursor
Copilot
Codex
Antigravity
Details
Repositoryspeakeasy-api/speakeasy
Pathskills/merge-openapi-specs/SKILL.md
Branchmain
Scoped Name@speakeasy-api/merge-openapi-specs
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: merge-openapi-specs description: Use when combining multiple OpenAPI specs, or have microservices with separate spec files
merge-openapi-specs
Use speakeasy merge to combine multiple specs into one.
Command
speakeasy merge -o <output-path> <spec1> <spec2> [spec3...]
Example
# Merge two specs
speakeasy merge -o combined.yaml ./api/users.yaml ./api/orders.yaml
# Merge multiple specs
speakeasy merge -o combined.yaml ./specs/*.yaml
Use Cases
- Microservices with separate specs per service
- API versioning with multiple spec files
- Combining public and internal API specs
Conflict Resolution
When specs have conflicts:
- Later specs override earlier ones for duplicate paths
- Schema conflicts may require manual resolution
- Review merged output for correctness
More by speakeasy-api
View allapply-openapi-overlay
377Use when applying an overlay file to a spec
get-ai-suggestions
377Use when SDK method names are ugly, wanting to improve operation IDs, or asking "how can I improve my spec"
diagnose-generation-failure
377name: diagnose-generation-failure
validate-openapi-spec
377Use when checking if an OpenAPI spec is valid, looking for errors, or running `speakeasy lint`
