Agent skill

Diagnose Generation Failure

A skill your agent uses when SDK generation failed or seeing errors.

Apache-2.0Auto-check passedBackend & APIs

Install Diagnose Generation Failure

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .claude/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .claude/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .agents/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .agents/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .cursor/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .cursor/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/trycompai/comp.git --path .agents/skills/diagnose-generation-failure

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .gemini/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .gemini/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .github/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .github/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add trycompai/comp --skill diagnose-generation-failure -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install trycompai/comp diagnose-generation-failure --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trycompai/comp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/diagnose-generation-failure .opencode/skills/diagnose-generation-failure && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "diagnose-generation-failure" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/diagnose-generation-failure into .opencode/skills/diagnose-generation-failure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose-generation-failure", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: diagnose-generation-failure
GitHub stars: 2k
Token cost: ~938 tokens
SKILL.md length: 240 words
Files: 1
Skills in repo: 31
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when SDK generation failed or seeing errors.

Works in 2 steps: Run lint to get detailed errors → Categorize issues
SDK generation failed
SKILL.md covers When to Use, Inputs, Outputs and Diagnosis Steps, plus 6 more sections
Calls yq

What it does

Diagnose Generation Failure is an agent skill from trycompai/comp. Use when SDK generation failed or seeing errors. Triggers on "generation failed", "speakeasy run failed", "SDK build error", "workflow failed", "Step Failed", "why did generation fail"

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering OpenAPI specifications. The repository describes itself as: AI Native platform to get companies compliant - Vanta & Drata Alternative. The licence is Apache-2.0.

When your agent uses it

SDK generation failed
Generation failed
Speakeasy run failed
SDK build error

Example prompts

“generation failed”
“speakeasy run failed”
“SDK build error”
“/diagnose-generation-failure”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Run lint to get detailed errors
Categorize issues

What it can do on your machine

Read from SKILL.md and the folder at commit 0117612. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- yq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Diagnose Generation Failure loads about 938 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 240 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~938

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trycompai/comp at commit 0117612, republished under its Apache-2.0 licence (© trycompai). 240 words, ~938 tokens.

Download SKILL.mdSave it as .claude/skills/diagnose-generation-failure/SKILL.md (or your agent's skills folder).

name: diagnose-generation-failure
description: Use when SDK generation failed or seeing errors. Triggers on "generation failed", "speakeasy run failed", "SDK build error", "workflow failed", "Step Failed", "why did generation fail"
license: Apache-2.0

diagnose-generation-failure

When SDK generation fails, diagnose the root cause and determine the fix strategy.

When to Use

speakeasy run failed with errors
SDK generation produced unexpected results
User says: "generation failed", "SDK build error", "why did generation fail"

Inputs

Input	Required	Description
OpenAPI spec	Yes	Path to spec that failed generation
Error output	Helpful	Error messages from failed run

Outputs

Output	Description
Diagnosis	Root cause of failure
Fix strategy	Overlay vs spec fix vs user decision
Action items	Specific steps to resolve

Diagnosis Steps

Run lint to get detailed errors:

bash

speakeasy lint openapi --non-interactive -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

Troubleshooting Tree

PROBLEM
  │
  ├─ ResponseValidationError at runtime?
  │    └─ SDK types don't match server responses
  │         ├─ Run contract tests to identify mismatches
  │         └─ Fix spec or create overlay to correct types
  │
  ├─ SDK doesn't match live API behavior?
  │    ├─ Spec may have drifted from API
  │    │    → Run contract tests to detect drift
  │    └─ Third-party spec may be inaccurate
  │         → Validate with contract testing before trusting
  │
  ├─ Type mismatch errors in generated SDK?
  │    ├─ At compile time → Check spec schema definitions
  │    └─ At runtime → Server returns unexpected types
  │                    → Contract testing required
  │
  └─ Enum value not recognized?
       └─ API returned value not in spec enum
            ├─ Add missing value to spec/overlay
            └─ Or use open enums for anti-fragility

Working with Large OpenAPI Specs

Use yq (YAML) or jq (JSON) to inspect specs without loading full content:

bash

# List all paths
yq '.paths | keys' spec.yaml

# Inspect a specific endpoint
yq '.paths["/users/{id}"]' spec.yaml

# List all schema names
yq '.components.schemas | keys' spec.yaml

# List all operationIds
yq '[.paths[][].operationId // empty] | unique' spec.yaml

Strategy Document

For complex issues, produce a document:

markdown

## 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]

manage-openapi-overlays - Fix issues with overlays
setup-sdk-testing - Contract testing for validation
writing-openapi-specs - Spec design best practices

Files

Just SKILL.md in .agents/skills/diagnose-generation-failure of trycompai/comp.

Open the folder on GitHubat commit 0117612

Compare with similar skills

Diagnose Generation Failure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Diagnose Generation Failure compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Diagnose Generation Failure this skilltrycompai/comp	2k	—	~938	Automated safety check: Pass	Apache-2.0	2 days ago
ToolJet Marketplace Plugin BuilderToolJet/ToolJet	41k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	today
CLI Creatorhuangruiteng/CS-Notes	4k	2 repos	~2.7k	Automated safety check: Pass	Apache-2.0	yesterday
Debug Oaselastic/kibana	21k	—	~1.4k	Automated safety check: Pass	Custom licence	today
Api2clialexknowshtml/api2cli	455	—	~2.9k	Automated safety check: Pass	MIT	7 mo ago
Sync APImollie/mollie-api-node	297	—	~3.6k	Automated safety check: Pass	BSD-3-Clause	1 mo ago

Similar skills

ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
41k GitHub stars~2.1k tokensUpdated today
Backend & APIsAuto-check passed
CLI Creator
huangruiteng/CS-Notes
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.
4k GitHub starsUsed in 2 repos~2.7k tokens
Backend & APIsAuto-check passed
Debug Oas
elastic/kibana
Official
A skill your agent uses when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS…
21k GitHub stars~1.4k tokensUpdated today
Backend & APIsAuto-check passed
Api2cli
alexknowshtml/api2cli
Generate a working CLI from any API, then wrap it in a Claude Code skill.
455 GitHub stars~2.9k tokensUpdated 7 mo ago
Backend & APIsAuto-check passed
Sync API
mollie/mollie-api-node
Reconcile the SDK against the Mollie API spec — checks and optionally fixes types, JSDoc, enums, deprecations, endpoint coverage, and helper wiring.
297 GitHub stars~3.6k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Vibex
Raja0sama/vibex
Diagrams and checkable docs from a codebase. An agent skill from Raja0sama/vibex.
388 GitHub stars~7.8k tokensUpdated 3 days ago
Backend & APIsAuto-check passed

Questions about Diagnose Generation Failure

What does Diagnose Generation Failure do?

A skill your agent uses when SDK generation failed or seeing errors. Diagnose Generation Failure is an agent skill from trycompai/comp. Use when SDK generation failed or seeing errors.

When should I use Diagnose Generation Failure?

Diagnose Generation Failure fits situations like: SDK generation failed; generation failed; speakeasy run failed; SDK build error.

How do I install Diagnose Generation Failure in Claude Code?

Run `npx skills add trycompai/comp --skill diagnose-generation-failure -a claude-code`. Or copy the skill folder (.agents/skills/diagnose-generation-failure in trycompai/comp) into .claude/skills/diagnose-generation-failure in your project. Claude Code loads it when a task matches its description.

How do I install Diagnose Generation Failure in Codex?

Run `npx skills add trycompai/comp --skill diagnose-generation-failure -a codex`. Or copy the skill folder (.agents/skills/diagnose-generation-failure in trycompai/comp) into .agents/skills/diagnose-generation-failure in your project. Codex loads it when a task matches its description.

Can I use Diagnose Generation Failure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trycompai/comp --skill diagnose-generation-failure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose-generation-failure, .gemini/skills/diagnose-generation-failure, .github/skills/diagnose-generation-failure and .opencode/skills/diagnose-generation-failure in your project.

What does Diagnose Generation Failure need to run?

Going by SKILL.md and its folder, Diagnose Generation Failure needs the command-line tools its instructions call (yq).

Does Diagnose Generation Failure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Diagnose Generation Failure safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Diagnose Generation Failure use?

Diagnose Generation Failure is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Diagnose Generation Failure use?

About 938 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Diagnose Generation Failure?

Skills that share tags, products or a category with Diagnose Generation Failure: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), CLI Creator (huangruiteng/CS-Notes, 4k stars), Debug Oas (elastic/kibana, 21k stars) and Api2cli (alexknowshtml/api2cli, 455 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Diagnose Generation Failure?

trycompai (a GitHub organization) maintains it in trycompai/comp, which has 2,023 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.

Source: trycompai/comp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Diagnose Generation Failure

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

diagnose-generation-failure

When to Use

Inputs

Outputs

Diagnosis Steps

Decision Framework

What NOT to Do

Troubleshooting Tree

Working with Large OpenAPI Specs

Strategy Document

Related Skills

Files

Compare with similar skills

Similar skills

More from trycompai/comp

Related

Questions about Diagnose Generation Failure