Agent skill · operations · anthropics
signature-request
Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.
Why this skill is useful
Adds a structured workflow for preparing and routing documents for e-signature that includes a pre-signature checklist and signing configuration details.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
/signature-request -- E-Signature Routing If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Prepare a document for electronic signature — verify completeness, set signing order, and route for execution. Important: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature. Usage Prepare for signature: @$1 Workflow Step 1: Accept the Document Accept the document in any format: File upload: PDF, DOCX URL: Link to a document in ~~cloud storage or ~~CLM Reference: "The Acme Corp MSA we finalized yesterday" Step 2: Pre-Signature Checklist Before routing for signature, verify: Step 3: Configure Signing Gather signing details: Signers: Who needs to sign? (names, emails, titles) Signing order: Sequential or parallel? Internal approval: Does anyone need to approve before the counterparty signs? CC recipients: Who should receive a copy of the executed document? Step 4: Route for Signature If ~~e-signature is connected: Create the signature envelope/request Set signing fields and order Add any required initials or date fields Send for signature If not connected: Generate a signing instruction document Provide the document formatted for wet signature or manual e-sign List all signers with contact information Output Tips 1. Check entity names carefully — The most common signing error is incorrect legal entity names. 2. Verify authority — Make sure each signer is authorized to bind their organization. 3. Keep a copy — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/signature-request