$ ~/registry/skill/anthropics-legal-skills-signature-request

SKILL

signature-request

Name: signature-request
Author: anthropics

Prepare documents for e-signature with checks, signer routing, and sending.

Stars

★ 22,528

Source

GitHub

Updated

2026-07-11

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 22.5k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "signature-request" skill from askskill:
1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/legal/skills/signature-request/SKILL.md
2. Save it as ~/.claude/skills/signature-request/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Send a finalized contract for signature

Prompt

Run a pre-signature check for this finalized client contract: verify legal entity names, exhibit list, signing date, and signature blocks; set signing order so our company signs first and the client signs second, then generate sending instructions.

Expected

A pre-signature checklist result plus brief instructions for sequential routing and sending.

Set up parallel signing for multiple signers

Prompt

This partnership agreement requires two representatives from each side to sign. Check whether the signature pages cover all signers, set all four signers to sign in parallel, and provide a recommended routing plan with pre-send notes.

Expected

A parallel signing configuration recommendation with signer coverage checks and pre-send notes.

Verify exhibits and signature blocks

Prompt

Review this agreement before signature and verify company names, exhibit numbers, exhibit titles, and signature blocks for completeness and consistency; if anything is missing, list the issues and suggest fixes without sending it yet.

Expected

An issue list and correction suggestions to complete final review before sending.

// docs

/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:

## 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

## 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

Check entity names carefully — The most common signing error is incorrect legal entity names.
Verify authority — Make sure each signer is authorized to bind their organization.
Keep a copy — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.