Use when you have an OpenAPI spec and want to generate an SDK, or asking "how do I get started with Speakeasy"
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill start-new-sdk-project --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Start New Sdk Project?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-start-new-sdk-project)More formats (shields.io, HTML) on the badges page.
---
name: start-new-sdk-project
description: Use when you have an OpenAPI spec and want to generate an SDK, or asking "how do I get started with Speakeasy"
---
# start-new-sdk-project
Use `speakeasy quickstart` to initialize a new project with a workflow configuration.
## Prerequisites
For non-interactive environments (CI/CD, AI agents), set:
```bash
export SPEAKEASY_API_KEY="<your-api-key>"
```
See `configure-authentication` skill for details.
## Command
```bash
speakeasy quickstart -s <path-to-openapi-spec> -t <target-language>
```
## Supported Targets
| Language | Target Flag |
|----------|-------------|
| TypeScript | `typescript` |
| Python | `python` |
| Go | `go` |
| Java | `java` |
| C# | `csharp` |
| PHP | `php` |
| Ruby | `ruby` |
| Kotlin | `kotlin` |
| Terraform | `terraform` |
## Example
```bash
# Initialize TypeScript SDK project
speakeasy quickstart -s ./api/openapi.yaml -t typescript
# With custom output directory
speakeasy quickstart -s ./api/openapi.yaml -t python -o ./sdks/python
```
## What It Creates
```
.speakeasy/
└── workflow.yaml # Workflow configuration
```
## Next Steps After Quickstart
1. Run `speakeasy run` to generate the SDK
2. Review the generated SDK in the output directory
3. Add more targets to workflow.yaml for multi-language support
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.