agentleFS
nisarthnisarth/claude-skills-store/skills/legal/signature-request/SKILL.md

signature-request

Skill1 starsChanged 7 months agoMITView on GitHub

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, verifying entity names and signature blocks, or configuring multi-party signing. Trigger with "send for signature", "signature request", "route for signing", or "e-signature".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Exhibits: All referenced exhibits attached and complete.

    line 35
  2. Distinctive:

    Parallel: All signers receive simultaneously.

    line 43
  3. Distinctive:

    Action: Run pre-signature checklist, verify entities and authority, configure sequential signing (Acme first), set 14-day expiration with …

    line 81
  4. Distinctive:

    Never send without completing the pre-signature checklist.

    line 88
  5. Distinctive:

    Verify signer authority against the delegation of authority matrix for the contract value.

    line 90
  6. Distinctive:

    After execution, file the fully executed copy and set reminders for key dates.

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Signature Request Preparation

Prepare documents for e-signature by running a pre-signature checklist, configuring signing order and routing, and verifying all prerequisites.

Workflow

Step 1: Pre-Signature Checklist

  • Final version: Confirmed with all negotiated changes incorporated.
  • Entity names: Match official registered names for all parties.
  • Signature blocks: Signer name, title, and entity correct.
  • Dates: Effective date, term dates, milestones verified.
  • Exhibits: All referenced exhibits attached and complete.
  • Internal approvals: Legal, finance, and business approvals obtained.
  • Authority: Each signer authorized for this contract type and value.
  • Clean copy: Draft watermarks, track changes, and comments removed.

Step 2: Configure Signing Order

  • Sequential: Counterparty signs first, then internal signer. Use when one signature depends on another.
  • Parallel: All signers receive simultaneously. Use for independent signers or time-sensitive execution.
  • Hybrid: Mix of sequential and parallel for multi-party agreements.

Roles: Signer, Initialer, Approver (review only), CC/Observer.

Step 3: Set Notifications and Deadlines

  • Envelope expiration (default: 14 days), reminders (default: every 3 days).
  • Completion notifications for stakeholders.
  • Post-execution filing location (CLM, matter folder).

Output Format

## Signature Request
**Document**: [Title] | **Date**: [YYYY-MM-DD]

### Pre-Signature Checklist
- [x] Final version confirmed (v[X])
- [x] Entity names verified
- [x] Signature blocks correct
- [x] Exhibits attached ([N] total)
- [x] Internal approvals obtained
- [ ] Draft markings removed

### Signing Order
| Order | Signer | Title | Entity | Role | Email |
|-------|--------|-------|--------|------|-------|
| 1 | [Name] | [Title] | [Entity] | Signer | [email] |

### Configuration
- Order: [Sequential / Parallel] | Expiration: [X days]
- Post-execution filing: [Location]

Examples

User: "Send the Acme Corp MSA for signature" Action: Run pre-signature checklist, verify entities and authority, configure sequential signing (Acme first), set 14-day expiration with 3-day reminders.

User: "The board resolution needs all directors' signatures today" Action: Configure parallel signing for all directors, set 24-hour expiration, enable hourly reminders, flag urgency in cover message.

Best Practices

  • Never send without completing the pre-signature checklist. Entity name errors can invalidate the agreement.
  • Have the counterparty sign first to retain the option not to countersign.
  • Verify signer authority against the delegation of authority matrix for the contract value.
  • After execution, file the fully executed copy and set reminders for key dates.
  • For multi-entity agreements, triple-check each entity's signer and signature block match.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.