Skip to main content

Install TurboDocx with AI Agents

The TurboDocx Quickstart Skill is an Agent Skills plugin that lets your AI coding agent install and wire up the TurboDocx SDK or @turbodocx/html-to-docx in a single prompt. It detects your project's language and framework, installs the package, configures environment variables, and generates working integration code that matches your existing codebase patterns.

TurboDocx quickstart on skills.sh

Works with:

  • Claude Code
  • GitHub Copilot (VS Code)
  • Cursor
  • OpenCode
  • OpenAI Codex CLI
  • Gemini CLI
  • Any tool that supports the Agent Skills standard

Skills

SkillWhat it does
turbodocx-sdkInstalls the TurboDocx SDK and generates working integration code for TurboSign (e-signatures), Deliverable (template document generation), TurboQuote (quotes & CPQ), TurboWebhooks (signature events), and TurboPartner (partner/org management). Supports JavaScript/TypeScript, Python, Go, PHP, and Java.
turbodocx-html-to-docxSets up @turbodocx/html-to-docx to convert HTML to Microsoft Word documents in Node.js, browser, or hybrid projects.

Install

The fastest path is the npx skills CLI, which auto-detects which agents you have installed and drops the skills into the right config directory.

npx skills add TurboDocx/quickstart

Usage

After installing, invoke the skill in your editor or terminal:

/turbodocx-sdk

The skill will:

  1. Detect your project language from manifest files (package.json, pyproject.toml, go.mod, composer.json, pom.xml).
  2. Ask which product you need. By default it offers TurboSign and Deliverable (and the generate-then-sign combo); TurboPartner, TurboWebhooks, and TurboQuote are opt-in via their shortcuts (below).
  3. Install the SDK with your project's package manager.
  4. Configure environment variables in .env and .env.example.
  5. Analyze your codebase structure (Express, FastAPI, Spring Boot, Laravel, Gin, etc.).
  6. Generate integration code that matches your existing patterns, with route handlers wired into your app.

Shortcuts

Skip the product selection prompt:

/turbodocx-sdk turbosign # TurboSign (e-signatures) only
/turbodocx-sdk deliverable # Deliverable (template document generation) only
/turbodocx-sdk turbosign+deliverable # generate-then-sign workflow
/turbodocx-sdk turboquote # TurboQuote (quotes, catalog, price books) only
/turbodocx-sdk turbowebhooks # TurboWebhooks (signature events) only
/turbodocx-sdk turbopartner # TurboPartner (org provisioning) only
/turbodocx-sdk both # TurboSign + Deliverable

For HTML-to-DOCX:

/turbodocx-html-to-docx

What gets generated

TurboSign

  • Client configuration with environment variable loading
  • sendSignature() — send documents for e-signature
  • getStatus() — check document/recipient status
  • download() — retrieve the signed PDF
  • Optional helpers when you need them: createSignatureReviewLink() (preview before sending), void(), resend(), and getAuditTrail()
  • A route handler wired into your existing app

Deliverable

  • generateDeliverable() — render a document from a template with variable substitution
  • getDeliverableDetails() — fetch a generated deliverable by ID
  • downloadPDF() / downloadSourceFile() — download the rendered output
  • If you also pick TurboSign, the generate-then-sign workflow (render a template, then route it for signature)

TurboQuote

  • createQuote(), addLineItems(), sendQuote(), downloadQuotePdf() — build, send, and export quotes and proposals
  • Optional catalog scaffolding — createProduct(), createBundle(), createPriceBook(), applyPriceBook()
  • Optional payments path — getPaymentConnectionStatus() (gate on the seller being connected), createPaymentLink(), and getPaymentStatus(), plus a verified quote.payment.succeeded webhook (adds TURBODOCX_WEBHOOK_SECRET)

TurboWebhooks

  • A verified webhook endpoint that subscribes to signature events (for example signature.document.completed)
  • X-TurboDocx-Signature verification so you can trust incoming payloads
  • Requires an administrator-role API key (non-admin keys are rejected); the endpoint is registered under the fixed name signature

TurboPartner

  • Partner client configuration
  • createOrganization() — provision customer organizations
  • listOrganizations() — list managed orgs
  • updateOrganizationEntitlements() — set an organization's features and entitlements
  • A route handler wired into your existing app

@turbodocx/html-to-docx

  • Helper module appropriate for your framework (Express, Next.js API route, Fastify, NestJS controller, etc.)
  • A working endpoint that returns a .docx response
  • Browser-bundle setup if you're running in a static HTML / no-bundler project

Prerequisites

  • API credentials from the TurboDocx dashboard. Which ones depend on the product (the skill writes them into .env and .env.example for you):
    • Most products use TURBODOCX_API_KEY + TURBODOCX_ORG_ID.
    • TurboSign also needs a verified TURBODOCX_SENDER_EMAIL (plus optional TURBODOCX_SENDER_NAME) — sendSignature() fails without it.
    • TurboWebhooks needs an administrator-role API key.
    • TurboPartner uses separate TURBODOCX_PARTNER_API_KEY + TURBODOCX_PARTNER_ID.
    • TurboQuote payments add TURBODOCX_WEBHOOK_SECRET.
  • Node.js to run the npx skills installer.

Source and feedback

The skill is open source at github.com/TurboDocx/quickstart — issues, PRs, and feature requests welcome.