Your AI Agent Can Now Build the Document: Autype CLI and Autype Skill Are Here

AI agents are good at writing. Until now, getting them from a strong draft to a reliable business document still required too much manual work.

The agent could produce the content, but someone still had to move it into the right template, repair page breaks, apply company styles, check internal references, insert approved sections, validate form fields and inspect the final DOCX or PDF. Giving the agent access to a generic code environment did not solve the underlying problem. It only moved document assembly into scripts and temporary files.

Today, Autype makes that final step directly accessible to developers and AI agents with two new open repositories:

• Autype CLI is the official command line interface and TypeScript client for the Autype Developer API.
• Autype Agent Skill teaches compatible AI agents how to create and operate documents with Autype Extended Markdown and the CLI.

Together, they give agents a structured path from an instruction to a validated and rendered document without asking the model to reconstruct DOCX internals or generate fragile OOXML.

Two components with different jobs

The CLI and the skill are designed to work together, but they solve different problems.

Component	What it does	Best suited for
Autype CLI	Executes document operations against Autype and exposes stable JSON output	Terminals, CI pipelines, scripts and AI agents with shell access
Autype Agent Skill	Gives a compatible agent the workflow, syntax guidance and quality rules it needs	Codex, Claude Code, Cursor, GitHub Copilot, OpenCode and other Agent Skills clients
Autype MCP	Exposes a connected, self describing Autype toolset	MCP clients that should work directly with remote Autype tools

The skill does not duplicate the complete API documentation inside every conversation. It loads focused references only when they are needed. The CLI performs the actual validation, rendering, resource discovery and online operations. Autype MCP remains a separate integration and continues to describe its own tools.

What Autype CLI can do

Autype CLI uses one authoring model: document content is written in Autype Extended Markdown. JSON and YAML are used for request data, variables and reusable style definitions, not as a second document content format.

With the CLI, developers and agents can:

• validate Extended Markdown before rendering
• run export readiness checks before spending credits
• render PDF, DOCX and other supported formats
• create and update persistent Autype documents
• list and use workspace templates
• discover and apply system or company styles
• retrieve versioned Reusable Blocks and insert exact directives
• inspect the bundled Developer API operations and schemas
• call published API operations, including uploads and binary downloads
• use deterministic JSON output in CI and agent workflows
• use the same package as a typed TypeScript API client

This matters because an agent no longer has to improvise a new document generation script for every task. It can work with a stable document source, validate that source, render it through the Autype document engine and inspect the result.

Install Autype CLI

Autype CLI requires Node.js 20 or newer. It is publicly available on npm as @autype/cli.

Run it without a permanent installation:

npx @autype/cli doctor --json

Or install it globally:

npm install --global @autype/cli
autype --help

Authenticate once with an API key from the Autype web app:

autype auth login
autype doctor --json

The login prompt hides the key, verifies it and stores it in a user only credentials file. For CI, provide the key through standard input or a protected environment variable. Do not place credentials in prompts, source documents or command arguments.

Create and render a first document

Create a file named report.mdd:

# Quarterly report

Prepared for **{{companyName}}**.

## Highlights

* Revenue increased by 18%.
* Customer retention reached 94%.

Keep variables and document settings in report.json:

{
  "document": {
    "type": "pdf",
    "size": "A4",
    "orientation": "portrait",
    "language": "en"
  },
  "stylePresetId": "system:executive-annual-report",
  "variables": {
    "companyName": "Acme Ltd"
  }
}

Then validate, check and render it:

autype validate report.mdd --data report.json --json
autype readiness report.mdd --data report.json --json
autype render report.mdd --data report.json --output report.pdf --json

The source remains readable, diffable and efficient for an agent to edit. The selected Autype style controls the visual system centrally instead of repeating formatting instructions throughout the content.

Install the Autype Agent Skill

The autype-documents skill follows the open Agent Skills specification. The same portable skill folder can be used by compatible clients without maintaining separate copies for every vendor.

Install it with the open skills CLI:

npx skills add centerbitco/autype-agent-skills --skill autype-documents

You can also target supported agents explicitly:

npx skills add centerbitco/autype-agent-skills \
  --skill autype-documents \
  --agent codex claude-code opencode cursor github-copilot

The installer detects the selected clients and places the complete skill in their native location. The repository also documents manual installation paths for Codex, Claude Code, Cursor, OpenCode, GitHub Copilot, Gemini CLI, OpenClaw, Hermes Agent and other compatible clients.

Once installed, an agent can activate it automatically for relevant document work or you can request it explicitly:

Use $autype-documents to create, validate and render a professional quarterly report.

The skill guides the agent through source creation, focused syntax lookup, validation, export readiness, rendering and visual quality assurance. If the CLI is unavailable, it can still author an offline .mdd file, but it must clearly report that server validation and render quality assurance are still pending.

Templates, styles and approved content stay reusable

The launch is not limited to creating a new document from an empty file.

An agent can list workspace templates, inspect the selected template and render it with new variables. It can select a system style or an organization style instead of inventing visual rules. It can retrieve an existing Reusable Block and insert the exact reference or a versioned snapshot into the document.

That makes the same workflow useful for both complete AI document creation and controlled template automation. A proposal can begin with generated content. A contract can begin with an approved template and fixed legal blocks. Both are processed by the same Autype document engine and can produce editable DOCX or final PDF output.

Built for agents, useful far beyond chat

Stable --json output, documented exit codes, local schema validation, asynchronous job polling and safe file writes make the CLI suitable for repeatable automation. A team can use the same commands during local development, in a deployment pipeline or inside an agent sandbox.

The package also exports a typed AutypeClient for applications that need the same API access without starting a separate process. For operations without a dedicated top level command, the CLI can discover the current OpenAPI contract and call published Developer API operations by their operation ID.

The result is a much smaller gap between what an AI agent proposes and what a business can actually deliver.

Available now

Autype CLI 0.1.0 and the Autype Agent Skill are available now:

• Install @autype/cli from npm
• View the Autype CLI repository
• View the Autype Agent Skills repository
• Open the Autype documentation
• Connect through Autype MCP

The web app, Developer API, MCP, CLI and Agent Skill now provide different entry points into the same goal: reliable, reusable and visually controlled business documents built with AI.