Docuseal cli

Skill docusealco/docuseal-agent-skills/skills/docuseal-cli

Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI - create templates from PDF/DOCX/HTML, send documents for signing, track submissions, and update submitters. Use when the user wants to run DocuSeal commands in the shell, scripts, or CI/CD pipelines. Always load this skill before running `docuseal` commands.From its SKILL.md

Install

npx -y skills add docusealco/docuseal-agent-skills --skill docuseal-cli

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

reads credentialsReads from 2 credential sources: `DOCUSEAL_API_KEY` and 1 more.
8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.5 KB, 956 tokens by cl100k_base, as published. Nobody here has run it

Agent Protocol

Rules for agents:

Supply ALL required flags — the CLI will not prompt for missing parameters.
Output is always JSON.
Use -d key=value (bracket notation) or -d '{"..": ".."}' (JSON) for body and array parameters.

Authentication

Set environment variables:

DOCUSEAL_API_KEY — API key (required). Get yours at https://console.docuseal.com/api
DOCUSEAL_SERVER — global (default), europe, or full URL for self-hosted (e.g. https://docuseal.yourdomain.com)

Available Commands

Command Group	What it does
`templates`	list, retrieve, update, archive, create-pdf, create-docx, create-html, clone, merge, update-documents
`submissions`	list, retrieve, update, archive, create, send-emails, create-pdf, create-docx, create-html, documents
`submitters`	list, retrieve, update

Read the matching reference file for detailed flags and examples.

Common Mistakes

#	Mistake	Fix
1	Forgetting `-d template_id=<id>` on `submissions create`	`--template-id` is a flag; submitters and other body params go via `-d`
2	Passing a plain file path as a URL	`--file` accepts a local path; for remote files use `-d "documents[0][file]=https://..."`
3	Expecting array params as comma-separated	Arrays use bracket notation: `-d "template_ids[]=1"` `-d "template_ids[]=2"`
4	Using `templates create-pdf` without a Pro plan	Commands marked (Pro) require a DocuSeal Pro subscription
5	Sending to multiple recipients with `submissions create`	Use `submissions send-emails --emails [email protected],[email protected]` for bulk; `submissions create` is per-submitter

Security

The CLI accepts user-provided file paths, remote URLs (documents[0][file]=https://...), and HTML content as template input. This is by design — all content originates from the authenticated user and is sent directly to the DocuSeal API over HTTPS. The CLI does not fetch, render, or execute remote content locally; it passes references to the server for processing. No user input is interpolated into shell commands.

Common Patterns

List templates:

docuseal templates list --q "NDA" --limit 20

Create a template from a PDF and send for signing:

docuseal templates create-pdf --file contract.pdf --name "NDA"
docuseal submissions send-emails --template-id 1001 --emails [email protected]

Create a submission with pre-filled fields (bracket notation):

docuseal submissions create --template-id 1001 \
  -d "submitters[0][email][email protected]" \
  -d "submitters[0][values][Company Name]=Acme Corp"

Create a submission with pre-filled fields (JSON):

docuseal submissions create --template-id 1001 \
  -d '{"submitters": [{"email": "[email protected]", "values": {"Company Name": "Acme Corp"}}]}'

Check signing status:

docuseal submissions list --template-id 1001 --status pending

Update a submitter:

docuseal submitters update 201 --email [email protected] --send-email

When to Load References

Creating or managing templates → references/templates.md
Sending documents for signing or tracking status → references/submissions.md
Using dynamic content variables in DOCX → references/docx-variables.md
Embedding field tags in PDF/DOCX → references/field-tags.md
Writing HTML templates with field tags → references/html-fields.md
Listing or updating signers → references/submitters.md

What ships with it: 6 files

32.3 KB alongside SKILL.md

references/

Gives 1 of the 12 instructions most pdf office docs skills give in 956 tokens

Counted across 569 of the 585 authors here whose files we hold, read 2026-09-06

Ensure every slide fits inside one viewportin 20 of 569, across 11 files
Check for product marketing context firstin 15 of 569, across 5 files
Ask for the minimum neededin 15 of 569, across 5 files
Set the API key environment variablehere, and in 15 of 569, across 10 files
Support keyboard and touch navigationin 14 of 569, across 5 files
Match the buyer stagein 13 of 569, across 3 files
Split overflowing content into multiple slidesin 12 of 569, across 3 files
Set page size explicitly for consistent resultsin 12 of 569, across 5 files
Convert documents to markdown using pandocin 12 of 569, across 6 files
Read STYLE_PRESETS.md before generatingin 12 of 569, across 7 files
Send multipart POST requests to the APIin 12 of 569, across 7 files
Use smart quotes for new contentin 11 of 569, across 4 files

Said here and by no other author read

Supply all required flags for the CLI
Use bracket notation for array parameters

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.