[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718DRAGTH4QSNR9HT3JMTFM":3,"skill-same:01M718DRAGTH4QSNR9HT3JMTFM":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M718DRAGTH4QSNR9HT3JMTFM","signature-request",null,"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.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35379,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Fsignature-request\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"request","signature request","checklist","blocks","sign","run","signing","route","with","configure","when","document","use","contract","execution","up","send","for","ready","parallel","2026-11-10 10:12:30",false,"---\nname: signature-request\ndescription: 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.\nargument-hint: \"\u003Cdocument or contract to send>\"\n---\n\n# \u002Fsignature-request -- E-Signature Routing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nPrepare a document for electronic signature — verify completeness, set signing order, and route for execution.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.\n\n## Usage\n\n```\n\u002Fsignature-request $ARGUMENTS\n```\n\nPrepare for signature: @$1\n\n## Workflow\n\n### Step 1: Accept the Document\n\nAccept the document in any format:\n- **File upload**: PDF, DOCX\n- **URL**: Link to a document in ~~cloud storage or ~~CLM\n- **Reference**: \"The Acme Corp MSA we finalized yesterday\"\n\n### Step 2: Pre-Signature Checklist\n\nBefore routing for signature, verify:\n\n```markdown\n## Pre-Signature Checklist\n\n- [ ] Document is in final, agreed form (no open redlines)\n- [ ] All exhibits and schedules are attached\n- [ ] Correct legal entity names on signature blocks\n- [ ] Dates are correct or left blank for execution date\n- [ ] Signature blocks match the authorized signers\n- [ ] Any required internal approvals have been obtained\n- [ ] Document has been reviewed by appropriate counsel\n```\n\n### Step 3: Configure Signing\n\nGather signing details:\n- **Signers**: Who needs to sign? (names, emails, titles)\n- **Signing order**: Sequential or parallel?\n- **Internal approval**: Does anyone need to approve before the counterparty signs?\n- **CC recipients**: Who should receive a copy of the executed document?\n\n### Step 4: Route for Signature\n\n**If ~~e-signature is connected:**\n- Create the signature envelope\u002Frequest\n- Set signing fields and order\n- Add any required initials or date fields\n- Send for signature\n\n**If not connected:**\n- Generate a signing instruction document\n- Provide the document formatted for wet signature or manual e-sign\n- List all signers with contact information\n\n## Output\n\n```markdown\n## Signature Request: [Document Title]\n\n### Document Details\n- **Type**: [MSA \u002F NDA \u002F SOW \u002F Amendment \u002F etc.]\n- **Parties**: [Party A] and [Party B]\n- **Pages**: [X]\n\n### Pre-Signature Check: [PASS \u002F ISSUES FOUND]\n[List any issues that need attention before sending]\n\n### Signing Configuration\n| Order | Signer | Email | Role |\n|-------|--------|-------|------|\n| 1 | [Name] | [email] | [Party A Authorized Signatory] |\n| 2 | [Name] | [email] | [Party B Authorized Signatory] |\n\n### CC Recipients\n- [Name] — [email]\n\n### Status\n[Sent for signature \u002F Ready to send \u002F Issues to resolve first]\n\n### Next Steps\n- [What to expect after sending]\n- [Expected turnaround time]\n- [Follow-up if not signed within X days]\n```\n\n## Tips\n\n1. **Check entity names carefully** — The most common signing error is incorrect legal entity names.\n2. **Verify authority** — Make sure each signer is authorized to bind their organization.\n3. **Keep a copy** — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.\n","# \u002Fsignature-request -- E-Signature Routing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nPrepare a document for electronic signature — verify completeness, set signing order, and route for execution.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.\n\n## Usage\n\n```\n\u002Fsignature-request $ARGUMENTS\n```\n\nPrepare for signature: @$1\n\n## Workflow\n\n### Step 1: Accept the Document\n\nAccept the document in any format:\n- **File upload**: PDF, DOCX\n- **URL**: Link to a document in ~~cloud storage or ~~CLM\n- **Reference**: \"The Acme Corp MSA we finalized yesterday\"\n\n### Step 2: Pre-Signature Checklist\n\nBefore routing for signature, verify:\n\n```markdown\n## Pre-Signature Checklist\n\n- [ ] Document is in final, agreed form (no open redlines)\n- [ ] All exhibits and schedules are attached\n- [ ] Correct legal entity names on signature blocks\n- [ ] Dates are correct or left blank for execution date\n- [ ] Signature blocks match the authorized signers\n- [ ] Any required internal approvals have been obtained\n- [ ] Document has been reviewed by appropriate counsel\n```\n\n### Step 3: Configure Signing\n\nGather signing details:\n- **Signers**: Who needs to sign? (names, emails, titles)\n- **Signing order**: Sequential or parallel?\n- **Internal approval**: Does anyone need to approve before the counterparty signs?\n- **CC recipients**: Who should receive a copy of the executed document?\n\n### Step 4: Route for Signature\n\n**If ~~e-signature is connected:**\n- Create the signature envelope\u002Frequest\n- Set signing fields and order\n- Add any required initials or date fields\n- Send for signature\n\n**If not connected:**\n- Generate a signing instruction document\n- Provide the document formatted for wet signature or manual e-sign\n- List all signers with contact information\n\n## Output\n\n```markdown\n## Signature Request: [Document Title]\n\n### Document Details\n- **Type**: [MSA \u002F NDA \u002F SOW \u002F Amendment \u002F etc.]\n- **Parties**: [Party A] and [Party B]\n- **Pages**: [X]\n\n### Pre-Signature Check: [PASS \u002F ISSUES FOUND]\n[List any issues that need attention before sending]\n\n### Signing Configuration\n| Order | Signer | Email | Role |\n|-------|--------|-------|------|\n| 1 | [Name] | [email] | [Party A Authorized Signatory] |\n| 2 | [Name] | [email] | [Party B Authorized Signatory] |\n\n### CC Recipients\n- [Name] — [email]\n\n### Status\n[Sent for signature \u002F Ready to send \u002F Issues to resolve first]\n\n### Next Steps\n- [What to expect after sending]\n- [Expected turnaround time]\n- [Follow-up if not signed within X days]\n```\n\n## Tips\n\n1. **Check entity names carefully** — The most common signing error is incorrect legal entity names.\n2. **Verify authority** — Make sure each signer is authorized to bind their organization.\n3. **Keep a copy** — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.\n",{"name":5,"description":7,"argument-hint":54},"\u003Cdocument or contract to send>","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","legal\u002Fskills\u002Fsignature-request",3918,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 11:16:59",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill signature-request",{"tool":69,"command":70},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill signature-request",{"tool":72,"command":73},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill signature-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Fsignature-request\u002FSKILL.md",true,[],[78,103,126,147,173,199],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":49},"01M718Y97HCGW12Q53PSJDY03W","ticket-deflector","Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says \"draft a response,\" \"answer this customer,\" \"where's my order,\" \"I want a refund,\" \"check my orders,\" or \"anything about to blow up.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fticket-deflector\u002FSKILL.md",[],[85,86,87,44,88,89,90,39,91,92,93,94,95,96,97,98,99,100,101,102],"ticket","ticket deflector","mode","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":49},"01M718Y55HFAN5705ME5VEDZ9K","tax-season-organizer","Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags.\nAny tax request routes first to \u002Ftax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: \"books are closed, now do the 1099s,\" \"run the quarterly estimate off the closed numbers,\" or \"just the contractor W-9 list.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-season-organizer\u002FSKILL.md",[],[110,111,112,113,114,115,116,117,118,119,39,120,121,122,34,29,102,123,124,125],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","flags","list","stripe",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":49},"01M718Y13VVPHDD9NTDBVFJ2AZ","tax-prep","Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on \"quarterly taxes,\" \"estimated tax payment,\" \"how much should I set aside,\" \"1099s,\" \"1099-NEC,\" \"W-9s,\" \"year-end tax prep,\" \"get my books ready for my accountant,\" any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-prep\u002FSKILL.md",[],[133,111,134,135,112,136,47,114,137,138,139,140,141,46,142,116,143,144,145,146],"tax prep","prep","SET","as","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":49},"01M718XWTWQZ01GYSG9T8RW8TW","speed-to-lead","Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like \"leads are going cold,\" \"did anyone answer that inquiry,\" \"I keep missing form submissions,\" \"nothing falls through the cracks,\" \"handle my inbound,\" \"respond to this lead,\" or \"we lose people because nobody gets back fast enough.\" Reach for it for a single unanswered inquiry as readily as for a standing setup.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fspeed-to-lead\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[157,158,159,160,161,162,137,163,164,45,165,166,167,168,39,169,170,93,171,172],"speed to lead","lead","speed","shared","back","cold","time","inbox","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":49},"01M718XQYMN1KY3TPS33967FK0","social-content-engine","Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including \"I need to post more,\" \"we've gone quiet on Instagram,\" \"what should we post this month,\" \"make the content,\" \"give me a month of posts,\" \"write this in my voice,\" \"repurpose this,\" or \"set up our content calendar.\" Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsocial-content-engine\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[183,184,185,186,187,188,135,189,190,191,192,44,193,39,194,195,196,102,197,198],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":49},"01M718XMPJVH0EVRVP998BVZPC","smb-router","The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks \"what can you do,\" \"help me with my business,\" \"what should I focus on,\" \"I don't know where to start,\" or any open-ended business request that doesn't clearly match a single skill.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[206,207,208,136,209,46,142,210,89,211,119,146,212,213,214,37,215,194,216,97],"router","smb","smb router","do","front","single","you","vague","can","plugin","focus"]