Skip to content
TrustedSkillsbeta
Back to all skills

Extract Openapi From Code

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

Automatically generates OpenAPI specifications from existing codebase, streamlining API documentation and development workflows.

Repository

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 extract-openapi-from-code -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.

Commit
d2eab5991e
Manifest
skills/extract-openapi-from-code/SKILL.md
Scanned
9 files, 3,484 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 automatically generates OpenAPI specifications directly from existing codebases. It analyzes your implementation to map out endpoints, request/response schemas, and authentication flows without manual documentation.

When to use it

  • You need to document a legacy API where original specs are missing or outdated.
  • You want to ensure your AI agents understand the exact structure of your backend services.
  • You are refactoring code and need to verify that new implementations match expected API contracts.
  • You require machine-readable documentation for rapid client SDK generation.

Key capabilities

  • Parses source code to identify HTTP methods, paths, and parameters.
  • Infers data models and validation rules from typed variables and function signatures.
  • Outputs standard OpenAPI 3.x format compatible with major tools like Swagger UI.
  • Handles complex scenarios including authentication headers and file uploads.

Example prompts

"Extract an OpenAPI spec from my Python FastAPI application located in the src directory." "Generate an OpenAPI document from this Node.js Express server code to help my AI agent interact with it." "Analyze my Go HTTP handlers and create a corresponding OpenAPI specification file."

Tips & gotchas

Ensure your codebase includes type hints or explicit struct definitions, as the extraction relies on these for accurate schema generation. Review the output carefully, as inferred logic may occasionally miss edge cases present only in runtime behavior.