diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 8fbba82..2e66d73 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -58,6 +58,11 @@ "name": "bio-research", "source": "./bio-research", "description": "Connect to preclinical research tools and databases (literature search, genomics analysis, target prioritization) to accelerate early-stage life sciences R&D" + }, + { + "name": "esignature", + "source": "./esignature", + "description": "Track, manage, and automate e-signature workflows. Monitor pending and signed documents, send reminders, manage templates, and get a real-time view of your signature pipeline." } ] } diff --git a/README.md b/README.md index c902fcb..1263da4 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Each plugin bundles the skills, connectors, slash commands, and sub-agents for a ## Plugin Marketplace -We're open-sourcing 11 plugins built and inspired by our own work: +We're open-sourcing 12 plugins built and inspired by our own work: | Plugin | How it helps | Connectors | |--------|-------------|------------| @@ -19,11 +19,12 @@ We're open-sourcing 11 plugins built and inspired by our own work: | **[customer-support](./customer-support)** | Triage tickets, draft responses, package escalations, research customer context, and turn resolved issues into knowledge base articles. | Slack, Intercom, HubSpot, Guru, Jira, Notion, Microsoft 365 | | **[product-management](./product-management)** | Write specs, plan roadmaps, synthesize user research, keep stakeholders updated, and track the competitive landscape. | Slack, Linear, Asana, Monday, ClickUp, Jira, Notion, Figma, Amplitude, Pendo, Intercom, Fireflies | | **[marketing](./marketing)** | Draft content, plan campaigns, enforce brand voice, brief on competitors, and report on performance across channels. | Slack, Canva, Figma, HubSpot, Amplitude, Notion, Ahrefs, SimilarWeb, Klaviyo | -| **[legal](./legal)** | Review contracts, triage NDAs, navigate compliance, assess risk, prep for meetings, and draft templated responses. | Slack, Box, Egnyte, Jira, Microsoft 365 | +| **[legal](./legal)** | Review contracts, triage NDAs, navigate compliance, assess risk, prep for meetings, and draft templated responses. | Slack, Box, Egnyte, Jira, Microsoft 365, [Signeasy](https://signeasy.com) | | **[finance](./finance)** | Prep journal entries, reconcile accounts, generate financial statements, analyze variances, manage close, and support audits. | Snowflake, Databricks, BigQuery, Slack, Microsoft 365 | | **[data](./data)** | Query, visualize, and interpret datasets — write SQL, run statistical analysis, build dashboards, and validate your work before sharing. | Snowflake, Databricks, BigQuery, Hex, Amplitude, Jira | | **[enterprise-search](./enterprise-search)** | Find anything across email, chat, docs, and wikis — one query across all your company's tools. | Slack, Notion, Guru, Jira, Asana, Microsoft 365 | | **[bio-research](./bio-research)** | Connect to preclinical research tools and databases (literature search, genomics analysis, target prioritization) to accelerate early-stage life sciences R&D. | PubMed, BioRender, bioRxiv, ClinicalTrials.gov, ChEMBL, Synapse, Wiley, Owkin, Open Targets, Benchling | +| **[esignature](./esignature)** | Track, manage, and automate e-signature workflows. Monitor pending and signed documents, send reminders, manage templates, and get a real-time view of your signature pipeline. | [Signeasy](https://signeasy.com) | | **[cowork-plugin-management](./cowork-plugin-management)** | Create new plugins or customize existing ones for your organization's specific tools and workflows. | — | Install these directly from Cowork, browse the full collection here on GitHub, or build your own. diff --git a/esignature/.claude-plugin/plugin.json b/esignature/.claude-plugin/plugin.json new file mode 100644 index 0000000..732d980 --- /dev/null +++ b/esignature/.claude-plugin/plugin.json @@ -0,0 +1,8 @@ +{ + "name": "esignature", + "version": "1.0.0", + "description": "Track, manage, and automate e-signature workflows. Monitor pending and signed documents, send reminders, manage templates, and get a real-time view of your signature pipeline.", + "author": { + "name": "Signeasy" + } +} diff --git a/esignature/.mcp.json b/esignature/.mcp.json new file mode 100644 index 0000000..6f4af38 --- /dev/null +++ b/esignature/.mcp.json @@ -0,0 +1,8 @@ +{ + "mcpServers": { + "signeasy": { + "type": "sse", + "url": "https://mcp.signeasy.com/mcp/sse" + } + } +} diff --git a/esignature/CONNECTORS.md b/esignature/CONNECTORS.md new file mode 100644 index 0000000..0d8de02 --- /dev/null +++ b/esignature/CONNECTORS.md @@ -0,0 +1,13 @@ +# Connectors + +## How tool references work + +Plugin files use `~~category` as a placeholder for whatever tool the user connects in that category. For example, `~~e-signature` might mean Signeasy, DocuSign, or any other e-signature provider with an MCP server. + +Plugins are **tool-agnostic** — they describe workflows in terms of categories (e-signature, cloud storage, chat, etc.) rather than specific products. The `.mcp.json` pre-configures specific MCP servers, but any MCP server in that category works. + +## Connectors for this plugin + +| Category | Placeholder | Included servers | Other options | +|----------|-------------|-----------------|---------------| +| E-signature | `~~e-signature` | [Signeasy](https://signeasy.com) | DocuSign, Adobe Sign | diff --git a/esignature/LICENSE b/esignature/LICENSE new file mode 100644 index 0000000..d645695 --- /dev/null +++ b/esignature/LICENSE @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/esignature/README.md b/esignature/README.md new file mode 100644 index 0000000..75e4d60 --- /dev/null +++ b/esignature/README.md @@ -0,0 +1,143 @@ +# E-Signature Plugin + +An e-signature management plugin primarily designed for [Cowork](https://claude.com/product/cowork), Anthropic's agentic desktop application — though it also works in Claude Code. Track pending documents, send reminders, search across your signature history, and manage templates — all from a single interface. + +## Installation + +``` +claude plugins add knowledge-work-plugins/esignature +``` + +## Quick Start + +### 1. Install the plugin + +``` +claude plugins add knowledge-work-plugins/esignature +``` + +### 2. Connect your e-signature tool + +The plugin comes pre-configured with [Signeasy](https://signeasy.com). See [CONNECTORS.md](CONNECTORS.md) for the full list of supported options. + +### 3. Check your signature dashboard + +``` +/signature-status +``` + +## Commands + +### `/signature-status` -- Signature Dashboard + +Get a real-time overview of your e-signature pipeline — documents pending your signature, documents awaiting others, recently signed, and expired requests. + +``` +/signature-status +``` + +### `/send-reminder` -- Send Signature Reminders + +Send reminders to signers for pending documents. Works for individual documents or in bulk. + +``` +/send-reminder [document name] +/send-reminder all +``` + +### `/document-search` -- Search Documents + +Search across all documents — signed, pending, expired, and templates — by name, signer, or status. + +``` +/document-search [query] +``` + +### `/document-details` -- Document Details + +Get comprehensive information about any document — signer status breakdown, timestamps, and progress. + +``` +/document-details [document ID or name] +``` + +### `/cancel-request` -- Cancel Signature Request + +Safely cancel/void a pending signature request with confirmation workflow. + +``` +/cancel-request [document ID or name] +``` + +## Skills + +| Skill | Description | +|-------|-------------| +| `document-tracking` | Monitor document lifecycle, detect stale requests, track signer status | +| `signature-workflows` | Sending best practices, reminder strategy, template management, troubleshooting | + +## Example Workflows + +### Morning Check-In + +1. Run `/signature-status` to see your dashboard +2. Sign any documents pending your signature +3. Send reminders for documents that have been pending for others for more than 3 days +4. Resend any expired documents that are still needed + +### Following Up on a Contract + +1. Run `/document-search Acme NDA` to find the document +2. See who has signed and who hasn't +3. Run `/send-reminder Acme NDA` to nudge pending signers + +### Bulk Reminder + +1. Run `/send-reminder all` to see all pending documents +2. Confirm which documents to send reminders for +3. Reminders are sent to all pending signers + +## MCP Integration + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md). + +The plugin connects to your e-signature tool through MCP (Model Context Protocol): + +| Category | Tool | Capabilities | +|----------|------|-------------| +| E-signature | [Signeasy](https://signeasy.com) | Track pending/signed/expired documents, send reminders, cancel requests, search signers, manage templates, view account summary | + +### Available Operations + +| Operation | Description | +|-----------|-------------| +| List pending documents | See all documents waiting for signatures | +| Pending for me | Documents that need your signature | +| Pending for others | Documents you sent that are waiting on recipients | +| List signed documents | All completed documents | +| Recently signed | Documents signed in the past N days | +| List expired | Documents that lapsed without being signed | +| Get signer details | See individual signer status for any document | +| Send reminder | Nudge signers on pending documents | +| Cancel request | Void a pending signature request | +| List templates | See all available document templates | +| Account summary | Document counts, subscription status, recent activity | + +## File Structure + +``` +esignature/ +├── .claude-plugin/plugin.json +├── .mcp.json +├── README.md +├── CONNECTORS.md +├── commands/ +│ ├── signature-status.md +│ ├── send-reminder.md +│ ├── document-search.md +│ ├── document-details.md +│ └── cancel-request.md +└── skills/ + ├── document-tracking/SKILL.md + └── signature-workflows/SKILL.md +``` diff --git a/esignature/commands/cancel-request.md b/esignature/commands/cancel-request.md new file mode 100644 index 0000000..4eb008d --- /dev/null +++ b/esignature/commands/cancel-request.md @@ -0,0 +1,87 @@ +--- +description: Cancel a pending signature request — individually or after reviewing all pending documents +argument-hint: "[document name or ID]" +--- + +# /cancel-request -- Cancel Signature Request + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). + +Cancel/void a pending signature request so it can no longer be signed. + +## Invocation + +``` +/cancel-request [document name] # Cancel a specific document's signature request +/cancel-request # Show all pending documents and choose which to cancel +``` + +## Workflow + +### Step 1: Identify the Document + +Query ~~e-signature for pending documents. + +If a specific document name or ID is provided: +- Search for the document by name or ID +- If multiple matches, present the list and ask the user to confirm which one + +If no argument: +- List all documents pending for others +- Ask the user which document(s) to cancel + +### Step 2: Show Document Details + +For the selected document, show full details before cancellation: + +``` +## [Document Name] (ID: [id]) +**Sent**: [date] +**Days Pending**: [count] +**Status**: [signed_count]/[total] signed + +| Signer | Email | Status | +|--------|-------|--------| +| [name] | [email] | Pending / Signed | +``` + +### Step 3: Confirm Cancellation + +**This action is irreversible.** Always confirm before cancelling: + +``` +WARNING: You are about to cancel the signature request for: + - [Document Name] → [pending signer names] + +This will void the document and signers will no longer be able to sign it. +Any signatures already collected will be discarded. + +Proceed with cancellation? [yes/no] +``` + +### Step 4: Cancel and Report + +Cancel the request via ~~e-signature, then confirm: + +``` +## Cancellation Complete + +- [Document Name] (ID: [id]): Signature request cancelled + +The document has been voided. Signers have been notified. +``` + +### Step 5: Suggest Next Steps + +Based on the cancellation, suggest what to do next: +- If the document needs changes: "You can update the document and resend it for signature" +- If it was sent to the wrong person: "You can resend to the correct recipient" +- If it's no longer needed: "No further action required" + +## Notes + +- Only the document owner/sender can cancel a signature request +- Cancellation is **irreversible** — always confirm with the user first +- If the document has already been fully signed (completed), it cannot be cancelled +- If some signers have already signed, warn the user that those signatures will be lost +- Suggest alternatives to cancellation when appropriate (e.g., sending a reminder instead) diff --git a/esignature/commands/document-details.md b/esignature/commands/document-details.md new file mode 100644 index 0000000..63978ac --- /dev/null +++ b/esignature/commands/document-details.md @@ -0,0 +1,89 @@ +--- +description: Get detailed information about a specific document — signer status, timeline, and available actions +argument-hint: "[document name or ID]" +--- + +# /document-details -- Document Details + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). + +Get comprehensive details about a specific e-signature document, including signer-by-signer status, timeline, and available actions. + +## Invocation + +``` +/document-details [document name or ID] +``` + +If no argument is provided, prompt the user for what document they want details on. + +## Workflow + +### Step 1: Find the Document + +Query ~~e-signature to locate the document: + +1. If an **ID** is provided (numeric), fetch details directly using the pending details or signer info tools +2. If a **name** is provided, search across all document states (pending, signed, expired) and match by name +3. If **multiple matches** are found, present the list and ask the user to select one + +### Step 2: Fetch Full Details + +Once the document is identified, gather all available information: + +- **Pending documents**: Get pending envelope details AND signer information +- **Signed documents**: Get signer information with completion timestamps +- **Any document**: Get the document signers for recipient-level detail + +### Step 3: Present Comprehensive Details + +``` +## [Document Name] + +**ID**: [id] +**Status**: [Pending / Signed / Expired / Cancelled] +**Created**: [date] +**Signing Order**: [Sequential / Parallel] + +### Timeline +- **Sent**: [date] +- **Last Activity**: [date or N/A] +- **Expires**: [date or N/A] +- **Completed**: [date or N/A] + +### Signers ([signed_count]/[total] signed) + +| # | Signer | Email | Status | Signed At | +|---|--------|-------|--------|-----------| +| 1 | [name] | [email] | Signed | [date] | +| 2 | [name] | [email] | Pending | -- | +| 3 | [name] | [email] | Declined | -- | +``` + +### Step 4: Show Available Actions + +Based on the document state, present relevant actions: + +**If Pending:** +- Send reminder to unsigned signers +- Cancel the signature request +- View which signer is currently blocking progress (for sequential signing) + +**If Signed/Completed:** +- No further actions needed +- Note completion date and all signer details + +**If Expired:** +- Suggest resending the document +- Note which signers had not yet signed + +**If Cancelled/Voided:** +- Suggest resending if still needed +- Note the cancellation context + +## Notes + +- For documents with sequential signing order, highlight which signer is "next up" +- If a document has been pending for an unusually long time, proactively suggest sending a reminder +- Show both the document-level status and individual signer statuses — they can differ +- If the document is not found in any state, suggest the user check the name/ID and try again diff --git a/esignature/commands/document-search.md b/esignature/commands/document-search.md new file mode 100644 index 0000000..cbc51c9 --- /dev/null +++ b/esignature/commands/document-search.md @@ -0,0 +1,79 @@ +--- +description: Search across all documents — signed, pending, expired, and templates — by name, signer, or status +argument-hint: "[search query]" +--- + +# /document-search -- Search Documents + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). + +Search across all e-signature documents by name, signer, or status. + +## Invocation + +``` +/document-search [query] +``` + +If no query is provided, prompt the user for what they're looking for. + +## Workflow + +### Step 1: Understand the Query + +Parse the search query to determine intent: + +- **By document name**: "NDA with Acme", "Q4 contract" +- **By signer/recipient**: "documents sent to john@example.com", "what did Jane sign" +- **By status**: "all pending", "expired this month", "signed last week" +- **By time range**: "signed this week", "pending for more than 5 days" + +### Step 2: Search Across Document States + +Query ~~e-signature across all relevant states: + +1. **Signed/completed documents** -- Search by name or signer +2. **Pending documents** -- Search pending requests and get signer details +3. **Expired documents** -- Search lapsed requests +4. **Templates** -- Search available templates +5. **Original documents** -- Search uploaded files + +### Step 3: Present Results + +``` +## Search Results: "[query]" + +### Signed Documents ([count]) +| Document | Signers | Signed Date | +|----------|---------|-------------| +| [name] | [names] | [date] | + +### Pending Documents ([count]) +| Document | Waiting On | Sent Date | Days Pending | +|----------|-----------|-----------|--------------| +| [name] | [names] | [date] | [count] | + +### Expired Documents ([count]) +| Document | Intended Signers | Expired Date | +|----------|-----------------|--------------| +| [name] | [names] | [date] | + +### Templates ([count]) +| Template Name | +|--------------| +| [name] | +``` + +### Step 4: Offer Actions + +For each result type, suggest relevant actions: +- **Signed**: View signer details +- **Pending**: Send reminder, view signer status, cancel request +- **Expired**: Resend for signature +- **Templates**: Use template to create new signature request + +## Notes + +- If the search returns no results, suggest broadening the search or trying alternate names +- For signer searches, match on both name and email +- Show the most recent results first diff --git a/esignature/commands/send-reminder.md b/esignature/commands/send-reminder.md new file mode 100644 index 0000000..a795fed --- /dev/null +++ b/esignature/commands/send-reminder.md @@ -0,0 +1,81 @@ +--- +description: Send signature reminders for pending documents — individually or in bulk +argument-hint: "[document name or 'all']" +--- + +# /send-reminder -- Signature Reminders + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). + +Send reminders to signers for pending signature requests. + +## Invocation + +``` +/send-reminder [document name] # Remind signers for a specific document +/send-reminder all # Remind signers for all pending documents +``` + +If no argument is provided, show all pending documents and let the user choose. + +## Workflow + +### Step 1: Identify Pending Documents + +Query ~~e-signature for documents pending for others. + +If a specific document name is provided: +- Search for the document by name +- If multiple matches, present the list and ask the user to confirm + +If `all` is specified: +- List all documents pending for others + +If no argument: +- List all pending documents with their signer status +- Ask the user which documents to send reminders for + +### Step 2: Show Signer Details + +For each selected document, show: + +``` +## [Document Name] +**Sent**: [date] +**Days Pending**: [count] + +| Signer | Email | Status | +|--------|-------|--------| +| [name] | [email] | Pending / Signed | +``` + +### Step 3: Confirm and Send + +Ask the user to confirm before sending reminders: + +``` +Ready to send reminders for: +- [Document 1] → [pending signer names] +- [Document 2] → [pending signer names] + +Proceed? [yes/no] +``` + +Send the reminder via ~~e-signature. + +### Step 4: Report Results + +``` +## Reminders Sent + +- [Document 1]: Reminder sent to [signer names] +- [Document 2]: Reminder sent to [signer names] + +[count] reminders sent successfully. +``` + +## Notes + +- Only send reminders to signers who have not yet signed +- If a document has been pending for less than 24 hours, suggest the user wait before sending a reminder +- Show the number of previous reminders sent if available, to avoid over-reminding diff --git a/esignature/commands/signature-status.md b/esignature/commands/signature-status.md new file mode 100644 index 0000000..469a55a --- /dev/null +++ b/esignature/commands/signature-status.md @@ -0,0 +1,79 @@ +--- +description: Get a dashboard view of all signature activity — pending, signed, expired, and documents awaiting your action +--- + +# /signature-status -- Signature Dashboard + +> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). + +Get a real-time overview of your e-signature pipeline across all document states. + +## Invocation + +``` +/signature-status +``` + +## Workflow + +### Step 1: Gather Data + +Query ~~e-signature for all document states: + +1. **Pending for me** -- Documents that need your signature +2. **Pending for others** -- Documents you sent that are waiting on others +3. **Recently signed** -- Documents completed in the past 7 days +4. **Expired/lapsed** -- Signature requests that expired without completion +5. **Account info** -- Subscription status, credits, and user details +6. **Account summary** -- Overall document counts and recent activity + +### Step 2: Generate Dashboard + +Output a structured dashboard: + +``` +## Signature Dashboard -- [Date] + +### Action Required +- **Pending Your Signature**: [count] + [List each document with name, sender, and date received] + +### Awaiting Others +- **Sent & Waiting**: [count] + [List each document with name, recipients, and days pending] + +### Recently Completed +- **Signed This Week**: [count] + [List each document with name, signers, and completion date] + +### Needs Attention +- **Expired/Lapsed**: [count] + [List each document with name, intended signers, and expiry date] + +### Account Overview +- **Total Documents**: [count] +- **Templates Available**: [count] +- **Subscription Status**: [status] +- **Envelope Credits**: [count] +- **Paid Account**: [yes/no] +``` + +### Step 3: Highlight Urgent Items + +Flag any items that need immediate attention: +- Documents pending your signature for more than 2 days +- Documents sent to others that have been pending for more than 5 days +- Recently expired documents that may need to be resent + +### Step 4: Suggest Actions + +Based on the current state, suggest next steps: +- Remind signers on stale pending documents +- Resend expired documents +- Follow up on documents awaiting others + +## Notes + +- If ~~e-signature is not connected, inform the user and provide instructions for connecting +- Sort pending documents by date received (oldest first) to prioritize +- For documents with multiple signers, show individual signer status diff --git a/esignature/skills/document-tracking/SKILL.md b/esignature/skills/document-tracking/SKILL.md new file mode 100644 index 0000000..32e7c88 --- /dev/null +++ b/esignature/skills/document-tracking/SKILL.md @@ -0,0 +1,80 @@ +--- +name: document-tracking +description: Track and manage the e-signature document lifecycle — monitor pending requests, follow up on stale documents, and maintain visibility across all signature activity. Use when checking document status, following up on unsigned documents, or reviewing signature completion rates. +--- + +# Document Tracking Skill + +You are an e-signature document tracking assistant. You help users maintain visibility across their entire signature pipeline — from sent to signed to expired. + +## Core Capabilities + +### Document States + +Understand and track documents across these states: + +| State | Description | Available Actions | +|-------|-------------|-------------------| +| **Pending (for me)** | Documents waiting for the user's signature | Sign, view details | +| **Pending (for others)** | Documents the user sent, waiting on recipients | Send reminder, cancel, view signer status | +| **Signed/Completed** | Fully executed documents | View, download, check signer details | +| **Expired/Lapsed** | Documents that were not signed before the deadline | Resend, review | +| **Templates** | Reusable document templates | Use to create new requests | + +### Monitoring Patterns + +When tracking documents, apply these patterns: + +**Stale Document Detection**: +- Documents pending for more than 3 business days should be flagged +- Documents pending for more than 7 days should be escalated +- Suggest sending reminders for stale documents + +**Expiration Awareness**: +- Alert users to documents approaching expiration +- Recommend resending expired documents that are still needed +- Track patterns in which recipients tend to let documents expire + +**Completion Tracking**: +- Track recently signed documents for confirmation +- Note multi-signer documents where some have signed and others haven't +- For documents with signing order, identify which signer is currently blocking progress + +### Signer Intelligence + +When checking signer details: +- Show individual signer status (signed / pending / viewed) +- Identify which signer is currently blocking a multi-party document +- Surface the signer's email for follow-up outside the e-signature tool + +## Workflow Guidance + +### Daily Check-In + +When a user starts their day or asks about document status: +1. Check for documents pending the user's own signature first (these are action items) +2. Show documents sent to others that are stale (> 3 days) +3. Highlight any expired documents that may need to be resent +4. Summarize recently completed documents + +### Following Up on a Specific Document + +When a user asks about a specific document: +1. Search across all states (pending, signed, expired) +2. Show full signer details including individual status +3. Suggest the most relevant action (remind, cancel, resend) + +### Bulk Operations + +When a user wants to manage multiple documents: +1. Group documents by status and urgency +2. Allow bulk reminders for all stale pending documents +3. Present a prioritized list with recommended actions + +## Integration with Other Workflows + +When e-signature context is relevant to other tasks: +- **Contract review**: After review is complete, check if the document is already in the signature pipeline +- **Vendor check**: Search signed and pending documents for the vendor name +- **Daily brief**: Include signature status as part of the morning overview +- **NDA triage**: After triage, check if the NDA is already pending signature diff --git a/esignature/skills/signature-workflows/SKILL.md b/esignature/skills/signature-workflows/SKILL.md new file mode 100644 index 0000000..054ae57 --- /dev/null +++ b/esignature/skills/signature-workflows/SKILL.md @@ -0,0 +1,97 @@ +--- +name: signature-workflows +description: Best practices for e-signature workflows — sending documents for signature, managing signing order, handling reminders, and resolving common signature issues. Use when sending documents, troubleshooting signing problems, or optimizing signature turnaround times. +--- + +# Signature Workflows Skill + +You are an e-signature workflow assistant. You help users send documents efficiently, manage the signing process, and resolve common issues. + +## Sending for Signature + +### Pre-Send Checklist + +Before sending a document for signature, verify: +- [ ] Document is in final form (no pending edits or redlines) +- [ ] All signer names and email addresses are correct +- [ ] Signing order is appropriate (if multi-party) +- [ ] Expiration date is set appropriately for the document type + +### Signing Order Guidance + +| Scenario | Recommended Order | +|----------|------------------| +| **Mutual NDA** | Either party first; no dependency | +| **Vendor contract** | Vendor signs first, then your organization's authorized signatory | +| **Employment agreement** | Employee signs first, then HR/management counter-signs | +| **Amendment** | Same order as original agreement, or party proposing the amendment signs first | +| **Multi-party** | Start with the party most likely to delay; get their commitment first | + +### Reminder Strategy + +Follow this escalation pattern for unsigned documents: + +| Days Pending | Action | +|-------------|--------| +| 3 days | First reminder via e-signature tool | +| 5 days | Second reminder; consider a direct message or email | +| 7 days | Escalate internally; contact the signer's point of contact | +| 10+ days | Review whether the document is still needed; consider cancelling and re-engaging | + +### Handling Expired Documents + +When a document expires without being signed: +1. Determine if the document is still needed +2. Check if terms or details need to be updated before resending +3. Reach out to the signer before resending to confirm they will sign +4. Resend with appropriate expiration (consider a longer window) + +## Template Management + +### When to Use Templates + +Use templates for documents that are sent frequently with minimal changes: +- Standard NDAs +- Offer letters +- Vendor onboarding forms +- Service agreements with standard terms +- Compliance acknowledgments + +### Template Best Practices + +- Keep template names descriptive and consistent (e.g., "Mutual NDA - Standard", "SOW Template - Consulting") +- Review templates periodically to ensure terms are current +- Maintain separate templates for different use cases rather than one generic template + +## Troubleshooting + +### Common Issues + +**Signer says they didn't receive the document:** +- Verify the email address is correct +- Send a reminder (this resends the notification) +- Ask the signer to check spam/junk folders +- Consider resending to an alternate email + +**Document was sent to the wrong person:** +- Cancel the request immediately +- Resend to the correct recipient +- If the wrong person already viewed or signed, flag for legal review + +**Signer needs to make changes before signing:** +- Cancel the current request +- Make the necessary changes to the document +- Resend the updated version + +**Document expired:** +- Check if terms are still current +- Resend with an appropriate new expiration date +- Contact the signer to ensure they will complete it this time + +## Metrics and Reporting + +When asked about signature performance, track: +- **Average time to signature**: How long documents take to get fully signed +- **Completion rate**: Percentage of sent documents that get signed vs. expire +- **Stale document rate**: How many documents are currently overdue +- **Busiest signers**: Which recipients have the most pending documents diff --git a/legal/.mcp.json b/legal/.mcp.json index e511a49..c7c6b9b 100644 --- a/legal/.mcp.json +++ b/legal/.mcp.json @@ -19,6 +19,10 @@ "ms365": { "type": "http", "url": "https://microsoft365.mcp.claude.com/mcp" + }, + "signeasy": { + "type": "sse", + "url": "https://mcp.signeasy.com/mcp/sse" } } } diff --git a/legal/CONNECTORS.md b/legal/CONNECTORS.md index 8aaa878..46197ee 100644 --- a/legal/CONNECTORS.md +++ b/legal/CONNECTORS.md @@ -14,6 +14,6 @@ Plugins are **tool-agnostic** — they describe workflows in terms of categories | Cloud storage | `~~cloud storage` | Box, Egnyte | Dropbox, SharePoint, Google Drive | | CLM | `~~CLM` | — | Ironclad, Agiloft | | CRM | `~~CRM` | — | Salesforce, HubSpot | -| E-signature | `~~e-signature` | — | DocuSign, Adobe Sign | +| E-signature | `~~e-signature` | Signeasy | DocuSign, Adobe Sign | | Office suite | `~~office suite` | Microsoft 365 | Google Workspace | | Project tracker | `~~project tracker` | Atlassian (Jira/Confluence) | Linear, Asana | diff --git a/legal/README.md b/legal/README.md index 9ff2355..e892cd8 100644 --- a/legal/README.md +++ b/legal/README.md @@ -77,7 +77,7 @@ Configure paths to your template files or define inline templates for common inq ### 3. Connect your tools -The plugin works best when connected to your existing tools via MCP. Pre-configured servers include Slack, Box, Egnyte, Atlassian, and Microsoft 365. See [CONNECTORS.md](CONNECTORS.md) for the full list of supported categories and options. +The plugin works best when connected to your existing tools via MCP. Pre-configured servers include Slack, Box, Egnyte, Atlassian, Microsoft 365, and Signeasy. See [CONNECTORS.md](CONNECTORS.md) for the full list of supported categories and options. ## Commands @@ -181,6 +181,7 @@ The plugin connects to your tools through MCP (Model Context Protocol) servers: |----------|----------|---------| | Chat | Slack, Teams | Team requests, notifications, triage | | Cloud storage | Box, Egnyte | Playbooks, templates, precedents | +| E-signature | [Signeasy](https://signeasy.com) | Track pending and signed documents, send reminders, cancel requests, search signers, manage templates | | Office suite | Microsoft 365 | Email, calendar, documents | | Project tracker | Atlassian (Jira/Confluence) | Matter tracking, tasks | diff --git a/legal/commands/brief.md b/legal/commands/brief.md index d55a426..93cbcaf 100644 --- a/legal/commands/brief.md +++ b/legal/commands/brief.md @@ -57,6 +57,12 @@ Check each connected source for legal-relevant items: - Approaching expiration dates (next 30 days) - Newly executed agreements +**E-signature (if connected):** +- Documents pending your signature +- Documents you sent that are waiting on others to sign +- Documents signed in the past week +- Expired or lapsed signature requests that need follow-up + **CRM (if connected):** - Deals moving to stages that require legal involvement - New opportunities flagged for legal review @@ -74,6 +80,12 @@ Check each connected source for legal-relevant items: - **Pending Counterparty Response**: [count and list] - **Approaching Deadlines**: [items due this week] +### Signature Status +- **Pending Your Signature**: [count and list from ~~e-signature] +- **Awaiting Others**: [count and list of documents sent for signature] +- **Recently Signed**: [documents completed in the past week] +- **Expired/Lapsed**: [signature requests that expired without completion] + ### New Requests [Contract review requests, NDA requests, compliance questions received since last brief] diff --git a/legal/commands/triage-nda.md b/legal/commands/triage-nda.md index bf787c0..1889db4 100644 --- a/legal/commands/triage-nda.md +++ b/legal/commands/triage-nda.md @@ -145,7 +145,7 @@ Output a structured report: ### Step 6: Routing Suggestion Based on the classification: -- **GREEN**: Suggest the user proceed to signature under their standard delegation of authority +- **GREEN**: Suggest the user proceed to signature under their standard delegation of authority. If ~~e-signature is connected, offer to send the NDA for signature via the e-signature tool - **YELLOW**: Identify which specific issues need counsel attention and suggest the user route to the appropriate reviewer - **RED**: Recommend the user engage counsel for a full review, and provide a counterproposal NDA if the organization has a standard form diff --git a/legal/commands/vendor-check.md b/legal/commands/vendor-check.md index 147997c..ec72515 100644 --- a/legal/commands/vendor-check.md +++ b/legal/commands/vendor-check.md @@ -59,6 +59,13 @@ Search for: - Redlines and drafts - Due diligence materials +#### E-signature (e.g., Signeasy) -- If Connected +Search for documents involving the vendor: +- Signed/completed documents (search by vendor name) +- Pending signature requests involving the vendor +- Expired or lapsed documents that were not signed +- Signer details and signature status for each document + #### Chat (e.g., Slack, Teams) -- If Connected Search for recent mentions: - Contract requests involving this vendor