indesign-cli

Operate Adobe InDesign via CLI tool discovery and JSX execution.

35|5|Updated Sep 20, 2025
One-click install
npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill indesign-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indesign-cli
Source: https://github.com/zhanglongxiao111/indesign-cli/tree/main/agent-harness/cli_anything/indesign/skills
Command: npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill indesign-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Agents reliably operate real Adobe InDesign and orchestrate JSX execution, tool discovery/calls, and exported-output verification without hardcoding unstable tool details into the task context.

Core Features & Use Cases

  • Tooling truth & discovery loop: Uses the CLI as the source of truth for tool domains, search results, and per-tool JSON schemas so Agents load only what they need.
  • Deterministic JSX workflows: Routes multi-step actions through file-based .jsx execution (with session/state persisted via files like .indesign-cli/session.json) instead of fragile one-off prompts.
  • Export verification: Confirms PDF/IDML/image outputs using the CLI’s export.verify flow rather than assuming success from a process exit code.
  • Template-slot orchestration: Supports advanced template workflows by following the tool-driven blueprint inspection and slot population flow to avoid guessing slot names.
  • Plugin integration guardrails: Encourages checking/validating plugins and calling plugin-exposed tools only through the host CLI tool schema and tool call.

Quick Start

From your target project root, run environment health checking and then let the Agent query tools, inspect the needed tool schema, and execute the required JSX or export-verify steps using indesign-cli.

Frequently Asked Questions about indesign-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Adobe InDesign document creation with an AI agent?

Automating Adobe InDesign document creation with an AI agent requires a CLI bridge that routes multi-step JSX execution and tool discovery calls. This setup allows agents to manipulate pages and templates reliably without hardcoding unstable tool details into the task context.

How does JSX automation work for Adobe InDesign template slot filling?

JSX automation for template slot filling works by routing multi-step actions through file-based .jsx execution with session state persisted in files. The CLI inspects tool-driven blueprints to identify exact slot names, ensuring agents populate templates accurately without guessing slot identifiers.

Do I need a local Adobe InDesign installation to use an MCP bridge for publishing automation?

Yes, local Adobe InDesign installation and a Node/MCP bridge environment are required for this CLI automation. This setup enables CLI-guided discovery, file-based JSX execution, and explicit cross-step state persistence during AI-driven publishing workflows.

What is the best way to verify PDF and IDML exports in AI-driven publishing workflows?

The best way to verify PDF and IDML exports is using the CLI's export.verify flow rather than assuming success from a process exit code. This method parses JSON-mode results to confirm the correctness of PDF, IDML, and image outputs during AI-driven publishing.

How do agents discover and call plugin-exposed tools in Adobe InDesign?

Agents discover and call plugin-exposed tools by using the CLI as the source of truth for tool domains and per-tool JSON schemas. This guardrail ensures plugin integration validates plugins first and calls their exposed tools safely through the host CLI.

Why does my Adobe InDesign automation script fail during multi-step template manipulation?

Adobe InDesign automation scripts fail during multi-step template manipulation when relying on fragile one-off prompts instead of deterministic JSX workflows. Using file-based .jsx execution with explicit cross-step state persistence prevents failures in document and page manipulation.