start-new-sdk-project

Bootstrap an SDK project from an OpenAPI specification with a workflow file.

19|6|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/speakeasy-api/skills --skill start-new-sdk-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-new-sdk-project
Source: https://github.com/speakeasy-api/skills/tree/main/skills/start-new-sdk-project
Command: npx skills add https://github.com/speakeasy-api/skills --skill start-new-sdk-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill speeds up starting a brand-new SDK project by automating the initial setup from an OpenAPI specification, reducing manual bootstrapping time and ensuring a consistent project structure.

Core Features & Use Cases

  • Bootstraps a complete SDK project from an OpenAPI spec for multiple languages (TypeScript, Python, Go, Java, etc.).
  • Generates the required Speakeasy workflow configuration (.speakeasy/workflow.yaml) and project skeleton in a single step.
  • Ideal for teams starting new SDKs, updating existing specs, or automating CI/CD ready SDK scaffolding.

Quick Start

Use the start-new-sdk-project skill to bootstrap a new SDK project from an OpenAPI spec. Provide the OpenAPI spec path or URL, target language, SDK name, and package name. The quickstart command will output a ready-to-use workflow and SDK in the specified directory.

Frequently Asked Questions about start-new-sdk-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap an SDK from an OpenAPI spec?

To generate an SDK from an OpenAPI spec, provide the spec path, target language, SDK name, and package name. The tool validates these inputs and outputs a ready-to-use workflow file and SDK skeleton in your specified directory.

Can I generate a Python or Go SDK from an OpenAPI specification?

Yes, SDK generation from OpenAPI specifications supports multiple target languages including TypeScript, Python, Go, and Java. You specify the target language during setup to output the corresponding SDK skeleton.

What inputs do I need to generate an SDK project skeleton?

Generating an SDK project skeleton requires four validated inputs: the OpenAPI source path or URL, target language, SDK name, and package name. These are used to generate the workflow configuration and project files.

Does SDK generation create the Speakeasy workflow.yaml configuration?

Yes, the process generates the .speakeasy/workflow.yaml configuration file automatically. It handles first-time setup by outputting both the workflow configuration and the SDK project skeleton in the specified output directory.

What is the best way to automate SDK scaffolding for CI/CD pipelines?

Automating SDK scaffolding for CI/CD is best achieved by using OpenAPI-driven generation to output a ready-to-use workflow and SDK skeleton. This approach reduces manual bootstrapping time and ensures consistent project structure across deployments.