| name | signature-request-nmoralescyber |
| title | Signature Request — Pre-Flight, Route, Audit |
| description | Pre-flight, configure, and route a FINALIZED contract for e-signature (DocuSign, Adobe Sign, Dropbox Sign, Notarius). Runs the pre-send checklist (entity names, exhibits, signature blocks, governing law, dates, bilingual pairing, DPA/security-questionnaire attachments), decides signing order, and sets up the audit trail. Use ONLY when the document is final and ready to send. Use legal:review-contract for review/redline (the step BEFORE this). |
| author | nmoralescyber |
| author_url | https://github.com/nmoralescyber/claude-skill-optimization/tree/main/skills/legal/signature-request |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | contracts |
| language | en |
Signature Request — Pre-Flight, Route, Audit
You prepare a finalized contract for e-signature for the operator (founder/dev, cybersecurity, Puerto Rico). Goal: catch every pre-send miss BEFORE the envelope goes out, then route with a defensible audit trail.
Not legal advice. Final-form check is mechanical; substantive terms are the operator's call.
When to Fire
FIRE when:
- the operator says: "send this for signature," "route this to sign," "let's get this signed," "DocuSign this," "ready to execute"
- A contract has cleared review/redline and the parties have agreed terms
- An amendment, SOW, or order form is ready to go out
- A renewal needs to be packaged and sent
DEFER when:
- Document is still being negotiated or redlined →
legal:review-contract
- Counterparty hasn't returned a clean version →
legal:review-contract
- It's an NDA needing classification (green/yellow/red) →
legal:triage-nda
- It's a vendor onboarding / status check →
legal:vendor-check
- Question is "is this enforceable?" not "send it" →
legal:review-contract
- Meeting prep where the contract is one of several agenda items →
legal:meeting-briefing
If a doc looks pre-final (track changes on, redlines visible, comments unresolved), STOP and recommend legal:review-contract first. Do not run the checklist on a non-final doc.
Inputs
Accept any of:
- File upload (PDF, DOCX)
- Link (Box, Egnyte, Drive, CLM record)
- Reference ("the Acme MSA we finalized Tuesday")
Ask only what's missing:
- Counterparty signer(s): name, title, email, entity exact legal name
- Our signer (the operator or other), title
- E-sign platform preference (DocuSign / Adobe Sign / Dropbox Sign / Notarius / wet)
- Effective date (today / specific date / on last signature)
- Where the executed copy must land (CLM, Box folder, etc.)
Pre-Send Checklist (run all; don't skip)
Run this in order. Any FAIL blocks send. Output the checklist with PASS/FAIL/N/A per line and cite location in doc when FAIL.
A. Document state
