signature-request

Prepares finalized contracts for electronic signature via completeness checklist and signer routing.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sun2443/designer-skills --skill signature-request-sun2443
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signature-request
Source: https://github.com/sun2443/designer-skills/tree/main/legal/skills/signature-request
Command: npx skills add https://github.com/sun2443/designer-skills --skill signature-request-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

signature-request streamlines the legal step of preparing a finalized document for electronic signature, reducing errors in signers, entity names, exhibits, and signing order that can delay execution.

Core Features & Use Cases

  • Pre-signature checklist: Validates the document is final and complete (exhibits/schedules present, correct entity names, signature blocks aligned, dates handled, internal approvals obtained).
  • Signing configuration: Captures signer identity, sequential vs parallel signing order, internal approval needs, and CC recipients for the executed copy.
  • Routing for execution: Creates an e-signature envelope when connected, or produces wet-manual e-sign instructions when e-sign tools are unavailable.

Use cases: Send an MSA/NDA/SOW once finalized, verify that signature blocks and authorized signers match the parties, and ensure the correct attachments and execution-ready formatting before sending for signature.

Quick Start

Use the signature-request skill to route the finalized contract for e-signature by running /signature-request with the document or contract you want to send.

Frequently Asked Questions about signature-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a contract for e-signature and verify signature blocks are correct?

To prepare a contract for e-signature, run a pre-signature completeness checklist that validates final exhibits, entity names, and signature blocks, then configure signer order and routing before execution.

What is included in a pre-signature checklist for contract execution?

A pre-signature checklist for contract execution validates that exhibits and schedules are present, entity names are correct, signature blocks are aligned, dates are handled, and internal approvals are obtained before routing.

How do I configure signing order and CC recipients for an MSA or NDA?

Configuring signing order for an MSA or NDA involves capturing signer identity, setting sequential or parallel signing order, defining internal approval needs, and adding CC recipients to receive the executed copy.

Can I route documents for wet-manual signature if e-signature tools are unavailable?

Yes, when e-signature tools are unavailable, the workflow generates manual wet-manual e-sign instructions instead of creating an electronic envelope, ensuring the document can still be routed for execution.

What types of contracts are supported for electronic signature routing?

Electronic signature routing supports contract execution workflows for MSAs, NDAs, SOWs, and amendments once the documents are finalized and signature blocks must be verified.

Do I need connected e-sign tooling to use the signature routing workflow?

No, connected e-sign tooling is not required; the workflow creates an e-signature envelope when tools are connected, or produces manual signing instructions when e-sign tools are unavailable.