Signature Request Manager
Legal and finance skill, available on Zeplik
Signature Request Manager is a ready-to-run legal and finance skill on Zeplik. ". Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured checklist you can keep and reuse: Checklist artifact -- actionable checked items with state, grouped by phase (see artifact-templates/checklist.md).
The Signature Request Manager skill loads automatically when your request matches it, or you can invoke it directly by typing /signature-request in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Signature Request Manager skill can do
- Run a pre-signature checklist for entity names and exhibits
- Configure signer order and internal approval routing
- Generate a signature envelope or manual signing instructions
- Flag missing schedules or authorized signer issues before sending
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Signature Request Manager skill works
/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
- Check entity names carefully — The most common signing error is incorrect legal entity names.
- Verify authority — Make sure each signer is authorized to bind their organization.
- Keep a copy — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.
How to use the Signature Request Manager skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Signature Request Manager skill right away.
Describe your legal and finance task
Ask in plain language, or type /signature-request to invoke the skill directly. Zeplik recognizes the Signature Request Manager skill and applies its method.
Review and refine the result
Zeplik returns a structured checklist you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- Anthropic
- License
- Apache-2.0
Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Signature Request Manager skill?
- Signature Request Manager is a ready-to-run legal and finance skill on Zeplik. ". Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured checklist you can keep and reuse: Checklist artifact -- actionable checked items with state, grouped by phase (see artifact-templates/checklist.md).
- How do I use Signature Request Manager on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /signature-request in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Signature Request Manager skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Signature Request Manager skill runs on your preferred model for the task.
- Where does the Signature Request Manager skill come from?
- The Signature Request Manager skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Signature Request Manager skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related legal and finance skills
- Account ReconciliationUse when the user asks to reconcile accounts -- "bank rec for June", "GL to subledger reconciliation", "intercompany rec", "find the reconciling items". Compares GL balances to subledgers, bank statements, or third-party data and categorizes differences.
- Audit SupportUse when the user is preparing for an internal or external audit -- "get ready for the auditors", "build testing workpapers", "select audit samples", "classify this control deficiency". SOX 404 control testing methodology and documentation standards. Not for running a SOX testing cycle (use sox-testing).
- Cash Flow SnapshotUse when the user asks about cash flow or runway -- "forecast my cash flow", "will I make payroll", "how long is my runway", "cash crunch coming". Builds a 30/60/90-day cash forecast with confidence bands and named risk flags from books data or CSV, plus a downloadable XLSX.
- Cash-Flow Heads UpA forward-looking 30/60-day cash outlook flagging the tightest week and two things to act on. Not for reconciling and closing the books (use close-month or month-end-prep).
- Compliance CheckUse when the user asks whether a feature, campaign, or initiative is compliant -- "compliance check this launch", "does this touch GDPR or personal data", "what approvals do we need before shipping". Surfaces applicable regulations, required approvals, jurisdictional requirements, and risk areas.
- Contract ReviewUse when the user asks to review a contract -- "review this MSA", "redline this vendor agreement", "what's risky in this contract". Clause-by-clause analysis against a negotiation playbook with redlines, business impact, and fallback positions. Not for quick NDA screening (use triage-nda).
More on Zeplik
Try Signature Request Manager on Zeplik
Every model, one chat. Bring the Signature Request Manager skill into your next conversation and let the assistant do the work.