AutoGineer
Generated banner for Signature Request
Generated logo for Signature Request

Signature Request

AnthropicOfficialPublished by Anthropic

  • Skill
  • Workflow
  • Business and productivity
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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 by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The signature-request skill provides a standardized procedure for finalizing documents and routing them for electronic signature. It guides users through a mandatory pre-signature checklist to ensure document integrity, verifies signer details, and configures the signing order. The skill supports both automated routing via connected e-signature services and manual preparation for wet signatures, ensuring that all legal requirements and internal approvals are addressed before execution.

What it does

  • Performs a pre-signature checklist to verify document completeness and accuracy.
  • Configures signing order for sequential or parallel execution.
  • Identifies authorized signers and CC recipients for the envelope.
  • Routes documents for signature via connected services.
  • Generates manual signing instructions if no e-signature service is connected.
  • Produces a summary report of the signing configuration and status.

When to use it

  • When a contract or document is finalized and ready for execution.
  • When you need to verify entity names, exhibits, and signature blocks before sending.
  • When setting up complex signing workflows involving multiple parties.
  • When you need to ensure all internal approvals are documented before routing.

Advantages

  • Reduces errors by enforcing a standardized pre-signature checklist.
  • Clarifies signing roles and order to prevent routing mistakes.
  • Provides a clear audit trail of the signing configuration.
  • Supports both digital and manual signature workflows.

Usage examples

“Prepare the Acme Corp MSA for signature.”
The agent initiates the pre-signature checklist, asks for signer details, and prepares the document for routing.
“Set up a signature request for the NDA with sequential signers.”
The agent configures the envelope to route to the first signer, then the second, and provides a summary of the workflow.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/signature-request/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip signature-request.zip -d .agents/skills

Documentation by Anthropic

/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

  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.

Files

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · legal/skills/signature-request · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from legal/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download signature-request.zip