Update to 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 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.\n",
  "included_files": [
    {
      "relative_path": ".DS_Store",
      "size_in_bytes": 6148
    },
    {
      "relative_path": "references/docx-variables.md",
      "size_in_bytes": 2395
    },
    {
      "relative_path": "references/field-tags.md",
      "size_in_bytes": 3718
    },
    {
      "relative_path": "references/html-fields.md",
      "size_in_bytes": 5456
    },
    {
      "relative_path": "references/submissions.md",
      "size_in_bytes": 11466
    },
    {
      "relative_path": "references/submitters.md",
      "size_in_bytes": 2270
    },
    {
      "relative_path": "references/templates.md",
      "size_in_bytes": 7765
    }
  ],
  "name": "docuseal-cli",
  "skill_md_contents": "---\nname: docuseal-cli\ndescription: >\n  Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI -\n  create templates from PDF/DOCX/HTML, send documents for signing, track submissions,\n  and update submitters. Use when the user wants to run DocuSeal commands in the shell,\n  scripts, or CI/CD pipelines. Always load this skill before running `docuseal` commands.\nlicense: MIT\nmetadata:\n  author: DocuSeal\n  version: \"1.0.7\"\n  homepage: https://www.docuseal.com\n  source: https://github.com/docusealco/docuseal-cli\n  openclaw:\n    emoji: \"📝\"\n    requires:\n      env:\n        - DOCUSEAL_API_KEY\n        - DOCUSEAL_SERVER\n      bins:\n        - docuseal\n      primaryEnv: DOCUSEAL_API_KEY\n    install:\n      - id: npm\n        kind: npm\n        package: docuseal\n        bins:\n          - docuseal\n        label: Install DocuSeal CLI (npm)\n---\n\n## Agent Protocol\n\n**Rules for agents:**\n- Supply ALL required flags — the CLI will not prompt for missing parameters.\n- Output is always JSON.\n- Use `-d key=value` (bracket notation) or `-d '{\"..\": \"..\"}'` (JSON) for body and array parameters.\n\n## Authentication\n\nSet environment variables:\n- `DOCUSEAL_API_KEY` — API key (required). Get yours at https://console.docuseal.com/api\n- `DOCUSEAL_SERVER` — `global` (default), `europe`, or full URL for self-hosted (e.g. `https://docuseal.yourdomain.com`)\n\n## Available Commands\n\n| Command Group | What it does |\n|---|---|\n| `templates` | list, retrieve, update, archive, create-pdf, create-docx, create-html, clone, merge, update-documents |\n| `submissions` | list, retrieve, update, archive, create, send-emails, create-pdf, create-docx, create-html, documents |\n| `submitters` | list, retrieve, update |\n\nRead the matching reference file for detailed flags and examples.\n\n## Common Mistakes\n\n| # | Mistake | Fix |\n|---|---|---|\n| 1 | **Forgetting `-d template_id=<id>` on `submissions create`** | `--template-id` is a flag; submitters and other body params go via `-d` |\n| 2 | **Passing a plain file path as a URL** | `--file` accepts a local path; for remote files use `-d \"documents[0][file]=https://...\"` |\n| 3 | **Expecting array params as comma-separated** | Arrays use bracket notation: `-d \"template_ids[]=1\"` `-d \"template_ids[]=2\"` |\n| 4 | **Using `templates create-pdf` without a Pro plan** | Commands marked _(Pro)_ require a DocuSeal Pro subscription |\n| 5 | **Sending to multiple recipients with `submissions create`** | Use `submissions send-emails --emails a@b.com,c@d.com` for bulk; `submissions create` is per-submitter |\n\n## Security\n\nThe 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.\n\n## Common Patterns\n\n**List templates:**\n```bash\ndocuseal templates list --q \"NDA\" --limit 20\n```\n\n**Create a template from a PDF and send for signing:**\n```bash\ndocuseal templates create-pdf --file contract.pdf --name \"NDA\"\ndocuseal submissions send-emails --template-id 1001 --emails signer@example.com\n```\n\n**Create a submission with pre-filled fields (bracket notation):**\n```bash\ndocuseal submissions create --template-id 1001 \\\n  -d \"submitters[0][email]=john@acme.com\" \\\n  -d \"submitters[0][values][Company Name]=Acme Corp\"\n```\n\n**Create a submission with pre-filled fields (JSON):**\n```bash\ndocuseal submissions create --template-id 1001 \\\n  -d '{\"submitters\": [{\"email\": \"john@acme.com\", \"values\": {\"Company Name\": \"Acme Corp\"}}]}'\n```\n\n**Check signing status:**\n```bash\ndocuseal submissions list --template-id 1001 --status pending\n```\n\n**Update a submitter:**\n```bash\ndocuseal submitters update 201 --email new@acme.com --send-email\n```\n\n## When to Load References\n\n- **Creating or managing templates** → [references/templates.md](references/templates.md)\n- **Sending documents for signing or tracking status** → [references/submissions.md](references/submissions.md)\n- **Using dynamic content variables in DOCX** → [references/docx-variables.md](references/docx-variables.md)\n- **Embedding field tags in PDF/DOCX** → [references/field-tags.md](references/field-tags.md)\n- **Writing HTML templates with field tags** → [references/html-fields.md](references/html-fields.md)\n- **Listing or updating signers** → [references/submitters.md](references/submitters.md)\n"
}