Skill

Official

Pass

Audit score 90

signature-request

anthropics/knowledge-work-plugins

Prepare and route documents for e-signature with pre-flight checks and signing order configuration.

What is signature-request?

Prepares a finalized contract for electronic signature by running a pre-signature checklist, configuring signers and signing order, and routing for execution. Use this when a contract is ready to sign and you need to verify completeness, set up sequential or parallel signers, and send the envelope.

Run pre-signature checklist to verify document completeness, entity names, and signature blocks
Configure signing order (sequential or parallel) and identify authorized signers
Gather signer details including names, emails, and titles
Set up CC recipients for the executed document
Generate signing instructions or create signature envelope if e-signature is connected

How to install signature-request

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill signature-request

Claude Code

Cursor

Windsurf

Cline

How to use signature-request

1.Provide the document (file upload, URL, or reference to a finalized contract)
2.Review and complete the pre-signature checklist to verify no open redlines, correct entity names, and proper approvals
3.Gather signer information: names, emails, titles, and roles for each party
4.Specify signing order (sequential or parallel) and any internal approval requirements
5.Confirm CC recipients who should receive the executed document
6.Submit for signature routing

Use cases

Good for

Verify an MSA is in final form before sending to counterparty for signature
Set up a multi-party NDA with sequential signing order (internal approval first, then external)
Route an SOW with parallel signers from two organizations
Check that exhibits and schedules are attached before sending for execution
Prepare an amendment with correct legal entity names and authorized signatory information

Who it's for

Contract managers
Legal operations professionals
Business development teams
Anyone managing document execution workflows

signature-request FAQ

What if the document isn't in final form?

The pre-signature checklist will flag issues like open redlines or missing exhibits. Resolve these before routing for signature.

Can I set up internal approval before the counterparty signs?

Yes. Specify internal approvers in the signing configuration, and they will sign before external parties receive the envelope.

What happens if e-signature is not connected?

The skill generates a signing instruction document with signer details and formats the document for wet signature or manual e-sign.

How do I ensure the correct person signs?

Verify each signer's name, email, and title match the authorized signatory for their organization. The pre-signature checklist includes this verification step.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.

name: signature-request description: 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. argument-hint: "<document or contract to send>"

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