Skip to content
TrustedSkillsbeta
Back to all skills

Openapi Spec Generation

Checked
wshobson·vlatest·backend·MIT

Generates OpenAPI specifications from existing code or descriptions, streamlining API documentation and development.

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 wshobson/agents --skill openapi-spec-generation -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Scanned
3 files, 1,023 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

The openapi-spec-generation skill enables AI agents to automatically generate OpenAPI specifications from existing API endpoints or code. This allows developers to document APIs efficiently, ensuring consistency and accuracy without manual effort.

When to use it

  • You need to quickly create or update API documentation for a RESTful service.
  • Your team is working on a new microservice and wants to maintain up-to-date OpenAPI specs as part of the development process.
  • You're integrating third-party APIs and want to generate spec files for easier testing and integration.

Key capabilities

  • Automatically generates OpenAPI 3.0+ specifications from API endpoints or code.
  • Supports multiple programming languages and frameworks.
  • Provides structured documentation with paths, operations, parameters, and responses.

Example prompts

  • "Generate an OpenAPI specification for my Flask-based REST API."
  • "Create a spec file for the /users endpoint of this Node.js service."
  • "Document the endpoints in this Python FastAPI project using OpenAPI format."

Tips & gotchas

  • Ensure your API is running and accessible so the agent can inspect its endpoints.
  • Some frameworks may require additional configuration to expose metadata needed for spec generation.