orchestrate-multi-target-sdks

Generate multiple SDK variants from a single repository using workflow.yaml and gen.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage and generate multiple SDK variants from a single repository, reducing duplication and ensuring consistent outputs across targets.

Core Features & Use Cases

  • Multi-target generation: generate core, Azure, GCP SDK variants from a shared OpenAPI sources.
  • Per-target configuration: apply per-target gen.yaml and workflow.yaml settings to control outputs and versions.
  • Use Case: Imagine you maintain a single OpenAPI spec and need separate TS SDKs for main, azure, and gcp packages; this skill coordinates generation and packaging for all variants.

Quick Start

Use the orchestrate-multi-target-sdks skill to configure and generate all target SDKs from your repository using workflow.yaml and per-target gen.yaml settings.

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 multiple SDK variants from a single OpenAPI repository?

To generate multiple SDK variants from a single OpenAPI repository, you orchestrate outputs using a structured workflow.yaml and per-target gen.yaml files. This coordinates monorepo configurations to produce distinct cloud-specific packages.

Can I output separate SDKs for different cloud providers from one OpenAPI spec?

Yes, you can output separate SDKs for different cloud providers from one OpenAPI spec by applying per-target configurations. This process generates distinct core, Azure, and GCP SDK variants from shared monorepo sources.

How do I manage consistent versioning across multiple SDK targets in a monorepo?

You manage consistent versioning across multiple SDK targets by enforcing structured workflow.yaml configurations. This coordinates versioning strategies across all generated SDK variants to ensure synchronized releases.

What is the best way to configure per-target SDK generation settings?

The best way to configure per-target SDK generation settings is by using individual gen.yaml files. These files define specific outputs and versions for each target, coordinating seamlessly with the overarching workflow.yaml structure.

When do I need a monorepo setup for multi-target SDK generation?

You need a monorepo setup for multi-target SDK generation when maintaining multiple OpenAPI sources that require distinct SDK variants. This approach reduces duplication and ensures consistent outputs across different cloud-specific targets.