Speakeasy
Official@speakeasy-api · United States of America
The enterprise control plane for AI. Secure and centrally manage MCPs, Skills, and Assistants your whole company can use!
Agent Skills by Speakeasy
Showing 27 vetted skills indexed across 3 GitHub repositories.
speakeasy-apivercel-react-best-practices
Apply Vercel best practices to improve React and Next.js performance.
speakeasy-apidatadog
Query Datadog logs, metrics, and traces to identify root causes across Gram services.
speakeasy-apigolang
Codify Go best practices for error handling, modules, and concurrency.
speakeasy-apifrontend
Standardize React dashboard component architecture and styling patterns.
speakeasy-apigram-functions
Deploys user-provided JS/TS and Python code as callable tools in Gram via manifests and JWT auth.
speakeasy-apipostgresql
Enforce PostgreSQL schema, migration, and data integrity guidelines for multi-tenant setups.
speakeasy-apiclickhouse
Configures ClickHouse query building with squirrel for telemetry analytics.
speakeasy-apimise-tasks
Standardize Bash and TypeScript task scripts under .mise-tasks directories.
speakeasy-apiextract-openapi-from-code
Extract OpenAPI specifications from FastAPI, Flask, Django, and other codebases.
speakeasy-apiconfigure-sdk-options
Configure Speakeasy SDK gen.yaml options and runtime overrides across supported languages.
speakeasy-apispeakeasy-context
Provides guidance for generating SDKs and using the Speakeasy CLI.
speakeasy-apiorchestrate-multi-target-sdks
Generate multiple SDK variants from a single repository using workflow.yaml and gen.yaml.
speakeasy-apiwriting-openapi-specs
Apply standardized best practices to draft and validate OpenAPI specifications.
speakeasy-apigenerate-terraform-provider
Generate a Terraform provider from an OpenAPI spec using the Speakeasy CLI.
speakeasy-apiimprove-sdk-naming
Generate SDK operation ID suggestions from OpenAPI specs via speakeasy suggest.
speakeasy-apiorchestrate-multi-repo-sdks
Dispatch SDK generation and reconcile PRs across multiple language repositories.
speakeasy-apimanage-openapi-overlays
Create, apply, and validate OpenAPI overlays using the speakeasy CLI.
speakeasy-apicustomize-sdk-hooks
Implement BeforeRequest, AfterSuccess, and AfterError hooks in generated SDKs.
speakeasy-apisetup-sdk-testing
Automate Speakeasy SDK test setup and execution via gen.yaml and OpenAPI specs.
speakeasy-apigenerate-mcp-server
Generate an MCP server from an OpenAPI specification using Speakeasy CLI.
speakeasy-apidiagnose-generation-failure
Diagnose OpenAPI-to-SDK generation failures and determine fix strategies.
speakeasy-apistart-new-sdk-project
Bootstrap an SDK project from an OpenAPI specification with a workflow file.
speakeasy-apigranary-plan-work
Create Granary projects and tasks from high-level features with dependencies.
speakeasy-apigranary-initiative-planner
Define initiatives, create projects, and spawn sub-agents for cross-project planning.
Frequently Asked Questions About Speakeasy
FAQPage SchemaWhat specific engineering tasks are enabled by these capabilities?▼
These capabilities enable the generation of type-safe client libraries, Terraform providers, and MCP servers directly from OpenAPI specifications. Engineers can also standardize task execution, enforce database schema migrations, and query telemetry data from ClickHouse and Datadog to maintain high-performance, consistent service architectures across large-scale repositories.
Which technical personas benefit most from these features?▼
Platform engineers, backend developers, and infrastructure architects benefit most. These features are designed for teams managing complex service meshes, multi-language codebases, and distributed systems who require centralized governance over interface definitions, SDK distribution, and cross-project task coordination to ensure consistency and reduce manual configuration overhead.
What are the primary prerequisites for implementing these solutions?▼
Implementation requires existing OpenAPI specifications to serve as the source of truth for generation. Users must also maintain standardized repository structures, such as .mise-tasks for task management and gen.yaml configurations for defining SDK generation parameters, to ensure the control plane can effectively reconcile and dispatch changes across multiple repositories.