{"id":87773,"plugin_id":"plugin_asdk_app_6ae1b3c33a0c8191a474eb9eb3c3485b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T18:08:56.807Z","digest":"c75277ad970f7b9ffcf01184b7a97960ffb3961f72d15abb8d022d02b38491f0","against":null,"payload":{"description":"Follow up documents that are out for signature in sajn — who has opened or signed, reminders, deadline extensions, withdrawal, and changing parties on sent documents. Use when the user asks about signing status or wants to nudge or manage an in-flight document.","included_files":[],"name":"follow-up-signings","skill_md_contents":"---\nname: follow-up-signings\ndescription: Follow up documents that are out for signature in sajn — who has opened or signed, reminders, deadline extensions, withdrawal, and changing parties on sent documents. Use when the user asks about signing status or wants to nudge or manage an in-flight document.\n---\n\n# Follow up in-flight signings\n\n## Workflow\n\n1. **Locate and read status first.** `findDocumentsByParty` (by person) or `findDocuments` / `listDocuments` with status PENDING, then `getPartyActivity` for who has opened, read, and signed. Answer status questions from this — do not guess.\n2. **Reminders.** `sendDocumentReminder` targets one party, works only while the document is PENDING, and emails them immediately. Confirm with the user before sending, and never remind a party who has already signed.\n3. **Deadlines.** `extendDocumentExpiration` is for sent documents and emails every party about the new date. `setDocumentExpiration` is for drafts only.\n4. **Changing parties on a sent document.** `addPartyToSentDocument` and `removePartyFromSentDocument` alter the live signing process and notify people — state the consequence and confirm before calling. A party who has already signed cannot be removed; the document must be withdrawn instead.\n5. **Withdrawal.** `withdrawDocument` returns the document to draft and notifies all parties. Use it when content must change after sending — then re-send.\n6. **sajn's own suggestions.** `listActions` lists follow-ups sajn already proposes (reminders, extensions, renewals). Prefer acting on an existing card over inventing a parallel action; `dismissAction` is permanent, `snoozeAction` is temporary.\n\n## Validation\n\nAfter any action, re-read `getPartyActivity` or `getDocumentDetails` and report the new state to the user.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}