name: diagnose-generation-failure
Installation
$skills install @speakeasy-api/diagnose-generation-failure
Claude Code
Cursor
Copilot
Codex
Antigravity
Details
Repositoryspeakeasy-api/speakeasy
Pathskills/diagnose-generation-failure/SKILL.md
Branchmain
Scoped Name@speakeasy-api/diagnose-generation-failure
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: diagnose-generation-failure
description: Use when SDK generation failed, seeing "Step Failed: Workflow", or speakeasy run errors
diagnose-generation-failure
When SDK generation fails, determine the root cause and fix strategy.
Diagnosis Steps
-
Run lint to get detailed errors:
speakeasy lint openapi -s <spec-path> -
Categorize issues:
- Fixable with overlays: Missing descriptions, poor operation IDs
- Requires spec fix: Invalid schema, missing required fields
- Requires user input: Design decisions, authentication setup
Decision Framework
| Issue Type | Fix Strategy | Example |
|---|---|---|
| Missing operationId | Overlay | Use speakeasy suggest operation-ids |
| Missing description | Overlay | Add via overlay |
| Invalid $ref | Ask user | Broken reference needs spec fix |
| Circular reference | Ask user | Design decision needed |
| Missing security | Ask user | Auth design needed |
What NOT to Do
- Do NOT disable lint rules to hide errors
- Do NOT try to fix every issue one-by-one
- Do NOT modify source spec without asking
- Do NOT assume you can fix structural problems
Strategy Document
For complex issues, produce a document:
## OpenAPI Spec Analysis
### Blocking Issues (require user input)
- [List issues that need human decision]
### Fixable Issues (can use overlays)
- [List issues with proposed overlay fixes]
### Recommended Approach
[Your recommendation]
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"
merge-openapi-specs
377Use when combining multiple OpenAPI specs, or have microservices with separate spec files
validate-openapi-spec
377Use when checking if an OpenAPI spec is valid, looking for errors, or running `speakeasy lint`
