Skip to content
TrustedSkillsbeta
Back to all skills

Openapi To Typescript

Checked
softaworks·vlatest·backend·MIT

Generates TypeScript interfaces and types from OpenAPI specifications, streamlining API client development with Softaworks' tool.

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 softaworks/agent-toolkit --skill openapi-to-typescript -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

softaworks

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 softaworks/agent-toolkit at 3027f20f31.

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

Commit
3027f20f31
Manifest
skills/openapi-to-typescript/SKILL.md
Scanned
2 files, 607 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 converts OpenAPI specifications into TypeScript interfaces, enabling developers to generate strongly-typed client code for REST APIs. It supports various OpenAPI versions and provides customizable output formats.

When to use it

  • You need to create TypeScript types from an existing OpenAPI specification file.
  • You're building a frontend application that interacts with a backend API defined in OpenAPI format.
  • You want to automate the generation of client-side type definitions for easier development and better tooling support.

Key capabilities

  • Converts OpenAPI 2.0, 3.0, and 3.1 specifications into TypeScript interfaces.
  • Supports custom configuration options like naming conventions and output formats.
  • Generates clean, maintainable code that integrates well with modern TypeScript projects.

Example prompts

  • "Convert the OpenAPI file at ./api-spec.yaml to TypeScript interfaces."
  • "Generate client types for my API using the OpenAPI 3.1 spec in the ./docs/api.json file."
  • "Create strongly-typed models from this OpenAPI document and output them as a module."

Tips & gotchas

  • Ensure your OpenAPI specification is valid before running conversion to avoid errors.
  • Customize configuration parameters for better alignment with project-specific naming or formatting conventions.