← Back to Skills Marketplace
alexbturchyn

Docuseal

by Alex Turchyn · GitHub ↗ · v1.0.5 · MIT-0
cross-platform ✓ Security Clean
208
Downloads
0
Stars
0
Active Installs
8
Versions
Install in OpenClaw
/install docuseal
Description
Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI - create templates from PDF/DOCX/HTML, send documents for signing, track submiss...
README (SKILL.md)

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_SERVERglobal (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, 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=\x3Cid> 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

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

Usage Guidance
This skill appears coherent for controlling DocuSeal via a CLI. Before installing or using it: 1) verify the docuseal CLI package (npm package name and publisher) and the linked GitHub/source to ensure you trust the binary that will run on your system; 2) provide an API key with least privilege and consider creating a dedicated key/account for automation; 3) double-check DOCUSEAL_SERVER when using a self-hosted URL (ensure it points to your instance, not a third party); and 4) review any emails/recipients you pass to the CLI since the skill will send signature requests. The only minor concerns are metadata inconsistencies (registry vs SKILL.md about install and primaryEnv) — these are not dangerous but you may want to confirm the authoritative install instructions and provenance.
Capability Analysis
Type: OpenClaw Skill Name: docuseal Version: 1.0.5 The DocuSeal skill bundle provides a legitimate interface for managing e-signature workflows via the official DocuSeal CLI. It includes comprehensive documentation for templates, submissions, and field tagging (PDF/DOCX/HTML), with installation steps correctly pointing to the official 'docuseal' npm package. No evidence of malicious intent, data exfiltration, or prompt injection was found; the instructions are strictly focused on proper CLI parameter formatting and usage patterns.
Capability Tags
cryptorequires-walletcan-make-purchases
Capability Assessment
Purpose & Capability
The name/description (DocuSeal CLI) align with the required binary (docuseal) and the two required env vars (DOCUSEAL_API_KEY, DOCUSEAL_SERVER). These are exactly the kinds of things an e-signature CLI would need. Minor metadata mismatch: the registry shows no primary credential while the SKILL.md declares primaryEnv: DOCUSEAL_API_KEY, which is reasonable but inconsistent metadata.
Instruction Scope
SKILL.md contains explicit CLI usage patterns, examples, and references. Instructions focus on running the docuseal CLI, supplying flags/JSON bodies, and setting the API key/server. There are no directives to read unrelated files, harvest additional env vars, or send data to unexpected endpoints.
Install Mechanism
The registry entry is instruction-only (no platform install spec), but SKILL.md includes an npm install recommendation (package: docuseal). Installing via npm is a common/traceable mechanism; it is moderate risk compared to no install. There are no arbitrary download URLs or archive extracts in the package.
Credentials
Only DOCUSEAL_API_KEY and DOCUSEAL_SERVER are required — both are appropriate and directly tied to service access. The skill does not request unrelated secrets or high counts of credentials. (Note: SKILL.md marks DOCUSEAL_API_KEY as primaryEnv while registry metadata lists no primary credential.)
Persistence & Privilege
The skill is not always-enabled, does not request elevated persistence, and is instruction-only with no system‑wide modifications. Autonomous model invocation is allowed (platform default) but not combined with other red flags.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install docuseal
  3. After installation, invoke the skill by name or use /docuseal
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.5
- Bumped skill version from 1.0.4 to 1.0.5 in metadata. - No functionality or documentation changes detected.
v1.0.4
- CLI skill refactored and renamed to "docuseal-cli" for more precise, terminal-based workflows. - Major documentation and protocol update: clearer environment variable usage (DOCUSEAL_API_KEY, DOCUSEAL_SERVER), installation steps, command syntax, and common usage patterns. - Added comprehensive references for templates, submissions, submitters, DOCX variables, field tags, and HTML fields. - Removed Node.js script instructions (previously scripts/cli.js), focusing on shell CLI usage. - All commands now require explicit flags and inputs; includes troubleshooting for common mistakes with bracket/JSON notation for complex parameters.
v1.0.3
- Added scripts/config.js for improved configuration management. - Updated scripts/cli.js to support the new configuration file. - No user-facing changes to SKILL.md or main functionality.
v1.0.2
- Removed the `ping` command from CLI usage. - Simplified the `create-template` command: now only supports document upload via URL (base64 file upload removed). - Updated documentation to reflect changes in supported commands and their options. - Minor clarifications and cleanup in the SKILL.md notes.
v1.0.1
Minor update with metadata improvements and additional security note. - Bumped version to 1.0.1 in metadata. - Added credential field to metadata for MCP token. - Appended security note: warns about base64 file content possibly appearing in shell history and process lists; recommends mitigations.
v1.0.0
- Replaced usage references from scripts/mcp.js to scripts/cli.js in documentation and examples. - Added scripts/cli.js and removed scripts/mcp.js to reflect the new CLI entry point. - Fixed typo in metadata: "requiress" corrected to "requires".
v0.1.1
- No changes detected in this release. - Skill version incremented to 0.1.1 without modifications to content or functionality.
v0.1.0
Initial release of the DocuSeal skill. - Manage DocuSeal document templates and e-signatures via MCP endpoint. - Provides CLI script for searching, creating templates, sending documents, and searching documents. - Requires environment variables DOCUSEAL_URL and DOCUSEAL_MCP_TOKEN. - All interactions use JSON-RPC 2.0 over HTTP POST. - Supports Node.js 18+ with no external dependencies.
Metadata
Slug docuseal
Version 1.0.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 8
Frequently Asked Questions

What is Docuseal?

Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI - create templates from PDF/DOCX/HTML, send documents for signing, track submiss... It is an AI Agent Skill for Claude Code / OpenClaw, with 208 downloads so far.

How do I install Docuseal?

Run "/install docuseal" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Docuseal free?

Yes, Docuseal is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Docuseal support?

Docuseal is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Docuseal?

It is built and maintained by Alex Turchyn (@alexbturchyn); the current version is v1.0.5.

💬 Comments