[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NZFS15GVVM4XBDRKDC6K5":3,"skill-same:01M71NZFS15GVVM4XBDRKDC6K5":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71NZFS15GVVM4XBDRKDC6K5","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.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignature-request\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignature-request\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"request","signature request","work","signing","order","route","with","configure","when","document","use","knowledge","contract","execution","up","send","for","ready","setting","parallel","2026-11-10 10:56:23",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.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"legal\u002Fskills\u002Fsignature-request\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\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,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","legal\u002Fskills\u002Fsignature-request","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignature-request",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill signature-request",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill signature-request",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill signature-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsignature-request\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[83,110,144,167,190,216],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":109},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[90,91,92,93,94,95,96,35,97,98,99,100,101,102,103,104,105,106,107,108],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":126,"publishedAt":109},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[118,123],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[127,128,129,94,130,131,32,132,98,133,134,135,136,137,138,139,140,141,142,143],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":109},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理",[137,155,156,157,158,35,159,32,160,161,26,136,24,162,163,164,165,166,34,33],"write spec","spec","user request","problem","acceptance","ask","vague","scoping","idea","metrics","feature","problem statement",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":109},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[98,137,178,179,40,180,35,34,32,181,182,30,183,26,184,185,186,187,188,189],"write query","postgres","snowflake","best practices","natural-language","multi","github","sql","https","syntax","plugins","data",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":202,"publishedAt":109},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":200,"categoryName":201,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000023","Skill与智能体开发",[203,204,205,43,40,206,207,208,209,97,210,211,212,98,101,184,213,214,215,186],"Workflow Automation","automation","workflow","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":109},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[222],{"categoryNo":200,"categoryName":201,"taxonomyType":121,"taxonomyTypeDesc":122},[205,224,225,226,227,228,229,40,230,231,133,232,233,234,101,184,235,236,186,237],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]