Skill Tracer
Skills › Knowledge Work Plugins › signature-request

signature-request

skill · 104 lines · Apache-2.0 · legal/skills/signature-request/SKILL.md

The facts

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

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent would reach for this when a contract or legal document is finalized and the next step is getting it signed — someone wants a document checked over, signers lined up, and an e-signature envelope sent. The description's emphasis on pre-signature checks, entity names, exhibits, and sequential/parallel signing order is what sets it apart from drafting or review skills.

Things a person might say (the model's guesses)

  • “The Acme MSA is final — send it out for signature to both parties”
  • “Set up the signing order for this NDA, our CFO signs before theirs”
  • “Can you run a pre-signature checklist on this contract before I send it?”

A model's summary of when it is used.

A model's reading

What it takes when started

<document or contract to send>

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from legal/LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: signature-request
3description: 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.
4argument-hint: "<document or contract to send>"
5---
6
7# /signature-request -- E-Signature Routing
8
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Prepare a document for electronic signature — verify completeness, set signing order, and route for execution.
13**Important**: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.

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

Raw lines 1 to 14
15## Usage
17```
18/signature-request $ARGUMENTS
19```
21Prepare for signature: @$1

Usage

/signature-request $ARGUMENTS

Prepare for signature: @$1

Raw lines 15 to 22
23## Workflow

Workflow

Raw lines 23 to 24
25### Step 1: Accept the Document
27Accept the document in any format:
28- **File upload**: PDF, DOCX
29- **URL**: Link to a document in ~~cloud storage or ~~CLM
30- **Reference**: "The Acme Corp MSA we finalized yesterday"

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"
Raw lines 25 to 31
Uses an outside tool ~~cloud :29
32### Step 2: Pre-Signature Checklist
34Before routing for signature, verify:
36```markdown
37## Pre-Signature Checklist
39- [ ] Document is in final, agreed form (no open redlines)
40- [ ] All exhibits and schedules are attached
41- [ ] Correct legal entity names on signature blocks
42- [ ] Dates are correct or left blank for execution date
43- [ ] Signature blocks match the authorized signers
44- [ ] Any required internal approvals have been obtained
45- [ ] Document has been reviewed by appropriate counsel
46```

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
Raw lines 32 to 47
48### Step 3: Configure Signing
50Gather signing details:
51- **Signers**: Who needs to sign? (names, emails, titles)
52- **Signing order**: Sequential or parallel?
53- **Internal approval**: Does anyone need to approve before the counterparty signs?
54- **CC recipients**: Who should receive a copy of the executed document?

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?
Raw lines 48 to 55
56### Step 4: Route for Signature
58**If ~~e-signature is connected:**
59- Create the signature envelope/request
60- Set signing fields and order
61- Add any required initials or date fields
62- Send for signature
64**If not connected:**
65- Generate a signing instruction document
66- Provide the document formatted for wet signature or manual e-sign
67- List all signers with contact information

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
Raw lines 56 to 68
Uses an outside tool ~~e-signature :58
69## Output
71```markdown
72## Signature Request: [Document Title]
74### Document Details
75- **Type**: [MSA / NDA / SOW / Amendment / etc.]
76- **Parties**: [Party A] and [Party B]
77- **Pages**: [X]
79### Pre-Signature Check: [PASS / ISSUES FOUND]
80[List any issues that need attention before sending]
82### Signing Configuration
83| Order | Signer | Email | Role |
84|-------|--------|-------|------|
85| 1 | [Name] | [email] | [Party A Authorized Signatory] |
86| 2 | [Name] | [email] | [Party B Authorized Signatory] |
88### CC Recipients
89- [Name] — [email]
91### Status
92[Sent for signature / Ready to send / Issues to resolve first]
94### Next Steps
95- [What to expect after sending]
96- [Expected turnaround time]
97- [Follow-up if not signed within X days]
98```

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]
Raw lines 69 to 99
100## Tips
1021. **Check entity names carefully** — The most common signing error is incorrect legal entity names.
1032. **Verify authority** — Make sure each signer is authorized to bind their organization.
1043. **Keep a copy** — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.

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.
Raw lines 100 to 104
Uses an outside tool ~~cloud :104

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.