[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWAP5YEVDWCVFC7DPSGDP4":3,"skill-same:01M7AWAP5YEVDWCVFC7DPSGDP4":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AWAP5YEVDWCVFC7DPSGDP4","docuseal-cli",null,"Use `dscli` for ALL DocuSeal work — uploading templates, placing fields, creating submissions, sharing signing URLs. The CLI bakes in workarounds for DocuSeal's quirks (silent page-drop on \u002Ftemplates\u002Fpdf, submission field-state caching at create time, immediate-email-on-create traps, default_value bleed). Triggers on \"docuseal\", \"dscli\", \"send a signature request\", \"create a signing form\", anything involving DocuSeal templates or submissions.","barkleesanders\u002Fclaude-code-starter","barkleesanders","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30680901?v=4","01M7AW019CGBYWDA8MFJEN1JXC","Barklee Sanders","01M7AW01A5H994ASJ2QZPW67AV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdocuseal-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docuseal-cli\ndescription: Use `dscli` for ALL DocuSeal work — uploading templates, placing fields, creating submissions, sharing signing URLs. The CLI bakes in workarounds for DocuSeal's quirks (silent page-drop on \u002Ftemplates\u002Fpdf, submission field-state caching at create time, immediate-email-on-create traps, default_value bleed). Triggers on \"docuseal\", \"dscli\", \"send a signature request\", \"create a signing form\", anything involving DocuSeal templates or submissions.\n---\n\n# DocuSeal CLI (`dscli`)\n\n`dscli` is the agent-friendly DocuSeal client. Located at\n`$HOME\u002Ftools\u002Fdocuseal\u002Fdscli`, symlinked to `~\u002F.local\u002Fbin\u002Fdscli`.\n\nAPI key at `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt` (or `DOCUSEAL_API_KEY` env).\n\n## DO NOT bypass dscli with raw curl\u002FHTTP unless `dscli` lacks the operation\nyou need. The CLI exists because every raw-call path has at least one trap\nthat ate hours on 2026-05-06. Specifically:\n\n1. **`POST \u002Ftemplates\u002Fpdf` silently drops field `area.page`.** Every field\n   you upload with `page=N` ends up at `page=0` regardless. `dscli template\n   upload` therefore creates the template *without* fields; use\n   `dscli template set-fields` to attach fields via PUT, which DOES respect\n   `page` (because the CLI also passes `attachment_uuid` per area).\n\n2. **Submissions cache the template's field layout at create time.** Editing\n   a template after a submission exists DOES NOT update the in-flight\n   submission's signing UI. Always `dscli submission archive` and recreate\n   after changing template fields.\n\n3. **`POST \u002Fsubmissions` with `send_email=true` sends emails IMMEDIATELY.**\n   Archiving the submission afterwards does not recall the email — the\n   recipient's inbox now has a link that 404s with \"This submission has\n   been deleted.\" `dscli submission create` defaults `send_email=false`;\n   you opt in only after verifying field placement via `dscli pdf preview`\n   or `dscli url screenshot`.\n\n4. **`default_value` on a text field renders as static text on the PDF\n   underlay.** It can visually bleed near adjacent fields and confuse\n   signers. Avoid unless really needed; pass user-provided values via the\n   submitter's `values` map at submission create instead.\n\n5. **Match signature field rects to the PDF's signature-line widget rects.**\n   DocuSeal renders an icon-sized \"click to sign\" indicator at the field\n   position; making the rect huge just covers nearby printed labels and\n   makes the user think the box is doing something it isn't. Use\n   `dscli pdf widgets` to extract the form's actual widget rects.\n\n6. **`page` in fields.json is 0-INDEXED — this is the #1 cause of \"signature\n   placed on the wrong page \u002F didn't render.\"** (2026-06-24, root cause found\n   by reading `dscli` line 291 + `cmd_template_set_fields`.) A multi-page\n   records request put its two signature fields on `\"page\": 2` and `\"page\": 4`\n   (thinking 1-indexed = \"the 2nd and 4th printed pages\"). The PDF had 4 pages\n   = valid 0-indexed pages **0,1,2,3**. So `page:2` landed on the 3rd printed\n   page (wrong) and `page:4` **does not exist** → DocuSeal silently dropped\u002F\n   mis-placed it; the signer \"completed\" the form but the signature never\n   rendered on the visible signature line. THE FIX: if the signature line is on\n   the Nth printed page, use `\"page\": N-1`. Locate it programmatically:\n   `for i,page in enumerate(fitz.open(pdf)): page.search_for(\"Signature:\")` —\n   the `i` it prints IS the value to put in `\"page\"`.\n   **ALWAYS pass `--pdf \u003Cfile>` to `set-fields`** — with `--pdf`, dscli calls\n   `pdf_page_size(pdf, page)` which raises `IndexError: page N not in document`\n   on an out-of-range index, turning this silent bug into a loud error. Without\n   `--pdf` it falls back to 612×792 and places the field on a phantom page.\n   (Treat any `IndexError: page N not in document` from set-fields as \"your\n   page number is too high by one\" — do NOT work around it by dropping `--pdf`.)\n\n   Secondary: keep signature rects ≥ 40pt tall and ≥ 250pt wide on a clearly-\n   labeled \"Signature:\" block (a too-short rect can clip the rendered image),\n   but the page index is the thing that bit hardest here.\n\n7. **ALWAYS verify the SIGNED PDF, not just `status: completed`.** A\n   submission can report `completed` with every field value populated\n   server-side while one or more signatures fail to render on the page.\n   After any signer finishes, download the signed document\n   (`dscli --json submission get \u003CSID>` → `.documents[].url` → curl it)\n   and rasterize EVERY signature page (`fitz` → `get_pixmap` → Read the\n   PNG) to confirm each signature + date is actually visible at its\n   field. `status: completed` is NOT proof the signatures rendered — the\n   pixels are. Especially critical for multi-page \u002F multi-signature docs.\n\n8. **Unembedded fonts silently destroy the document downstream — `template upload`\n   now BLOCKS on them** (added 2026-07-24). A PDF whose fonts aren't embedded is\n   accepted by DocuSeal and looks fine on screen, then fails at the mail vendor:\n   **Lob** — now the ONLY mail vendor (PostGrid removed 2026-08-12) — rejects it\n   outright with `HTTP 422 unembedded_fonts`, so an unembedded font is a HARD STOP\n   on the send, not a cosmetic warning. (The historical alternative was worse and\n   is why this gate exists: PostGrid accepted the same file silently and\n   *rasterized* it — a 4 MB upload became a **137 MB** print artifact that stalled\n   at `status: printing` for 81 days with `errorMessage: null`.)\n   `dscli template upload` runs `pdffonts` first and refuses to upload, printing the\n   exact remedy. Use `--embed-fonts` to auto-fix via ghostscript (also shrank a real\n   87-page packet 4.0 MB → 2.8 MB), or `--allow-unembedded` to override.\n   **Also re-embed AFTER signing** — DocuSeal re-renders its own output, so the\n   signed PDF must be checked again before it goes to any print\u002Fmail vendor:\n   `pdffonts signed.pdf | awk 'NR>2 && $(NF-3)==\"no\"'` must be empty.\n   Reference incident: Sanders ABCMR filing, 63 unembedded fonts across 125 total.\n\n## Commands at a glance\n\n```\ndscli --help                                      # full reference\ndscli [--json] template upload \u003Cpdf> [--name X]   # upload, no fields yet\ndscli [--json] template add-roles \u003Cid> \"R1,R2\"    # add submitter roles\ndscli [--json] template set-fields \u003Cid> \u003Cjson> [--pdf \u003Cpdf>]\n                                                  # PUT fields (correct path)\ndscli [--json] template get \u003Cid> [--fields-only]\ndscli [--json] template list\ndscli [--json] template delete \u003Cid> --force       # archives subs first\ndscli [--json] template archive-subs \u003Cid>\n\ndscli [--json] submission create \u003Ctid> \u003Cjson>\n       [--send-email] [--order preserved] [--subject X --body Y]\ndscli [--json] submission get \u003Cid>\ndscli [--json] submission list [--template-id N]\ndscli [--json] submission archive \u003Cid>\ndscli [--json] submission urls \u003Cid>               # role | name | status | URL\n\ndscli [--json] pdf widgets \u003Cpdf>                  # PDF AcroForm fields\ndscli [--json] pdf prefill \u003Cpdf> \u003Cout> \u003Cvalues.json> [--checkboxes-json '...']\ndscli [--json] pdf preview \u003Cpdf> --out preview.pdf --template-id \u003Cid>\n                                                  # Overlay rects on PDF\n                                                  # for visual verification\n\ndscli [--json] url check \u003Curl>                    # live? archived? title\ndscli [--json] url screenshot \u003Curl> [--out X --full]   # via agent-browser\n```\n\n`--json` is a GLOBAL flag (must come before the subcommand).\n\n## Standard end-to-end flow\n\n```bash\n# 1. Pre-fill any data fields on the source PDF (subject info, recipient,\n#    reason text, checkboxes). Bake so DocuSeal sees a static document.\ndscli pdf widgets form.pdf > \u002Ftmp\u002Fwidgets.json   # discover field names\necho '{\"FullName-FLD\": \"Jane Doe\", ...}' > \u002Ftmp\u002Fvalues.json\ndscli pdf prefill form.pdf \u002Ftmp\u002Fprefilled.pdf \u002Ftmp\u002Fvalues.json \\\n      --checkboxes-json '[\"Box1\",\"Box2\"]'\n\n# 2. Upload the prefilled PDF as a template (no fields yet).\nTID=$(dscli --json template upload \u002Ftmp\u002Fprefilled.pdf --name \"Form X\" \\\n        | jq -r .id)\n\n# 3. Add the signing roles you need. Names become role IDs in submissions.\ndscli template add-roles \"$TID\" \"Witness 1,Subject,Witness 2\"\n\n# 4. Place signature\u002Ftext\u002Fdate\u002Fcheckbox fields. fields.json schema:\n#    [\n#      {\"name\":\"W1 Sig\", \"type\":\"signature\", \"role\":\"Witness 1\",\n#       \"rect\":[21,707,303,717], \"page\":1, \"required\":true},\n#      {\"name\":\"W1 Addr\", \"type\":\"text\", \"role\":\"Witness 1\",\n#       \"rect\":[21,735,303,771], \"page\":1, \"required\":true},\n#      ...\n#    ]\n#    Rect is PDF points (top-left origin). Pass --pdf so exact page dims\n#    are used (avoids assuming 612×792).\ndscli template set-fields \"$TID\" fields.json --pdf \u002Ftmp\u002Fprefilled.pdf\n\n# 5. VISUALLY VERIFY before sending. Render a preview with rects overlaid.\ndscli pdf preview \u002Ftmp\u002Fprefilled.pdf --template-id \"$TID\" \\\n      --out \u002Ftmp\u002Fpreview.pdf\n# Open \u002Ftmp\u002Fpreview.pdf in Preview.app; confirm rects sit where signers\n# will actually need to sign \u002F type.\n\n# 6. Create the submission. send_email=false by default — you control how\n#    URLs are shared.\ncat > \u002Ftmp\u002Fsubmitters.json \u003C\u003CEOF\n[\n  {\"role\":\"Witness 1\",\"email\":\"a@x.com\",\"name\":\"Alice\"},\n  {\"role\":\"Subject\",  \"email\":\"b@x.com\",\"name\":\"Bob\"},\n  {\"role\":\"Witness 2\",\"email\":\"c@x.com\",\"name\":\"Carol\"}\n]\nEOF\ndscli --json submission create \"$TID\" \u002Ftmp\u002Fsubmitters.json \\\n      --order preserved > \u002Ftmp\u002Fsub.json\nSID=$(jq -r .submission_id \u002Ftmp\u002Fsub.json)\n\n# 7. Surface URLs to the user (or trigger DocuSeal email by recreating\n#    with --send-email once you're confident).\ndscli submission urls \"$SID\"\n\n# 8. After signers complete: pull the signed PDF.\ndscli --json submission get \"$SID\" | jq '.documents'\n```\n\n## CRITICAL: every field needs a `uuid` attribute\n\nDocuSeal's signing frontend uses `\u003Cinput name=\"values[\u003Cfield.uuid>]\">` to\ncollect each field's value. If a field has no `uuid` attribute, `field.uuid`\nis JavaScript-undefined and the input becomes `name=\"values[undefined]\"`.\nALL fields without a uuid then share the SAME form slot — typing in any\none of them overwrites the others. The \"type a sig and the address\nappears in both\" bug is purely a manifestation of this.\n\n`dscli template set-fields` auto-generates a UUIDv4 per field if you\ndon't supply one. Don't bypass it. If you ever PUT fields directly via\nHTTP, include a unique `uuid` per field or expect cross-field overwrites.\n\nVerified 2026-05-08 via chrome-cdp: with `uuid` per field, the live form's\nhidden inputs are `values[\u003Csig_uuid>]` and `values[\u003Caddr_uuid>]` — separate.\nWithout uuid, both collapse to `values[undefined]`.\n\n## \"Type text\" signature mode contaminates next text field (frontend bug)\n\nWhen a submitter clicks the signature field, picks **\"Type text\"** mode,\ntypes their name (or any text), and clicks NEXT, DocuSeal does two things:\n\n1. Stores the typed cursive as a signature image attachment (correct).\n2. **Writes the image's attachment UUID into the local state of the\n   next text field for that submitter** (BUG).\n\nThe text field then renders something like\n`77866bd2-fe60-4c80-9533-e0f6ccff8e66` until the user manually clears it.\nIf the submitter has a cached prior value (e.g., they typed their address\ninto a sig field on an earlier attempt), the cached value renders instead.\n\nThe server-side `submitter.values` stays `[]` — this leak is purely\nclient-side. The REST API does NOT expose `with_typed_signature` at any\nlevel; verified that template, submission, and submitter PUTs with every\nplausible shape silently no-op. The rendered HTML always has\n`data-with-typed-signature=\"true\"`.\n\n**Workarounds:**\n- Tell submitters to use **\"Sign on the touchscreen\"** (Draw) or **Upload**,\n  never \"Type text\".\n- Make signature field rects ≥ 30pt tall. The PDF widget rect for a\n  signature LINE is typically ~10pt; reusing that rect causes the typed\n  cursive image to render at natural size and visually overflow into the\n  field below, looking like a duplicated value even before the actual\n  bug fires.\n\n## Browser-side autofill trap (`data-reuse-signature`)\n\nThe signing page renders with `data-reuse-signature=\"true\"` hardcoded by\nDocuSeal's UI — not exposed via the public REST API. Once a user has typed\n*anything* into a signature field on this account\u002Fbrowser before, DocuSeal\ncaches it in browser localStorage as their \"preferred signature\" and\nauto-suggests it on every new submission, even on freshly-created\nsubmissions with `default_value=\"\"` on all fields. The cached string can\nalso bleed into adjacent text fields.\n\n**This is NOT fixable via the API.** Verified: `POST \u002Fsubmissions\n{reuse_signature: false}`, `PUT \u002Ftemplates\u002F{id} {preferences: {...}}`, and\nevery other shape silently no-op. The rendered HTML still has\n`data-reuse-signature=\"true\"` regardless.\n\n**Fixes are user-side:**\n\n1. **Open the sign URL in incognito\u002Fprivate window** — no localStorage,\n   no cached signature.\n2. **Click the trash\u002Fclear icon in the signature modal** before signing.\n3. **Use the \"Draw\" tab** in the signature modal instead of \"Type\".\n\nWhen you hand a sign URL to a user who has previously typed anything into\na signature field on the same browser, **proactively recommend incognito\nmode** so they don't get the auto-fill surprise.\n\n## When something looks wrong on the signing page\n\nDon't try to PUT-fix a live submission's layout — it won't update. Always:\n\n1. `dscli url check \u003Curl>` — confirms whether it's live or archived.\n2. `dscli url screenshot \u003Curl> --full --out \u002Ftmp\u002Fshot.png` — see what the\n   signer sees.\n3. Adjust template fields with `dscli template set-fields`.\n4. Archive AND recreate the submission with `dscli submission archive`\n   then `dscli submission create`. Critical: the OLD URL becomes a\n   \"deleted\" page in the recipient's inbox — make sure you tell the user\n   to use the NEW URL, not the old email.\n\n## Three instances: CLOUD (default), SELF-HOSTED (`--self`), SEALWORKER (`--seal`)\n\n| | cloud | self-hosted | sealworker |\n|---|---|---|---|\n| flag | *(default)* | `--self` (or `DOCUSEAL_SELF=1`) | `--seal` (or `SEAL_MODE=1` \u002F `DOCUSEAL_SEAL=1`) |\n| base | `https:\u002F\u002Fapi.docuseal.com` | `https:\u002F\u002Fdocuseal.example.com\u002Fapi` | `SEALWORKER_API_BASE` env, else `~\u002F.config\u002Fdocuseal\u002Fseal-base.txt`, else `https:\u002F\u002Fseal.example.com\u002Fapi` |\n| key | `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt` | `~\u002F.config\u002Fdocuseal\u002Fapi-key-selfhosted.txt` | `DOCUSEAL_API_KEY` env or `~\u002F.config\u002Fdocuseal\u002Fapi-key-sealworker.txt` |\n| edition | Pro (SaaS) | **OSS** — some APIs are Pro-gated (below) | sealworker (Workers-native, `~\u002Fsealworker`) — implements the cloud API subset dscli uses, **including `POST \u002Ftemplates\u002Fpdf`** (the OSS Pro-gap and Rails-session workaround do NOT apply in seal mode) |\n| edge | none | **Cloudflare Access** (email allowlist) | none on `\u002Fapi\u002F*` (Access is path-scoped to `\u002Fadmin*` only; if `SEALWORKER_CF_COOKIE` is set, dscli sends it) |\n\n```bash\ndscli --json template list           # cloud\ndscli --self --json template list    # self-hosted\ndscli --seal --json template list    # sealworker\n# local sealworker dev:\nSEALWORKER_API_BASE=http:\u002F\u002Flocalhost:8787\u002Fapi DOCUSEAL_API_KEY=testkey-sealworker-dev \\\n  dscli --seal --json template list\n```\n\n`--seal` needs no cookie plumbing; `template upload` works there (unlike\n`--self`). Signing URLs printed by `submission create`\u002F`submission urls`\nPREFER the server-returned `embed_src` verbatim, falling back to deriving the\nhost from the active API base (`signing_url()`\u002F`sign_origin()` in dscli) —\ncloud still prints `https:\u002F\u002Fdocuseal.com\u002Fs\u002F...` byte-identically, while\n`--self`\u002F`--seal` print their own hosts (this fixed two previously hardcoded\n`docuseal.com\u002Fs\u002F` builders; verified 2026-07-12: `--seal` against wrangler dev\nprints `http:\u002F\u002Flocalhost:8787\u002Fs\u002F\u003Cslug>`). Cloud->sealworker migration + PDF\narchive: `~\u002Ftools\u002Fdocuseal\u002Fmigrate-cloud-to-seal.py` (`templates [--dry-run]`\nand `archive`; cloud strictly read-only; field uuids preserved verbatim;\nidempotent via `external_id \"cloud:\u003Cid>\"`; `--limit N` \u002F `--only ids` for\ntest runs).\n\n`--self` auto-attaches the CF Access `CF_Authorization` cookie by reading the\nlogged-in Chrome profile via `~\u002Ftools\u002Fcookies-txt`. If Access has expired, dscli\ntells you to re-open the site in Chrome and finish the OTP. Two other traps it\nalready handles: CF's Browser Integrity Check **403s (error 1010)** the default\nPython-urllib User-Agent (dscli now sends its own UA), and an expired Access\nsession comes back as a **302 to cloudflareaccess.com**, not a 401.\n\n### Self-hosted is the OSS edition — creating a template from a PDF is Pro-only\n\nVerified live 2026-07-12 against the running instance:\n\n```\nPOST \u002Fapi\u002Ftemplates\u002Fpdf   -> 404 {\"message\":\"This feature is available in Pro Edition\"}\nPOST \u002Fapi\u002Ftemplates\u002Fhtml  -> 404   (same)\nPOST \u002Fapi\u002Ftemplates\u002Fdocx  -> 404   (same)\n```\n\nSo `dscli --self template upload` **cannot work** — that command posts to\n`\u002Ftemplates\u002Fpdf`. But `PUT \u002Fapi\u002Ftemplates\u002F{id}` IS in OSS and permits\n`external_id`, `submitters[]`, and full `fields[]` (areas\u002Fpages\u002Fuuids,\nconditions, options, validation). The working shape is therefore two-legged:\n\n1. **create + attach the PDF** via the Rails web session\n   (`POST \u002Ftemplates_upload`, multipart `files[]`) — exactly what a human does\n   in the UI; and\n2. **set roles + fields** via `PUT \u002Fapi\u002Ftemplates\u002F{id}` with the API token.\n\n`~\u002Ftools\u002Fdocuseal\u002Fmigrate-cloud-to-self.py` implements this (it also signs into\nthe Rails session using the stored admin password) and is the reference for any\nfuture \"put this PDF on the self-hosted box\" automation.\n\n## Configuration\n\n- API key (cloud): `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt`\n- API key (self):  `~\u002F.config\u002Fdocuseal\u002Fapi-key-selfhosted.txt`\n- API key (seal):  `~\u002F.config\u002Fdocuseal\u002Fapi-key-sealworker.txt`\n- Base URL: `https:\u002F\u002Fapi.docuseal.com`; override with `DOCUSEAL_API_BASE`, or\n  pass `--self` \u002F `--seal` (seal base: `SEALWORKER_API_BASE` env, else\n  `~\u002F.config\u002Fdocuseal\u002Fseal-base.txt`, else `https:\u002F\u002Fseal.example.com\u002Fapi`).\n- Self-hosted admin password: `~\u002Fdocuseal-worker\u002F.secrets\u002FDOCUSEAL_ADMIN_PASSWORD`\n- PyMuPDF (`fitz`) required for `pdf` subcommands — installed system-wide.\n- `agent-browser` required for `url screenshot`.\n\n### Self-hosted upload silently failing? It's the R2 checksum trap.\n\nIf a document upload bounces to the dashboard with no error and the template\nends up with **zero documents**, the container is hitting\n`Aws::S3::Errors::InvalidRequest: You can only specify one non-default checksum\nat a time.` — aws-sdk-ruby's default flexible checksums (`x-amz-checksum-crc32`)\ncolliding with Active Storage's `Content-MD5` on R2. DocuSeal rescues the error\nand redirects to root, so nothing surfaces in `wrangler tail` (`outcome: ok`).\nFix is `AWS_REQUEST_CHECKSUM_CALCULATION=when_required` +\n`AWS_RESPONSE_CHECKSUM_VALIDATION=when_required` in the Worker's container env\n(`~\u002Fdocuseal-worker\u002Fsrc\u002Findex.ts`). Full write-up: `~\u002Fdocuseal-worker\u002FDEPLOY.md`.\n\n## Source\n\n- CLI: `$HOME\u002Ftools\u002Fdocuseal\u002Fdscli`\n- Skill: `$HOME\u002F.claude\u002Fskills\u002Fdocuseal-cli\u002FSKILL.md`\n- API key: `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt`\n\n\n## Ground-truth gate (MANDATORY)\n\nBefore this skill asserts a stakes-bearing fact or takes any outward\u002Firreversible action, apply the global standard — verify against a **primary source fetched now**, never a cached\u002Fremembered value. Full standard: `~\u002F.claude\u002Fskills\u002Fshared\u002Fground-truth-standard.md`.\n\n**Verify live before you act or assert (this skill):**\n- Verify signer identity + the exact document before dispatch; explicit approval; capture the submission id.\n\nThen: dry-run where possible, show the user exactly what will be sent\u002Ffiled\u002Fasserted, get explicit chat approval for any outward action (per CLAUDE.md), capture the confirmation, and write any verified fact back into its source doc. State uncertainty as uncertainty; never assert plausible-but-unverified as fact.\n","# DocuSeal CLI (`dscli`)\n\n`dscli` is the agent-friendly DocuSeal client. Located at\n`$HOME\u002Ftools\u002Fdocuseal\u002Fdscli`, symlinked to `~\u002F.local\u002Fbin\u002Fdscli`.\n\nAPI key at `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt` (or `DOCUSEAL_API_KEY` env).\n\n## DO NOT bypass dscli with raw curl\u002FHTTP unless `dscli` lacks the operation\nyou need. The CLI exists because every raw-call path has at least one trap\nthat ate hours on 2026-05-06. Specifically:\n\n1. **`POST \u002Ftemplates\u002Fpdf` silently drops field `area.page`.** Every field\n   you upload with `page=N` ends up at `page=0` regardless. `dscli template\n   upload` therefore creates the template *without* fields; use\n   `dscli template set-fields` to attach fields via PUT, which DOES respect\n   `page` (because the CLI also passes `attachment_uuid` per area).\n\n2. **Submissions cache the template's field layout at create time.** Editing\n   a template after a submission exists DOES NOT update the in-flight\n   submission's signing UI. Always `dscli submission archive` and recreate\n   after changing template fields.\n\n3. **`POST \u002Fsubmissions` with `send_email=true` sends emails IMMEDIATELY.**\n   Archiving the submission afterwards does not recall the email — the\n   recipient's inbox now has a link that 404s with \"This submission has\n   been deleted.\" `dscli submission create` defaults `send_email=false`;\n   you opt in only after verifying field placement via `dscli pdf preview`\n   or `dscli url screenshot`.\n\n4. **`default_value` on a text field renders as static text on the PDF\n   underlay.** It can visually bleed near adjacent fields and confuse\n   signers. Avoid unless really needed; pass user-provided values via the\n   submitter's `values` map at submission create instead.\n\n5. **Match signature field rects to the PDF's signature-line widget rects.**\n   DocuSeal renders an icon-sized \"click to sign\" indicator at the field\n   position; making the rect huge just covers nearby printed labels and\n   makes the user think the box is doing something it isn't. Use\n   `dscli pdf widgets` to extract the form's actual widget rects.\n\n6. **`page` in fields.json is 0-INDEXED — this is the #1 cause of \"signature\n   placed on the wrong page \u002F didn't render.\"** (2026-06-24, root cause found\n   by reading `dscli` line 291 + `cmd_template_set_fields`.) A multi-page\n   records request put its two signature fields on `\"page\": 2` and `\"page\": 4`\n   (thinking 1-indexed = \"the 2nd and 4th printed pages\"). The PDF had 4 pages\n   = valid 0-indexed pages **0,1,2,3**. So `page:2` landed on the 3rd printed\n   page (wrong) and `page:4` **does not exist** → DocuSeal silently dropped\u002F\n   mis-placed it; the signer \"completed\" the form but the signature never\n   rendered on the visible signature line. THE FIX: if the signature line is on\n   the Nth printed page, use `\"page\": N-1`. Locate it programmatically:\n   `for i,page in enumerate(fitz.open(pdf)): page.search_for(\"Signature:\")` —\n   the `i` it prints IS the value to put in `\"page\"`.\n   **ALWAYS pass `--pdf \u003Cfile>` to `set-fields`** — with `--pdf`, dscli calls\n   `pdf_page_size(pdf, page)` which raises `IndexError: page N not in document`\n   on an out-of-range index, turning this silent bug into a loud error. Without\n   `--pdf` it falls back to 612×792 and places the field on a phantom page.\n   (Treat any `IndexError: page N not in document` from set-fields as \"your\n   page number is too high by one\" — do NOT work around it by dropping `--pdf`.)\n\n   Secondary: keep signature rects ≥ 40pt tall and ≥ 250pt wide on a clearly-\n   labeled \"Signature:\" block (a too-short rect can clip the rendered image),\n   but the page index is the thing that bit hardest here.\n\n7. **ALWAYS verify the SIGNED PDF, not just `status: completed`.** A\n   submission can report `completed` with every field value populated\n   server-side while one or more signatures fail to render on the page.\n   After any signer finishes, download the signed document\n   (`dscli --json submission get \u003CSID>` → `.documents[].url` → curl it)\n   and rasterize EVERY signature page (`fitz` → `get_pixmap` → Read the\n   PNG) to confirm each signature + date is actually visible at its\n   field. `status: completed` is NOT proof the signatures rendered — the\n   pixels are. Especially critical for multi-page \u002F multi-signature docs.\n\n8. **Unembedded fonts silently destroy the document downstream — `template upload`\n   now BLOCKS on them** (added 2026-07-24). A PDF whose fonts aren't embedded is\n   accepted by DocuSeal and looks fine on screen, then fails at the mail vendor:\n   **Lob** — now the ONLY mail vendor (PostGrid removed 2026-08-12) — rejects it\n   outright with `HTTP 422 unembedded_fonts`, so an unembedded font is a HARD STOP\n   on the send, not a cosmetic warning. (The historical alternative was worse and\n   is why this gate exists: PostGrid accepted the same file silently and\n   *rasterized* it — a 4 MB upload became a **137 MB** print artifact that stalled\n   at `status: printing` for 81 days with `errorMessage: null`.)\n   `dscli template upload` runs `pdffonts` first and refuses to upload, printing the\n   exact remedy. Use `--embed-fonts` to auto-fix via ghostscript (also shrank a real\n   87-page packet 4.0 MB → 2.8 MB), or `--allow-unembedded` to override.\n   **Also re-embed AFTER signing** — DocuSeal re-renders its own output, so the\n   signed PDF must be checked again before it goes to any print\u002Fmail vendor:\n   `pdffonts signed.pdf | awk 'NR>2 && $(NF-3)==\"no\"'` must be empty.\n   Reference incident: Sanders ABCMR filing, 63 unembedded fonts across 125 total.\n\n## Commands at a glance\n\n```\ndscli --help                                      # full reference\ndscli [--json] template upload \u003Cpdf> [--name X]   # upload, no fields yet\ndscli [--json] template add-roles \u003Cid> \"R1,R2\"    # add submitter roles\ndscli [--json] template set-fields \u003Cid> \u003Cjson> [--pdf \u003Cpdf>]\n                                                  # PUT fields (correct path)\ndscli [--json] template get \u003Cid> [--fields-only]\ndscli [--json] template list\ndscli [--json] template delete \u003Cid> --force       # archives subs first\ndscli [--json] template archive-subs \u003Cid>\n\ndscli [--json] submission create \u003Ctid> \u003Cjson>\n       [--send-email] [--order preserved] [--subject X --body Y]\ndscli [--json] submission get \u003Cid>\ndscli [--json] submission list [--template-id N]\ndscli [--json] submission archive \u003Cid>\ndscli [--json] submission urls \u003Cid>               # role | name | status | URL\n\ndscli [--json] pdf widgets \u003Cpdf>                  # PDF AcroForm fields\ndscli [--json] pdf prefill \u003Cpdf> \u003Cout> \u003Cvalues.json> [--checkboxes-json '...']\ndscli [--json] pdf preview \u003Cpdf> --out preview.pdf --template-id \u003Cid>\n                                                  # Overlay rects on PDF\n                                                  # for visual verification\n\ndscli [--json] url check \u003Curl>                    # live? archived? title\ndscli [--json] url screenshot \u003Curl> [--out X --full]   # via agent-browser\n```\n\n`--json` is a GLOBAL flag (must come before the subcommand).\n\n## Standard end-to-end flow\n\n```bash\n# 1. Pre-fill any data fields on the source PDF (subject info, recipient,\n#    reason text, checkboxes). Bake so DocuSeal sees a static document.\ndscli pdf widgets form.pdf > \u002Ftmp\u002Fwidgets.json   # discover field names\necho '{\"FullName-FLD\": \"Jane Doe\", ...}' > \u002Ftmp\u002Fvalues.json\ndscli pdf prefill form.pdf \u002Ftmp\u002Fprefilled.pdf \u002Ftmp\u002Fvalues.json \\\n      --checkboxes-json '[\"Box1\",\"Box2\"]'\n\n# 2. Upload the prefilled PDF as a template (no fields yet).\nTID=$(dscli --json template upload \u002Ftmp\u002Fprefilled.pdf --name \"Form X\" \\\n        | jq -r .id)\n\n# 3. Add the signing roles you need. Names become role IDs in submissions.\ndscli template add-roles \"$TID\" \"Witness 1,Subject,Witness 2\"\n\n# 4. Place signature\u002Ftext\u002Fdate\u002Fcheckbox fields. fields.json schema:\n#    [\n#      {\"name\":\"W1 Sig\", \"type\":\"signature\", \"role\":\"Witness 1\",\n#       \"rect\":[21,707,303,717], \"page\":1, \"required\":true},\n#      {\"name\":\"W1 Addr\", \"type\":\"text\", \"role\":\"Witness 1\",\n#       \"rect\":[21,735,303,771], \"page\":1, \"required\":true},\n#      ...\n#    ]\n#    Rect is PDF points (top-left origin). Pass --pdf so exact page dims\n#    are used (avoids assuming 612×792).\ndscli template set-fields \"$TID\" fields.json --pdf \u002Ftmp\u002Fprefilled.pdf\n\n# 5. VISUALLY VERIFY before sending. Render a preview with rects overlaid.\ndscli pdf preview \u002Ftmp\u002Fprefilled.pdf --template-id \"$TID\" \\\n      --out \u002Ftmp\u002Fpreview.pdf\n# Open \u002Ftmp\u002Fpreview.pdf in Preview.app; confirm rects sit where signers\n# will actually need to sign \u002F type.\n\n# 6. Create the submission. send_email=false by default — you control how\n#    URLs are shared.\ncat > \u002Ftmp\u002Fsubmitters.json \u003C\u003CEOF\n[\n  {\"role\":\"Witness 1\",\"email\":\"a@x.com\",\"name\":\"Alice\"},\n  {\"role\":\"Subject\",  \"email\":\"b@x.com\",\"name\":\"Bob\"},\n  {\"role\":\"Witness 2\",\"email\":\"c@x.com\",\"name\":\"Carol\"}\n]\nEOF\ndscli --json submission create \"$TID\" \u002Ftmp\u002Fsubmitters.json \\\n      --order preserved > \u002Ftmp\u002Fsub.json\nSID=$(jq -r .submission_id \u002Ftmp\u002Fsub.json)\n\n# 7. Surface URLs to the user (or trigger DocuSeal email by recreating\n#    with --send-email once you're confident).\ndscli submission urls \"$SID\"\n\n# 8. After signers complete: pull the signed PDF.\ndscli --json submission get \"$SID\" | jq '.documents'\n```\n\n## CRITICAL: every field needs a `uuid` attribute\n\nDocuSeal's signing frontend uses `\u003Cinput name=\"values[\u003Cfield.uuid>]\">` to\ncollect each field's value. If a field has no `uuid` attribute, `field.uuid`\nis JavaScript-undefined and the input becomes `name=\"values[undefined]\"`.\nALL fields without a uuid then share the SAME form slot — typing in any\none of them overwrites the others. The \"type a sig and the address\nappears in both\" bug is purely a manifestation of this.\n\n`dscli template set-fields` auto-generates a UUIDv4 per field if you\ndon't supply one. Don't bypass it. If you ever PUT fields directly via\nHTTP, include a unique `uuid` per field or expect cross-field overwrites.\n\nVerified 2026-05-08 via chrome-cdp: with `uuid` per field, the live form's\nhidden inputs are `values[\u003Csig_uuid>]` and `values[\u003Caddr_uuid>]` — separate.\nWithout uuid, both collapse to `values[undefined]`.\n\n## \"Type text\" signature mode contaminates next text field (frontend bug)\n\nWhen a submitter clicks the signature field, picks **\"Type text\"** mode,\ntypes their name (or any text), and clicks NEXT, DocuSeal does two things:\n\n1. Stores the typed cursive as a signature image attachment (correct).\n2. **Writes the image's attachment UUID into the local state of the\n   next text field for that submitter** (BUG).\n\nThe text field then renders something like\n`77866bd2-fe60-4c80-9533-e0f6ccff8e66` until the user manually clears it.\nIf the submitter has a cached prior value (e.g., they typed their address\ninto a sig field on an earlier attempt), the cached value renders instead.\n\nThe server-side `submitter.values` stays `[]` — this leak is purely\nclient-side. The REST API does NOT expose `with_typed_signature` at any\nlevel; verified that template, submission, and submitter PUTs with every\nplausible shape silently no-op. The rendered HTML always has\n`data-with-typed-signature=\"true\"`.\n\n**Workarounds:**\n- Tell submitters to use **\"Sign on the touchscreen\"** (Draw) or **Upload**,\n  never \"Type text\".\n- Make signature field rects ≥ 30pt tall. The PDF widget rect for a\n  signature LINE is typically ~10pt; reusing that rect causes the typed\n  cursive image to render at natural size and visually overflow into the\n  field below, looking like a duplicated value even before the actual\n  bug fires.\n\n## Browser-side autofill trap (`data-reuse-signature`)\n\nThe signing page renders with `data-reuse-signature=\"true\"` hardcoded by\nDocuSeal's UI — not exposed via the public REST API. Once a user has typed\n*anything* into a signature field on this account\u002Fbrowser before, DocuSeal\ncaches it in browser localStorage as their \"preferred signature\" and\nauto-suggests it on every new submission, even on freshly-created\nsubmissions with `default_value=\"\"` on all fields. The cached string can\nalso bleed into adjacent text fields.\n\n**This is NOT fixable via the API.** Verified: `POST \u002Fsubmissions\n{reuse_signature: false}`, `PUT \u002Ftemplates\u002F{id} {preferences: {...}}`, and\nevery other shape silently no-op. The rendered HTML still has\n`data-reuse-signature=\"true\"` regardless.\n\n**Fixes are user-side:**\n\n1. **Open the sign URL in incognito\u002Fprivate window** — no localStorage,\n   no cached signature.\n2. **Click the trash\u002Fclear icon in the signature modal** before signing.\n3. **Use the \"Draw\" tab** in the signature modal instead of \"Type\".\n\nWhen you hand a sign URL to a user who has previously typed anything into\na signature field on the same browser, **proactively recommend incognito\nmode** so they don't get the auto-fill surprise.\n\n## When something looks wrong on the signing page\n\nDon't try to PUT-fix a live submission's layout — it won't update. Always:\n\n1. `dscli url check \u003Curl>` — confirms whether it's live or archived.\n2. `dscli url screenshot \u003Curl> --full --out \u002Ftmp\u002Fshot.png` — see what the\n   signer sees.\n3. Adjust template fields with `dscli template set-fields`.\n4. Archive AND recreate the submission with `dscli submission archive`\n   then `dscli submission create`. Critical: the OLD URL becomes a\n   \"deleted\" page in the recipient's inbox — make sure you tell the user\n   to use the NEW URL, not the old email.\n\n## Three instances: CLOUD (default), SELF-HOSTED (`--self`), SEALWORKER (`--seal`)\n\n| | cloud | self-hosted | sealworker |\n|---|---|---|---|\n| flag | *(default)* | `--self` (or `DOCUSEAL_SELF=1`) | `--seal` (or `SEAL_MODE=1` \u002F `DOCUSEAL_SEAL=1`) |\n| base | `https:\u002F\u002Fapi.docuseal.com` | `https:\u002F\u002Fdocuseal.example.com\u002Fapi` | `SEALWORKER_API_BASE` env, else `~\u002F.config\u002Fdocuseal\u002Fseal-base.txt`, else `https:\u002F\u002Fseal.example.com\u002Fapi` |\n| key | `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt` | `~\u002F.config\u002Fdocuseal\u002Fapi-key-selfhosted.txt` | `DOCUSEAL_API_KEY` env or `~\u002F.config\u002Fdocuseal\u002Fapi-key-sealworker.txt` |\n| edition | Pro (SaaS) | **OSS** — some APIs are Pro-gated (below) | sealworker (Workers-native, `~\u002Fsealworker`) — implements the cloud API subset dscli uses, **including `POST \u002Ftemplates\u002Fpdf`** (the OSS Pro-gap and Rails-session workaround do NOT apply in seal mode) |\n| edge | none | **Cloudflare Access** (email allowlist) | none on `\u002Fapi\u002F*` (Access is path-scoped to `\u002Fadmin*` only; if `SEALWORKER_CF_COOKIE` is set, dscli sends it) |\n\n```bash\ndscli --json template list           # cloud\ndscli --self --json template list    # self-hosted\ndscli --seal --json template list    # sealworker\n# local sealworker dev:\nSEALWORKER_API_BASE=http:\u002F\u002Flocalhost:8787\u002Fapi DOCUSEAL_API_KEY=testkey-sealworker-dev \\\n  dscli --seal --json template list\n```\n\n`--seal` needs no cookie plumbing; `template upload` works there (unlike\n`--self`). Signing URLs printed by `submission create`\u002F`submission urls`\nPREFER the server-returned `embed_src` verbatim, falling back to deriving the\nhost from the active API base (`signing_url()`\u002F`sign_origin()` in dscli) —\ncloud still prints `https:\u002F\u002Fdocuseal.com\u002Fs\u002F...` byte-identically, while\n`--self`\u002F`--seal` print their own hosts (this fixed two previously hardcoded\n`docuseal.com\u002Fs\u002F` builders; verified 2026-07-12: `--seal` against wrangler dev\nprints `http:\u002F\u002Flocalhost:8787\u002Fs\u002F\u003Cslug>`). Cloud->sealworker migration + PDF\narchive: `~\u002Ftools\u002Fdocuseal\u002Fmigrate-cloud-to-seal.py` (`templates [--dry-run]`\nand `archive`; cloud strictly read-only; field uuids preserved verbatim;\nidempotent via `external_id \"cloud:\u003Cid>\"`; `--limit N` \u002F `--only ids` for\ntest runs).\n\n`--self` auto-attaches the CF Access `CF_Authorization` cookie by reading the\nlogged-in Chrome profile via `~\u002Ftools\u002Fcookies-txt`. If Access has expired, dscli\ntells you to re-open the site in Chrome and finish the OTP. Two other traps it\nalready handles: CF's Browser Integrity Check **403s (error 1010)** the default\nPython-urllib User-Agent (dscli now sends its own UA), and an expired Access\nsession comes back as a **302 to cloudflareaccess.com**, not a 401.\n\n### Self-hosted is the OSS edition — creating a template from a PDF is Pro-only\n\nVerified live 2026-07-12 against the running instance:\n\n```\nPOST \u002Fapi\u002Ftemplates\u002Fpdf   -> 404 {\"message\":\"This feature is available in Pro Edition\"}\nPOST \u002Fapi\u002Ftemplates\u002Fhtml  -> 404   (same)\nPOST \u002Fapi\u002Ftemplates\u002Fdocx  -> 404   (same)\n```\n\nSo `dscli --self template upload` **cannot work** — that command posts to\n`\u002Ftemplates\u002Fpdf`. But `PUT \u002Fapi\u002Ftemplates\u002F{id}` IS in OSS and permits\n`external_id`, `submitters[]`, and full `fields[]` (areas\u002Fpages\u002Fuuids,\nconditions, options, validation). The working shape is therefore two-legged:\n\n1. **create + attach the PDF** via the Rails web session\n   (`POST \u002Ftemplates_upload`, multipart `files[]`) — exactly what a human does\n   in the UI; and\n2. **set roles + fields** via `PUT \u002Fapi\u002Ftemplates\u002F{id}` with the API token.\n\n`~\u002Ftools\u002Fdocuseal\u002Fmigrate-cloud-to-self.py` implements this (it also signs into\nthe Rails session using the stored admin password) and is the reference for any\nfuture \"put this PDF on the self-hosted box\" automation.\n\n## Configuration\n\n- API key (cloud): `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt`\n- API key (self):  `~\u002F.config\u002Fdocuseal\u002Fapi-key-selfhosted.txt`\n- API key (seal):  `~\u002F.config\u002Fdocuseal\u002Fapi-key-sealworker.txt`\n- Base URL: `https:\u002F\u002Fapi.docuseal.com`; override with `DOCUSEAL_API_BASE`, or\n  pass `--self` \u002F `--seal` (seal base: `SEALWORKER_API_BASE` env, else\n  `~\u002F.config\u002Fdocuseal\u002Fseal-base.txt`, else `https:\u002F\u002Fseal.example.com\u002Fapi`).\n- Self-hosted admin password: `~\u002Fdocuseal-worker\u002F.secrets\u002FDOCUSEAL_ADMIN_PASSWORD`\n- PyMuPDF (`fitz`) required for `pdf` subcommands — installed system-wide.\n- `agent-browser` required for `url screenshot`.\n\n### Self-hosted upload silently failing? It's the R2 checksum trap.\n\nIf a document upload bounces to the dashboard with no error and the template\nends up with **zero documents**, the container is hitting\n`Aws::S3::Errors::InvalidRequest: You can only specify one non-default checksum\nat a time.` — aws-sdk-ruby's default flexible checksums (`x-amz-checksum-crc32`)\ncolliding with Active Storage's `Content-MD5` on R2. DocuSeal rescues the error\nand redirects to root, so nothing surfaces in `wrangler tail` (`outcome: ok`).\nFix is `AWS_REQUEST_CHECKSUM_CALCULATION=when_required` +\n`AWS_RESPONSE_CHECKSUM_VALIDATION=when_required` in the Worker's container env\n(`~\u002Fdocuseal-worker\u002Fsrc\u002Findex.ts`). Full write-up: `~\u002Fdocuseal-worker\u002FDEPLOY.md`.\n\n## Source\n\n- CLI: `$HOME\u002Ftools\u002Fdocuseal\u002Fdscli`\n- Skill: `$HOME\u002F.claude\u002Fskills\u002Fdocuseal-cli\u002FSKILL.md`\n- API key: `~\u002F.config\u002Fdocuseal\u002Fapi-key.txt`\n\n\n## Ground-truth gate (MANDATORY)\n\nBefore this skill asserts a stakes-bearing fact or takes any outward\u002Firreversible action, apply the global standard — verify against a **primary source fetched now**, never a cached\u002Fremembered value. Full standard: `~\u002F.claude\u002Fskills\u002Fshared\u002Fground-truth-standard.md`.\n\n**Verify live before you act or assert (this skill):**\n- Verify signer identity + the exact document before dispatch; explicit approval; capture the submission id.\n\nThen: dry-run where possible, show the user exactly what will be sent\u002Ffiled\u002Fasserted, get explicit chat approval for any outward action (per CLAUDE.md), capture the confirmation, and write any verified fact back into its source doc. State uncertainty as uncertainty; never assert plausible-but-unverified as fact.\n",{"name":5,"description":7},"main","e7b39d448c7d905feed2b044d3ccdf60822596ab","skills\u002Fdocuseal-cli",0,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter","https:\u002F\u002Fgithub.com\u002Fbarkleesanders","barkleesanders.com","Stay Hungry, Stay Foolish","2026-11-06 08:47:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add barkleesanders\u002Fclaude-code-starter --skill docuseal-cli",{"tool":39,"command":40},"bunx","bunx skills add barkleesanders\u002Fclaude-code-starter --skill docuseal-cli",{"tool":42,"command":43},"pnpm","pnpm dlx skills add barkleesanders\u002Fclaude-code-starter --skill docuseal-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdocuseal-cli\u002FSKILL.md",true,[],[48,54,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AWV75B37B6YKG7ZKGZ783F","zi-search","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fzi-search\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AWTZA3JGK1T7V1HS543FG7","visualise","Render inline interactive visuals — SVG diagrams, HTML widgets, charts, and explainers — directly in the conversation. Use this skill whenever the user asks to visualize, diagram, chart, illustrate, or explain something visually, or when an explanation would genuinely benefit from a spatial\u002Finteractive diagram rather than text. Also triggers for: flowcharts, architecture diagrams, data visualizations, interactive explainers, comparison layouts, UI mockups, and any request containing 'show me', 'draw', 'map out', 'visualize', or 'diagram'. Even when the user doesn't explicitly ask for a visual, use this skill proactively when the topic has spatial, sequential, or systemic relationships that a diagram would clarify better than prose.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvisualise\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AWTR056C3P9R3VS8YVM2WX","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AWTHTWBMTYZPMHHEYX3TTG","manim-video","Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric\u002Fmathematical content.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002Fskills\u002Fmanim-video\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AWTCXDJ9NWFQW51ENM8A2Z","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AWTA1D5FP895S33GHSA2G5","ui-improver","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fui-improver\u002FSKILL.md",[],[]]