orchestrate-multi-target-sdks

Generate multi-language SDKs from an OpenAPI specification using the Speakeasy CLI.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/berea-ch/bereach-sdk-ts --skill orchestrate-multi-target-sdks-berea-ch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate-multi-target-sdks
Source: https://github.com/berea-ch/bereach-sdk-ts/tree/main/.agents/skills/orchestrate-multi-target-sdks
Command: npx skills add https://github.com/berea-ch/bereach-sdk-ts --skill orchestrate-multi-target-sdks-berea-ch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of generating SDKs for multiple programming languages or variants from a single API specification, managing monorepo structures and per-language configurations.

Core Features & Use Cases

  • Multi-Language SDK Generation: Create SDKs for various languages (TypeScript, Python, Go, etc.) from one OpenAPI spec.
  • SDK Variant Creation: Generate different SDK versions (e.g., Azure, GCP) from distinct API specs.
  • Monorepo Management: Organizes multiple SDK projects within a single repository.
  • Use Case: A company has a core API and needs to provide SDKs for its partners using TypeScript, Python, and Go. This Skill automates the entire generation and configuration process for all three.

Quick Start

Use the speakeasy CLI to configure and generate SDKs for multiple languages from your OpenAPI specification.

Frequently Asked Questions about orchestrate-multi-target-sdks

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

FAQPage Schema
How do I generate SDKs for multiple languages from a single OpenAPI spec?

You can generate multi-language SDKs from a single OpenAPI spec by orchestrating the Speakeasy CLI to manage per-language configurations. This Skill automates the entire generation process, supporting TypeScript, Python, and Go outputs within a monorepo structure.

Can I manage multiple SDK variants in a monorepo using Speakeasy?

Yes, you can manage multiple SDK variants in a monorepo using Speakeasy. The Skill orchestrates complex monorepo structures and handles per-language generation configurations, allowing you to organize distinct SDK versions like Azure or GCP variants in one repository.

What is the best way to add a new target language to an existing SDK generation workflow?

The best way to add a new target language to an existing SDK generation workflow is to use this Skill's support for adding new targets. It orchestrates per-language configurations via the Speakeasy CLI, updating the monorepo structure to include the new SDK.

Does this SDK generation approach work with different OpenAPI specifications for each variant?

Yes, this SDK generation approach works with different OpenAPI specifications for each variant. The Skill supports SDK variant creation, allowing you to generate distinct versions like Azure or GCP from separate API specs within the same monorepo.

Do I need the Speakeasy CLI to set up multi-language SDK generation?

Yes, you need the Speakeasy CLI to set up multi-language SDK generation. The Skill uses the Speakeasy CLI to configure and generate SDKs from your OpenAPI specification, managing the initial setup and the generation process across all configured targets.

Why use a monorepo structure for multi-language SDK generation?

Using a monorepo structure for multi-language SDK generation organizes multiple SDK projects within a single repository. This approach streamlines management of per-language configurations and automates the generation process across all configured SDKs from your unified OpenAPI specification.