Skip to content
TrustedSkillsbeta
Back to all skills

Manage Openapi Overlays

Checked
speakeasy-api·vlatest·backend·Apache-2.0

Automates OpenAPI overlay management, simplifying API versioning and customization within Speakeasy projects.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add speakeasy-api/sdk-generation-skills --skill manage-openapi-overlays -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

speakeasy-api

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned speakeasy-api/skills at d2eab5991e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 868 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to manage OpenAPI overlays. It enables modification of existing OpenAPI specifications, facilitating customization and extension without altering the original document. The skill can apply changes such as adding new paths, modifying request bodies, or updating security schemes.

When to use it

  • You need to add custom endpoints to an existing API specification.
  • You want to modify request body schemas for specific use cases.
  • You're integrating with a third-party API and need to adjust the OpenAPI definition accordingly.
  • You require changes to security schemes defined in the original OpenAPI document.

Key capabilities

  • Modify existing OpenAPI specifications.
  • Add new paths to an OpenAPI specification.
  • Update request body schemas within an OpenAPI specification.
  • Adjust security schemes described in an OpenAPI specification.

Example prompts

  • "Add a /users/{id} endpoint to the API definition, with a GET method."
  • "Modify the create_user request body schema to include an optional 'email' field."
  • "Update the security scheme to use API keys instead of OAuth 2.0."

Tips & gotchas

The skill requires a valid OpenAPI specification as input. Ensure the provided specification is well-formed and adheres to the OpenAPI standard for optimal results.