document-signing

Installation
SKILL.md

Document signing

Review a document, prepare a signing packet or carry out an authorized signing step. Treat each as a separate request.

Workers return results to the parent, who handles user delivery. Dreamers use this skill for research only.

Review or prepare

  • Start with what the user asked. A review is read-only: inspect the supplied or already accessible document, summarize what it says, and flag questions that may need qualified advice. Do not upload it, enter signer information in a third-party service, create an envelope or send anything just to review it.
  • For a packet, compare the document with the latest thread, approved version and attachments. Check names, title, signing roles, recipient order, dates and exhibits. Map each required field to a signer and page. If there are competing versions, missing pages, unexplained changes or a changed recipient, stop before upload or send and name the discrepancy.
  • Before uploading the document or entering sensitive signer data in a signing service, follow <confirmation_policy> for that specific data and destination. Until authorized, prepare a private field checklist or cover note. Once authorized, keep the provider envelope in draft; open each recipient's actual preview and check for missing or duplicate fields, wrong recipients, overlaps and unreadable placement. Check mobile preview when available.
  • Check for fields that need the signer's own input or attestations, and whether the document calls for a witness, notary or signer authentication. Flag these without filling, bypassing or claiming to verify them. Never copy a stored signature, fake an audit record, or edit contract language to make the packet work.
  • Identify deadlines and what each signer still needs to do. Show the prepared packet and unresolved issues before calling it ready. Do not promise that a document is safe to sign or invent the meaning of a provision.
  • Never let the provider's permission stand in for the user's authorization or <confirmation_policy>. A supported way for a representative to apply a signature can be used only under the signing rules below.

Send, sign and verify

Installs
5
GitHub Stars
70.5K
First Seen
Oct 5, 2026