Signature Request
Run a pre-signature checklist and route finalized contracts for e-sign with correct entities, exhibits, and signing order.
Overview
Signature-request is an agent skill for the Operate phase that runs a pre-signature checklist and routes finalized documents for e-signature with configured signing order.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill signature-requestWhat is this skill?
- Pre-signature checklist: final form, exhibits, entity names, dates, signature blocks
- Accepts PDF/DOCX uploads, URLs, or natural-language contract references
- Configure sequential vs parallel signing order before sending the envelope
- Explicit guardrail: assist workflows only—verify final form; not legal advice
- Integrates with cloud storage / CLM connectors per CONNECTORS.md
Adoption & trust: 1.4k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a agreed contract PDF but keep catching wrong entity names, missing exhibits, or signing-order mistakes after you hit send.
Who is it for?
Founders sending MSAs, SOWs, or vendor contracts through DocuSign-style flows after terms are locked.
Skip if: Drafting or negotiating contract language, tax advice, or jurisdictions where you need a lawyer to approve substance before any e-sign tool.
When should I use this skill?
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.
What do I get? / Deliverables
You get a completed checklist and a routed envelope with sequential or parallel signers instead of a recalled or disputed execution package.
- Completed pre-signature checklist
- Configured signing order and send/routing instructions for the envelope
Recommended Skills
Journey fit
Contract execution sits in day-to-day business ops after product and deal terms are settled—not in build or launch tooling. Iterate covers closing operational loops (send, track, execute agreements) once legal text is final.
How it compares
Use instead of manually eyeballing PDFs in chat when you want a repeatable checklist before your e-sign provider sends the envelope.
Common Questions / FAQ
Who is signature-request for?
Solo builders and small teams who finalize B2B or vendor contracts and need a consistent pre-send review before e-signature—without a dedicated legal ops role.
When should I use signature-request?
Use it when a contract is in final agreed form, before you configure signers in your e-sign tool, or when you need to verify exhibits, entities, and signature blocks on an envelope.
Is signature-request safe to install?
Treat it as workflow assistance only, not legal advice. Review the Security Audits panel on this Prism page and restrict connector access to documents you intend to sign.
SKILL.md
READMESKILL.md - Signature Request
# /signature-request -- E-Signature Routing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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.