Signature Request

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

AI-generated overview

Prepares a finalized document for e-signature by running a pre-signature checklist, configuring signers, and routing it for execution.

What it does
This skill walks through preparing a document for electronic signature: accepting the document, running a pre-signature checklist covering final form, exhibits, entity names, dates, signature blocks and approvals, and gathering signer details. It then configures signing order (sequential or parallel), internal approvals and CC recipients, and either creates a signature envelope when an e-signature tool is connected or produces a signing instruction document for wet or manual e-signature. It outputs a structured signature request summary with document details, checklist status, a signer table, CC recipients, status and next steps.
When to use it
Use it 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.
Requirements
Instructions only; no scripts are shipped. It works with a document supplied as a file upload (PDF, DOCX), a URL, or a reference. Routing for signature requires a connected e-signature tool; without one it falls back to generating a signing instruction document. It references external connector documentation and cloud storage or CLM systems.

/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

/signature-request $ARGUMENTS

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:

markdown
## Pre-Signature Checklist
- [ ] Document is in final, agreed form (no open redlines)- [ ] All exhibits and schedules are attached- [ ] Correct legal entity names on signature blocks- [ ] Dates are correct or left blank for execution date- [ ] Signature blocks match the authorized signers- [ ] Any required internal approvals have been obtained- [ ] Document has been reviewed by appropriate counsel

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

markdown
## Signature Request: [Document Title]
### Document Details- **Type**: [MSA / NDA / SOW / Amendment / etc.]- **Parties**: [Party A] and [Party B]- **Pages**: [X]
### Pre-Signature Check: [PASS / ISSUES FOUND][List any issues that need attention before sending]
### Signing Configuration| Order | Signer | Email | Role ||-------|--------|-------|------|| 1 | [Name] | [email] | [Party A Authorized Signatory] || 2 | [Name] | [email] | [Party B Authorized Signatory] |
### CC Recipients- [Name] — [email]
### Status[Sent for signature / Ready to send / Issues to resolve first]
### Next Steps- [What to expect after sending]- [Expected turnaround time]- [Follow-up if not signed within X days]

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.

Source and attribution

Source:anthropics/knowledge-work-pluginsinlegal/skills/signature-requestat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today