SkillAgentSearch skills...

signature-request

Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution

Install / Use

npx skills add anthropics/knowledge-work-plugins --skill signature-request

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Zed

Tags

Our assessment of signature-request

signature-request scores 93/100 on our quality scale, 189th of 1,155 Content & Media skills we index (top 17%).

Its SKILL.md is 3.3 KB long, well organised into 17 sections with 3 code examples: a solid amount of guidance for an agent.

With 25,526 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
19/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so signature-request is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

signature-request compared with similar skills

All 4 of these similar skills score higher than signature-request; compare them before choosing.

SkillScoreStarsUpdatedFormat
signature-request (this skill)by anthropics9325.5k53d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install signature-request?
Run npx skills add anthropics/knowledge-work-plugins --skill signature-request. The install tabs above show the steps for each supported agent.
Which AI agents does signature-request work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is signature-request safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is signature-request still maintained?
The repository was last updated about 2 months ago, so signature-request is actively maintained.

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

  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.

Related Skills

View on GitHub
GitHub Stars25.5k
CategoryContent
Updated1mo ago
Forks3.0k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions