Agent skill

Manage Openapi Overlays

A skill your agent uses when creating, applying, or validating overlay files including x-speakeasy extensions.

Apache-2.0Auto-check passedBackend & APIs

Install Manage Openapi Overlays

skills CLI

$ npx skills add trycompai/comp --skill manage-openapi-overlays -a claude-code

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

GitHub CLI

$ gh skill install trycompai/comp manage-openapi-overlays --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/manage-openapi-overlays .claude/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .claude/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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/manage-openapi-overlays

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 manage-openapi-overlays -a codex

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

GitHub CLI

$ gh skill install trycompai/comp manage-openapi-overlays --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/manage-openapi-overlays .agents/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .agents/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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 manage-openapi-overlays -a cursor

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

GitHub CLI

$ gh skill install trycompai/comp manage-openapi-overlays --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/manage-openapi-overlays .cursor/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .cursor/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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/manage-openapi-overlays

--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 manage-openapi-overlays -a gemini-cli

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

GitHub CLI

$ gh skill install trycompai/comp manage-openapi-overlays --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/manage-openapi-overlays .gemini/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .gemini/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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 manage-openapi-overlays

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 manage-openapi-overlays -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/manage-openapi-overlays .github/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .github/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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 manage-openapi-overlays -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 manage-openapi-overlays --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/manage-openapi-overlays .opencode/skills/manage-openapi-overlays && 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 "manage-openapi-overlays" agent skill from https://github.com/trycompai/comp/tree/main/.agents/skills/manage-openapi-overlays into .opencode/skills/manage-openapi-overlays/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-openapi-overlays", 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: manage-openapi-overlays
GitHub stars: 2k
Token cost: ~2.8k tokens
SKILL.md length: 805 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 creating, applying, or validating overlay files including x-speakeasy extensions.

Validating overlay files including x-speakeasy extensions
SKILL.md covers Content Guides, Authentication, When to Use and Inputs, plus 12 more sections
Needs SPEAKEASY_API_KEY and MYAPI_KEY_ID
Configure retries

What it does

Manage Openapi Overlays is an agent skill from trycompai/comp. Use when creating, applying, or validating overlay files including x-speakeasy extensions. Covers overlay syntax, JSONPath targeting, retries, pagination, naming, grouping, open enums, global headers, custom security. Triggers on "create overlay", "apply overlay", "overlay file", "x-speakeasy", "add extension", "configure retries", "add pagination", "overlay for retries".

Its SKILL.md is about 2.8k 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. It works with OpenAPI. 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

Validating overlay files including x-speakeasy extensions
Configure retries
Overlay for retries

Example prompts

“create overlay”
“apply overlay”
“overlay file”
“/manage-openapi-overlays”

Requirements

A credential in SPEAKEASY_API_KEY
A credential in MYAPI_KEY_SECRET

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
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and bash).
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 these keys or tokens, usually read from environment variables:
- SPEAKEASY_API_KEY
- MYAPI_KEY_ID
- MYAPI_KEY_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Manage Openapi Overlays loads about 2.8k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 805 words of instructions outside code blocks.

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

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). 805 words, ~2,785 tokens.

Download SKILL.mdSave it as .claude/skills/manage-openapi-overlays/SKILL.md (or your agent's skills folder).

name: manage-openapi-overlays
description: Use when creating, applying, or validating overlay files including x-speakeasy extensions. Covers overlay syntax, JSONPath targeting, retries, pagination, naming, grouping, open enums, global headers, custom security. Triggers on "create overlay", "apply overlay", "overlay file", "x-speakeasy", "add extension", "configure retries", "add pagination", "overlay for retries".
license: Apache-2.0

manage-openapi-overlays

Overlays let you customize an OpenAPI spec for SDK generation without modifying the source. This skill covers creating overlay files, applying them to specs, and using them to fix validation errors.

Content Guides

Topic	Guide
OpenAPI Validation	content/validation.md
Security Schemes	content/security-schemes.md

These guides cover validating specs, fixing common issues, and configuring authentication methods.

Authentication

Set SPEAKEASY_API_KEY env var or run speakeasy auth login.

When to Use

Use this skill when you need to manually work with overlay files:

Creating an overlay file from scratch with specific JSONPath targets
Applying an existing overlay file to a spec
Validating overlay syntax and structure
Comparing two specs to generate an overlay
Understanding overlay mechanics (actions, targets, update/remove)
Fixing lint issues via manual overlay creation
User says: "create overlay", "apply overlay", "overlay file", "manual overlay", "overlay syntax", "JSONPath targeting", "validate overlay"

NOT for: AI-powered naming suggestions (see improve-sdk-naming instead)

Inputs

Input	Required	Description
Target spec	Yes	OpenAPI spec to customize or fix
Customizations	Depends	Changes to apply (groups, names, retries, descriptions)
Overlay file	Depends	Existing overlay to apply (for apply workflow)
Lint output	Helpful	Validation errors to fix (for fix workflow)

Outputs

Output	Description
Overlay file	YAML file with JSONPath-targeted changes
Modified spec	Transformed OpenAPI spec (when applying)

Commands

Generate an Overlay by Comparing Specs

bash

speakeasy overlay compare -b <before-spec> -a <after-spec> -o <output-overlay>

Use this when you have a modified version of a spec and want to capture the differences as a reusable overlay.

Apply an Overlay to a Spec

bash

speakeasy overlay apply -s <spec-path> -o <overlay-path> --out <output-path>

Validate an Overlay

bash

speakeasy overlay validate -o <overlay-path>

Creating an Overlay Manually

Create an overlay file with this structure:

yaml

overlay: 1.0.0
info:
  title: My Overlay
  version: 1.0.0
actions:
  - target: "$.paths['/example'].get"
    update:
      x-speakeasy-group: example
      x-speakeasy-name-override: getExample

Each action has a target (JSONPath expression) and an update (object to merge) or remove (boolean to delete the target).

Example: SDK Method Naming and Grouping

yaml

overlay: 1.0.0
info:
  title: SDK Customizations
  version: 1.0.0
actions:
  - target: "$.paths['/users'].get"
    update:
      x-speakeasy-group: users
      x-speakeasy-name-override: list
  - target: "$.paths['/users'].post"
    update:
      x-speakeasy-group: users
      x-speakeasy-name-override: create
  - target: "$.paths['/users/{id}'].get"
    update:
      x-speakeasy-group: users
      x-speakeasy-name-override: get
  - target: "$.paths['/users/{id}'].delete"
    update:
      x-speakeasy-group: users
      x-speakeasy-name-override: delete
      deprecated: true

This produces SDK methods: sdk.users.list(), sdk.users.create(), sdk.users.get(), sdk.users.delete().

Example: Apply Overlay

bash

# Apply overlay and write merged spec
speakeasy overlay apply -s openapi.yaml -o sdk-overlay.yaml --out openapi-modified.yaml

# Compare two specs to generate an overlay
speakeasy overlay compare -b original.yaml -a modified.yaml -o changes-overlay.yaml

Using in Workflow (Recommended)

Instead of applying overlays manually, add them to .speakeasy/workflow.yaml:

yaml

sources:
  my-api:
    inputs:
      - location: ./openapi.yaml
    overlays:
      - location: ./naming-overlay.yaml
      - location: ./grouping-overlay.yaml

Overlays are applied in order. Later overlays can override earlier ones. This approach ensures overlays are always applied during speakeasy run.

Common Fix Patterns

Use overlays to fix validation issues when you cannot edit the source spec.

Issue	Overlay Fix
Poor operation names	Add `x-speakeasy-name-override` to the operation
Missing descriptions	Add `summary` or `description` to the operation
Missing tags	Add `tags` array to the operation
Need operation grouping	Add `x-speakeasy-group` to operations
Need retry config	Add `x-speakeasy-retries` to operations or globally
Deprecate an endpoint	Add `deprecated: true` to the operation
Add SDK-specific metadata	Add any `x-speakeasy-*` extension

Fix Workflow

bash

# 1. Validate the spec to identify issues
speakeasy lint openapi --non-interactive -s openapi.yaml

# 2. Create an overlay file targeting each issue (see patterns above)

# 3. Add overlay to workflow.yaml under sources.overlays

# 4. Regenerate the SDK
speakeasy run --output console

Speakeasy Extensions Reference

Extensions (x-speakeasy-*) customize SDK generation. Apply them via overlays.

Extension	Applies To	Purpose
`x-speakeasy-retries`	Operation or root	Configure retry behavior
`x-speakeasy-pagination`	Operation	Enable automatic pagination
`x-speakeasy-name-override`	Operation	Override SDK method name
`x-speakeasy-group`	Operation	Group methods under namespace
`x-speakeasy-unknown-values`	Schema with enum	Allow unknown enum values
`x-speakeasy-globals`	Root	Define SDK-wide parameters
`x-speakeasy-custom-security-scheme`	Security scheme	Multi-part custom auth

Retries

yaml

actions:
  - target: "$.paths['/resources'].get"  # Or "$" for global
    update:
      x-speakeasy-retries:
        strategy: backoff
        backoff:
          initialInterval: 500      # ms
          maxInterval: 60000        # ms
          maxElapsedTime: 3600000   # ms
          exponent: 1.5
        statusCodes: ["5XX", "429"]
        retryConnectionErrors: true

Pagination

Offset/Limit:

yaml

actions:
  - target: "$.paths['/users'].get"
    update:
      x-speakeasy-pagination:
        type: offsetLimit
        inputs:
          - name: offset
            in: parameters
            type: offset
          - name: limit
            in: parameters
            type: limit
        outputs:
          results: $.data
          numPages: $.meta.total_pages

Cursor:

yaml

actions:
  - target: "$.paths['/events'].get"
    update:
      x-speakeasy-pagination:
        type: cursor
        inputs:
          - name: cursor
            in: parameters
            type: cursor
        outputs:
          results: $.events
          nextCursor: $.next_cursor

Open Enums (Anti-Fragility)

Prevent SDK breakage when APIs return new enum values:

yaml

actions:
  - target: "$.components.schemas.Status"
    update:
      x-speakeasy-unknown-values: allow

For all enums (add x-speakeasy-jsonpath: rfc9535 at overlay root):

yaml

actions:
  - target: $..[?length(@.enum) > 1]
    update:
      x-speakeasy-unknown-values: allow

Show full SKILL.md (319 more words)Show less

Global Headers

Add SDK-wide headers as constructor options:

yaml

actions:
  - target: $
    update:
      x-speakeasy-globals:
        parameters:
          - $ref: "#/components/parameters/TenantId"
  - target: $.components
    update:
      parameters:
        TenantId:
          name: X-Tenant-Id
          in: header
          schema:
            type: string

Result: client = SDK(api_key="...", tenant_id="tenant-123")

Custom Security Schemes

For complex auth (HMAC, multi-part credentials):

yaml

actions:
  - target: $.components
    update:
      securitySchemes:
        hmacAuth:
          type: http
          scheme: custom
          x-speakeasy-custom-security-scheme:
            schema:
              type: object
              properties:
                keyId:
                  type: string
                keySecret:
                  type: string
  - target: $
    update:
      security:
        - hmacAuth: []

With envVarPrefix: MYAPI in gen.yaml, generates env var support for MYAPI_KEY_ID, MYAPI_KEY_SECRET.

JSONPath Targeting Reference

Target	Selects
`$.paths['/users'].get`	GET /users operation
`$.paths['/users/{id}'].*`	All operations on /users/{id}
`$.paths['/users'].get.parameters[0]`	First parameter of GET /users
`$.components.schemas.User`	User schema definition
`$.components.schemas.User.properties.name`	Name property of User schema
`$.info`	API info object
`$.info.title`	API title
`$.servers[0]`	First server entry

What NOT to Do

Do NOT use overlays for invalid YAML/JSON syntax errors -- fix the source file
Do NOT try to fix broken $ref paths with overlays -- fix the source spec
Do NOT use overlays to fix wrong data types -- this is an API design issue
Do NOT try to deduplicate schemas with overlays -- requires structural analysis
Do NOT ignore errors that require source spec fixes -- overlays cannot solve everything
Do NOT modify source OpenAPI specs directly if they are externally managed
Do NOT use a speakeasy overlay create command -- it does not exist

Troubleshooting

Error	Cause	Solution
"target not found"	JSONPath does not match spec structure	Verify exact path and casing by inspecting the spec
Changes not applied	Overlay not in workflow	Add overlay to `sources.overlays` in `workflow.yaml`
"invalid overlay"	Malformed YAML	Check overlay structure: needs `overlay`, `info`, `actions`
YAML parse error	Invalid overlay syntax	Check YAML indentation and quoting
No changes visible	Wrong target path	Use `$.paths['/exact-path']` with exact casing
Errors persist after overlay	Issue not overlay-appropriate	Check if the issue requires a source spec fix instead
Overlay order conflict	Later overlay overrides earlier	Reorder overlays in `workflow.yaml` or merge into one file

After Making Changes

After creating or modifying overlay files and adding them to workflow.yaml, prompt the user to regenerate the SDK:

Overlay configuration complete. Would you like to regenerate the SDK now with speakeasy run?

If the user confirms, run:

bash

speakeasy run --output console

Overlay changes only take effect in the SDK after regeneration.

Files

Just SKILL.md in .agents/skills/manage-openapi-overlays of trycompai/comp.

Open the folder on GitHubat commit 0117612

Compare with similar skills

Manage Openapi Overlays 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.

Manage Openapi Overlays compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Manage Openapi Overlays this skilltrycompai/comp	2k	—	~2.8k	Automated safety check: Pass	Apache-2.0	today
ToolJet Marketplace Plugin BuilderToolJet/ToolJet	41k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	today
Step Partsearthtojake/text-to-cad	18k	1 repos	~1.5k	Automated safety check: Pass	MIT	today
API DesignerJeffallan/claude-skills	12k	2 repos	~2k	Automated safety check: Pass	MIT	4 days ago
OpenAPI to MCP Servermcp-use/mcp-use	11k	—	~5.2k	Automated safety check: Pass	Apache-2.0	today
Use Yaakmountain-loop/yaak	19k	—	~1.9k	Automated safety check: Pass	MIT	yesterday

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
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
18k GitHub starsUsed in 1 repo~1.5k tokens
Backend & APIsAuto-check passed
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
12k GitHub starsUsed in 2 repos~2k tokens
Backend & APIsAuto-check passed
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
11k GitHub stars~5.2k tokensUpdated today
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated yesterday
Backend & APIsAuto-check passed
Old Coder API Design
AmazingAng/old-coder
Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.
749 GitHub starsUsed in 1 repo~3.4k tokens
Backend & APIsAuto-check passed

Questions about Manage Openapi Overlays

What does Manage Openapi Overlays do?

A skill your agent uses when creating, applying, or validating overlay files including x-speakeasy extensions. Manage Openapi Overlays is an agent skill from trycompai/comp. Use when creating, applying, or validating overlay files including x-speakeasy extensions.

When should I use Manage Openapi Overlays?

Manage Openapi Overlays fits situations like: validating overlay files including x-speakeasy extensions; configure retries; overlay for retries.

How do I install Manage Openapi Overlays in Claude Code?

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

How do I install Manage Openapi Overlays in Codex?

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

Can I use Manage Openapi Overlays 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 manage-openapi-overlays -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-openapi-overlays, .gemini/skills/manage-openapi-overlays, .github/skills/manage-openapi-overlays and .opencode/skills/manage-openapi-overlays in your project.

What does Manage Openapi Overlays need to run?

Going by SKILL.md and its folder, Manage Openapi Overlays needs credentials named SPEAKEASY_API_KEY, MYAPI_KEY_ID and MYAPI_KEY_SECRET. Our summary lists: A credential in SPEAKEASY_API_KEY; A credential in MYAPI_KEY_SECRET.

Does Manage Openapi Overlays 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 Manage Openapi Overlays 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 Manage Openapi Overlays use?

Manage Openapi Overlays 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 Manage Openapi Overlays use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Manage Openapi Overlays?

Skills that share tags, products or a category with Manage Openapi Overlays: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 18k stars), API Designer (Jeffallan/claude-skills, 12k stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Manage Openapi Overlays?

trycompai (a GitHub organization) maintains it in trycompai/comp, which has 2,018 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 Manage Openapi Overlays

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

manage-openapi-overlays

Content Guides

Authentication

When to Use

Inputs

Outputs

Commands

Generate an Overlay by Comparing Specs

Apply an Overlay to a Spec

Validate an Overlay

Creating an Overlay Manually

Example: SDK Method Naming and Grouping

Example: Apply Overlay

Using in Workflow (Recommended)

Common Fix Patterns

Fix Workflow

Speakeasy Extensions Reference

Retries

Pagination

Open Enums (Anti-Fragility)

Global Headers

Custom Security Schemes

JSONPath Targeting Reference

What NOT to Do

Troubleshooting

After Making Changes

Files

Compare with similar skills

Similar skills

More from trycompai/comp

Related

Questions about Manage Openapi Overlays