If you have ever added an SDK to a project, you know the rhythm: open the docs, copy the install command, find the right place for the client, hunt down environment variables, write the first route, run it, fix a typo. None of those steps are hard. They are just tax—time you pay before you can do the actual work.
Today we are open-sourcing the TurboDocx Quickstart Skill—an Agent Skill that pays the tax for you. Hand it to your AI coding agent and it installs the SDK, configures the environment, and writes a working integration that matches your existing code style.
It works with Claude Code, GitHub Copilot in VS Code, Cursor, OpenCode, OpenAI Codex CLI, and Gemini CLI. One install command, six tools.
What is an Agent Skill?
Agent Skills are a portable format for AI agent capabilities. A skill is just a folder of instructions and reference material that an agent can load on demand. When your agent sees a skill matches the user's request, it follows the skill's instructions step by step.
The TurboDocx skill lives at github.com/TurboDocx/quickstart. The format is the open standard from agentskills.io, so the same skill works across every supported agent without modification.
Why we chose Agent Skills over a CLI generator: a generator gives you scaffolding at one moment in time. A skill follows the agent into the conversation and can reason about your codebase—where your routes live, how you load config, whether you use TypeScript or plain JS—and produce code that matches.
The two skills
turbodocx-sdkWhat it does: TurboSign (e-signature) + TurboPartner (partner/org management)
Languages: JavaScript / TypeScript, Python, Go, PHP, Java
Frameworks: Express, Next.js, Fastify, NestJS, FastAPI, Flask, Django, Spring Boot, Laravel, Gin, Echo, and others
turbodocx-html-to-docxWhat it does: Convert HTML strings to Microsoft Word documents
Languages: JavaScript / TypeScript (Node.js and browser)
Frameworks: Express, Next.js (API routes), Fastify, NestJS, static HTML, Vite, Webpack
Install
The npx skills CLI from vercel-labs/skills auto-detects which agents you have installed and drops the skills into the right place. From the root of any project:
$ npx skills add TurboDocx/quickstart$ npx skills add TurboDocx/quickstart --skill turbodocx-sdk$ npx skills add TurboDocx/quickstart --skill turbodocx-html-to-docx$ npx skills add TurboDocx/quickstart -gClaude Code users can also install via the plugin command: claude plugin add turbodocx/quickstart.
Supported agents
Plus any other tool that supports the Agent Skills standard. The CLI knows where each agent stores its skills and routes the install accordingly.
What it generates
After install, invoke the skill in your editor or terminal:
/turbodocx-sdkTurboSign integration
- SDK client configured with environment variable loading
sendSignature()helper that sends documents for legally-binding e-signaturegetStatus()helper that checks document and recipient state- A route handler wired into your existing application
TurboPartner integration
- Partner client configured with environment variables
createOrganization()helper that provisions customer orgslistOrganizations()helper that lists managed organizations- A route handler wired into your existing application
@turbodocx/html-to-docx integration
- Helper module that matches your framework (Express, Next.js API route, Fastify, NestJS, etc.)
- A working endpoint that returns a
.docxresponse - For static HTML projects, the polyfilled
<script>tag setup with the bundled IIFE build - For bundlers (Vite, Webpack, Next.js client), the ESM import path
Why this matters
The integration story for SDKs is shifting. A year ago, "great docs" meant a getting-started page, a few code samples, and a thorough reference. That is still true—but increasingly the first reader of those docs is not a person, it is an agent.
Documentation alone isn't enough. An agent given a doc has to guess at which patterns to apply. A skill is documentation plus process: detect the language, pick the right package, edit the right files, run the right install command. The result is a working integration on the first try instead of three round-trips with the user.
If you ship an SDK, an Agent Skill is the new minimum.
Frequently asked
What is the TurboDocx Quickstart Agent Skill?
An open-source Agent Skills plugin that gives your AI coding agent the knowledge to install the TurboDocx SDK or @turbodocx/html-to-docx into any project. It detects your language and framework, installs the right package, configures environment variables, and generates working integration code that matches your existing patterns.
Which AI coding agents support the TurboDocx skill?
Claude Code, GitHub Copilot in VS Code, Cursor, OpenCode, OpenAI Codex CLI, and Gemini CLI. Any tool that supports the open Agent Skills standard from agentskills.io.
How do I install both skills at once?
Run "npx skills add TurboDocx/quickstart" in any project. The CLI auto-detects which AI agents you have installed and drops both skills into the right config directory. Add the -g flag to install globally so the skills are available everywhere.
What languages does the SDK skill support?
JavaScript/TypeScript, Python, Go, PHP, and Java. The skill detects your project language from package.json, pyproject.toml, go.mod, composer.json, or pom.xml.
Does the html-to-docx skill work in the browser?
Yes. The skill prefers server-side generation when a backend is available because it is faster and skips the browser bundle. It can also wire up the standalone IIFE build for static HTML pages and the ESM build for client-side bundlers like Vite or Webpack.
Try it in your project
Open any project, run the install command, and ask your agent to set up TurboSign, TurboPartner, or html-to-docx.
$ npx skills add TurboDocx/quickstart