Signature Request
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.
MCP get_skill({ skillId: "signature-request-e-signature-routing-d7fa3a74" })Use this skill with your agent
Create a free account and connect via MCP
# /signature-request -- E-Signature Routing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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: ```markdown ## 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 ```markdown ## 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
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Audit Support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
Compliance Check
Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding.
Compliance Tracking
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.