[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PDNB14S4YC2P900K1HB5Y":3,"skill-same:01M79PDNB14S4YC2P900K1HB5Y":61},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79PDNB14S4YC2P900K1HB5Y","master-agreement-generator",null,"Generate review drafts of counterparty master agreements from one template plus a JSON spec, with role-selected clauses and a Schedule A workflow limited to the executed agreement's notice authority. Use when you need reproducible drafting and separately reviewed execution preparation.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmaster-agreement-generator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: master-agreement-generator\ndescription: Generate review drafts of counterparty master agreements from one template plus a JSON spec, with role-selected clauses and a Schedule A workflow limited to the executed agreement's notice authority. Use when you need reproducible drafting and separately reviewed execution preparation.\n---\n\n# Master Agreement Generator\n\nOne master template, one small spec per counterparty, one draft build step.\nThe generator always labels output **DRAFT**, including documents generated\nfrom a completed template. A successful conversion proves artifact generation,\nnot legal completeness, authority to contract, or readiness to send or sign.\nAn executed agreement may permit designated opportunities to be added by notice;\nthat authority must be established before using the Schedule A workflow.\n\n## When to Use\n\n- You issue a framework agreement (NDA, referral or sourcing fee,\n  non-circumvention, master services) to many counterparties with the same\n  terms and a few party-specific fields.\n- Deals are added over time and re-papering each one is the bottleneck.\n- Documents must be reproducible from tracked source, diffable, and free of\n  hand edits.\n- Signature fields are placed by automation and need a stable page layout.\n\n## How It Works\n\n### Template\n\nA single markdown template with `{{PLACEHOLDER}}` fields. Every party-specific\nvalue is a placeholder; everything else is fixed text. A skeleton lives at\n[references\u002Fmaster-template.example.md](references\u002Fmaster-template.example.md).\nReplace its generic sentences with your counsel-approved clauses.\n\nPlaceholders the reference script fills:\n\n| Placeholder | Source |\n| --- | --- |\n| `{{DATE}}` | `spec.date`, default today |\n| `{{CP_SHORT}}` | `spec.short` |\n| `{{CP_LEGAL}}`, `{{CP_JURIS}}`, `{{CP_ADDR}}` | spec fields, or a blank line when the counterparty completes them at signing |\n| `{{ROLE_CLAUSE}}`, `{{FEE_TITLE}}`, `{{FEE_CLAUSE}}` | selected by `spec.role` from the role table |\n| `{{SCHEDULE_ROWS}}` | `spec.schedule`, or one \"no entries at signing\" row |\n| `{{SUPPLEMENT_CLAUSE}}` | `spec.supplement`, rendered with a trailing separator or empty |\n| `{{CP_SIGBLOCK}}`, `{{CP_SIGNER}}`, `{{CP_TITLE}}`, `{{CP_EMAIL}}` | signature block fields, blanks when unknown |\n\n### Spec\n\nOne JSON file per counterparty:\n\n```json\n{\n  \"file\": \"AcmeSupplier\",\n  \"short\": \"Acme\",\n  \"role\": \"supplier\",\n  \"legal\": \"Acme Compute Ltd\",\n  \"juris\": \"England and Wales company\",\n  \"addr\": \"1 Example Street, London\",\n  \"signer\": \"A. Person\",\n  \"title\": \"Director\",\n  \"email\": \"signer@example.com\",\n  \"schedule\": [[\"1\", \"2026-09-01\", \"Lot A (16 nodes)\", \"introducer\", \"12 months\", \"standard\"]],\n  \"supplement\": \"the Data Processing Addendum dated 2026-09-01\"\n}\n```\n\nOnly `file`, `short`, and `role` are required for a draft. Missing signature fields\nrender as blank lines for review and completion. See\n[references\u002Fspec.example.json](references\u002Fspec.example.json).\n\n`file` must be a nonempty portable filename, such as `AcmeSupplier` or\n`Acme Supplier`, without directory components. The builder rejects either path\nseparator, drive\u002FUNC syntax, control characters, Windows-reserved punctuation\nor device names, and trailing dots or spaces. Invalid names are rejected without\nsanitizing or renaming them, before creating output or invoking pandoc.\n\nOmit `schedule` or use `[]` for the “no entries at signing” placeholder. A supplied\nschedule must otherwise be a dense array of six-cell arrays, in this order:\nnumber, date, protected counterparty or lot, role, terms, fee. Each cell must be\na valid Unicode string or finite number; empty strings are allowed for intentional blanks.\nNulls, booleans, objects, nested cell arrays, missing cells and non-finite numbers\nare rejected with a row\u002Fcell index before any artifact write or pandoc activity.\nUnpaired UTF-16 surrogates are also rejected rather than replaced during UTF-8\noutput; valid supplementary characters, such as emoji, remain supported.\n\nCells are plain text, not Markdown or HTML. The builder encodes syntax characters\nso literal pipes, backslashes, backticks and markup stay in their original fields.\nEach CRLF, bare CR or LF becomes a space; text around line breaks is retained.\nOther whitespace and literal punctuation are preserved in the rendered cells.\nThe source spec is not modified. An ordinary valid schedule retains its six\ncolumns; malformed input is never silently replaced with an empty schedule.\n\n### Role table\n\n`spec.role` selects three strings: the standing-arrangement clause, the fee\nsection title, and the fee clause opener.\n\n| Role | Who pays | Shape of the clause |\n| --- | --- | --- |\n| buyer | The counterparty pays on transactions with introduced parties | Counterparty appoints us on a non-exclusive basis to source and introduce |\n| supplier | The counterparty pays on transactions with introduced parties; where we buy as principal we contract on the schedule terms | Counterparty offers capacity to us and to buyers we introduce |\n| mutual | Whoever closes with the other's introduction pays | Each party may introduce; the closing party pays |\n\nUnknown roles are rejected at build time.\n\n### Build\n\nUse operator-reviewed templates and specs only. Ordinary template substitutions\noutside Schedule A are markup-capable, not a sanitizer for untrusted documents.\nPandoc can read referenced local or remote resources; this generator does not\nsandbox the converter's filesystem or network access. Review those references\nand run conversion in your own appropriately restricted environment. The focused\ntests use a synthetic converter and do not certify real DOCX layout or isolation.\n\n```sh\nnode skills\u002Fmaster-agreement-generator\u002Fscripts\u002Fbuild-agreement.js \\\n  skills\u002Fmaster-agreement-generator\u002Freferences\u002Fmaster-template.example.md \\\n  specs\u002FAcmeSupplier.json \\\n  out\u002F\n```\n\nThe script fills placeholders, renders the schedule table, and writes\n`out\u002F\u003Cfile> MASTER.md` with a mandatory DRAFT notice. By default (or with\n`--require-docx`) it requires installed pandoc to produce a nonempty regular\n`.docx` artifact. Missing pandoc, failed conversion or missing\u002Fempty output\nreturns exit code 1. Each pandoc probe or conversion is bounded to ten seconds.\nUnknown, duplicate or conflicting flags return exit code 2.\n\nUse `--markdown-only` explicitly for a successful Markdown-only draft. This mode\nnever probes or invokes pandoc, returns `docxSkipped: true` from the library,\nand provides no DOCX for an e-sign workflow. Library callers must pass\n`{ markdownOnly: true }`; `{ pandoc: false }` alone now fails the DOCX requirement.\nThe result always reports `documentStatus: 'draft'`. Existing generated DOCX is\nremoved when rebuilding its Markdown, and failed conversion leaves no partial\nDOCX, so an earlier artifact cannot masquerade as the current output. Keep\nboth generated files out of version control; the template and specs are source.\n\nThere is no execution-copy mode. The example deliberately contains unresolved\nbracketed drafting directives; filling `{{PLACEHOLDER}}` tokens does not complete\nthose legal provisions. Before preparing an execution document, obtain separate\nreview of the completed clauses, party details, authorized signer, commercial\nterms and exact document version. Preserve the draft and the reviewed execution\ncopy as distinct records. Even a successful DOCX conversion does not authorize an\nupload, send or signature. See the esign-field-placement approval workflow.\n\nBoth output destinations must be direct children of the resolved output directory.\nAn existing symlink at either destination, including a dangling link, is rejected\nbefore either artifact is written, even when DOCX conversion is disabled. Ordinary\nregular files can be rebuilt. Use an output directory you control; these checks\ndo not provide isolation against concurrent hostile filesystem changes. Returned\nartifact paths are absolute.\n\n### Signature page geometry\n\nThe template ends the body with an OpenXML page break so the signature block\nrequests a fresh page in a compatible DOCX renderer:\n\n````markdown\n```{=openxml}\n\u003Cw:p>\u003Cw:r>\u003Cw:br w:type=\"page\"\u002F>\u003C\u002Fw:r>\u003C\u002Fw:p>\n```\n````\n\nThe signature page structure (our block, then the counterparty block, each with\nBy, Name, Title, Email, Date) is consistent, but pagination can change with text,\nfonts, renderer or format. Inspect the actual reviewed document and its page\ngeometry before placing fields; see the esign-field-placement skill.\n\n### Schedule A append workflow\n\nUse the executed agreement's actual authority and notice requirements:\n\n1. Review opportunity economics and negotiation strategy in an **internal**\n   negotiation\u002Fapproval channel. Obtain commitment approval before sending\n   contractual content. A shared counterparty channel is not an internal channel.\n2. Confirm that the proposed entry, role, terms, fee and effective date fall\n   within the agreement's express Schedule A notice authority. Changes to\n   standing terms, or variations outside that authority, require the applicable\n   amendment procedure; a notice cannot create its own exception.\n3. Draft an approved, counterparty-specific dated notice for the recipient and\n   notice channel authorized by the executed agreement. Include useful business\n   content: the protected counterparty or lot, authorized role, commercial terms\n   and applicable fee. Exclude internal margins, negotiation strategy, other\n   parties' economics, system traces, raw errors and internal filing notices.\n4. File the exact notice for operator approval before sending; see\n   operator-approval-loop. Preserve silence in the counterparty channel while\n   approval or participation authority is absent. Approval is distinct from\n   evidence that an authorized sender actually delivered the notice.\n5. Record the authorized delivery evidence, effective date and any objection\n   under the executed agreement's actual requirements. Example periods are not\n   defaults. Keep the executed document immutable; update the tracked schedule\n   record and rebuild a **draft consolidated view** for internal review, with a\n   reference to the executed version and approved notice. This rebuild does not\n   replace the signed agreement or prove legal effect.\n\n## Examples\n\n### Notice text\n\nIllustrative draft only: use these terms and dates solely when the executed\nagreement authorizes them and the operator approves this exact recipient notice.\n\n```text\nSchedule A notice, 2026-09-02\nAgreement: Master Agreement dated 2026-08-14 between Us and Acme\nEntry 2: Lot B, 8 nodes, region EU-West\nRole: introducer\nTerms: 6 month term, start no later than 2026-10-01\nFee: standard\nThis entry takes effect today unless you object within ten business days\nwith dated written evidence of a prior relationship with the counterparty.\n```\n\n### Adding the entry to the spec\n\n```json\n\"schedule\": [\n  [\"1\", \"2026-08-20\", \"Lot A (16 nodes)\", \"introducer\", \"12 months\", \"standard\"],\n  [\"2\", \"2026-09-02\", \"Lot B (8 nodes, EU-West)\", \"introducer\", \"6 months\", \"standard\"]\n]\n```\n\nRebuild, diff the draft Markdown, and attach the consolidated draft to the\ninternal record alongside the unchanged executed document and notice evidence.\n\n### Counterparty fills its own details at signing\n\nFor drafting, omit `legal`, `juris`, `addr`, `signer`, `title`, `email` from the\nspec to render blank lines. A separately reviewed execution workflow must decide\nwhich details may be completed by the counterparty and verify the actual fields;\nthe generator does not create or approve an e-sign envelope.\n","# Master Agreement Generator\n\nOne master template, one small spec per counterparty, one draft build step.\nThe generator always labels output **DRAFT**, including documents generated\nfrom a completed template. A successful conversion proves artifact generation,\nnot legal completeness, authority to contract, or readiness to send or sign.\nAn executed agreement may permit designated opportunities to be added by notice;\nthat authority must be established before using the Schedule A workflow.\n\n## When to Use\n\n- You issue a framework agreement (NDA, referral or sourcing fee,\n  non-circumvention, master services) to many counterparties with the same\n  terms and a few party-specific fields.\n- Deals are added over time and re-papering each one is the bottleneck.\n- Documents must be reproducible from tracked source, diffable, and free of\n  hand edits.\n- Signature fields are placed by automation and need a stable page layout.\n\n## How It Works\n\n### Template\n\nA single markdown template with `{{PLACEHOLDER}}` fields. Every party-specific\nvalue is a placeholder; everything else is fixed text. A skeleton lives at\n[references\u002Fmaster-template.example.md](references\u002Fmaster-template.example.md).\nReplace its generic sentences with your counsel-approved clauses.\n\nPlaceholders the reference script fills:\n\n| Placeholder | Source |\n| --- | --- |\n| `{{DATE}}` | `spec.date`, default today |\n| `{{CP_SHORT}}` | `spec.short` |\n| `{{CP_LEGAL}}`, `{{CP_JURIS}}`, `{{CP_ADDR}}` | spec fields, or a blank line when the counterparty completes them at signing |\n| `{{ROLE_CLAUSE}}`, `{{FEE_TITLE}}`, `{{FEE_CLAUSE}}` | selected by `spec.role` from the role table |\n| `{{SCHEDULE_ROWS}}` | `spec.schedule`, or one \"no entries at signing\" row |\n| `{{SUPPLEMENT_CLAUSE}}` | `spec.supplement`, rendered with a trailing separator or empty |\n| `{{CP_SIGBLOCK}}`, `{{CP_SIGNER}}`, `{{CP_TITLE}}`, `{{CP_EMAIL}}` | signature block fields, blanks when unknown |\n\n### Spec\n\nOne JSON file per counterparty:\n\n```json\n{\n  \"file\": \"AcmeSupplier\",\n  \"short\": \"Acme\",\n  \"role\": \"supplier\",\n  \"legal\": \"Acme Compute Ltd\",\n  \"juris\": \"England and Wales company\",\n  \"addr\": \"1 Example Street, London\",\n  \"signer\": \"A. Person\",\n  \"title\": \"Director\",\n  \"email\": \"signer@example.com\",\n  \"schedule\": [[\"1\", \"2026-09-01\", \"Lot A (16 nodes)\", \"introducer\", \"12 months\", \"standard\"]],\n  \"supplement\": \"the Data Processing Addendum dated 2026-09-01\"\n}\n```\n\nOnly `file`, `short`, and `role` are required for a draft. Missing signature fields\nrender as blank lines for review and completion. See\n[references\u002Fspec.example.json](references\u002Fspec.example.json).\n\n`file` must be a nonempty portable filename, such as `AcmeSupplier` or\n`Acme Supplier`, without directory components. The builder rejects either path\nseparator, drive\u002FUNC syntax, control characters, Windows-reserved punctuation\nor device names, and trailing dots or spaces. Invalid names are rejected without\nsanitizing or renaming them, before creating output or invoking pandoc.\n\nOmit `schedule` or use `[]` for the “no entries at signing” placeholder. A supplied\nschedule must otherwise be a dense array of six-cell arrays, in this order:\nnumber, date, protected counterparty or lot, role, terms, fee. Each cell must be\na valid Unicode string or finite number; empty strings are allowed for intentional blanks.\nNulls, booleans, objects, nested cell arrays, missing cells and non-finite numbers\nare rejected with a row\u002Fcell index before any artifact write or pandoc activity.\nUnpaired UTF-16 surrogates are also rejected rather than replaced during UTF-8\noutput; valid supplementary characters, such as emoji, remain supported.\n\nCells are plain text, not Markdown or HTML. The builder encodes syntax characters\nso literal pipes, backslashes, backticks and markup stay in their original fields.\nEach CRLF, bare CR or LF becomes a space; text around line breaks is retained.\nOther whitespace and literal punctuation are preserved in the rendered cells.\nThe source spec is not modified. An ordinary valid schedule retains its six\ncolumns; malformed input is never silently replaced with an empty schedule.\n\n### Role table\n\n`spec.role` selects three strings: the standing-arrangement clause, the fee\nsection title, and the fee clause opener.\n\n| Role | Who pays | Shape of the clause |\n| --- | --- | --- |\n| buyer | The counterparty pays on transactions with introduced parties | Counterparty appoints us on a non-exclusive basis to source and introduce |\n| supplier | The counterparty pays on transactions with introduced parties; where we buy as principal we contract on the schedule terms | Counterparty offers capacity to us and to buyers we introduce |\n| mutual | Whoever closes with the other's introduction pays | Each party may introduce; the closing party pays |\n\nUnknown roles are rejected at build time.\n\n### Build\n\nUse operator-reviewed templates and specs only. Ordinary template substitutions\noutside Schedule A are markup-capable, not a sanitizer for untrusted documents.\nPandoc can read referenced local or remote resources; this generator does not\nsandbox the converter's filesystem or network access. Review those references\nand run conversion in your own appropriately restricted environment. The focused\ntests use a synthetic converter and do not certify real DOCX layout or isolation.\n\n```sh\nnode skills\u002Fmaster-agreement-generator\u002Fscripts\u002Fbuild-agreement.js \\\n  skills\u002Fmaster-agreement-generator\u002Freferences\u002Fmaster-template.example.md \\\n  specs\u002FAcmeSupplier.json \\\n  out\u002F\n```\n\nThe script fills placeholders, renders the schedule table, and writes\n`out\u002F\u003Cfile> MASTER.md` with a mandatory DRAFT notice. By default (or with\n`--require-docx`) it requires installed pandoc to produce a nonempty regular\n`.docx` artifact. Missing pandoc, failed conversion or missing\u002Fempty output\nreturns exit code 1. Each pandoc probe or conversion is bounded to ten seconds.\nUnknown, duplicate or conflicting flags return exit code 2.\n\nUse `--markdown-only` explicitly for a successful Markdown-only draft. This mode\nnever probes or invokes pandoc, returns `docxSkipped: true` from the library,\nand provides no DOCX for an e-sign workflow. Library callers must pass\n`{ markdownOnly: true }`; `{ pandoc: false }` alone now fails the DOCX requirement.\nThe result always reports `documentStatus: 'draft'`. Existing generated DOCX is\nremoved when rebuilding its Markdown, and failed conversion leaves no partial\nDOCX, so an earlier artifact cannot masquerade as the current output. Keep\nboth generated files out of version control; the template and specs are source.\n\nThere is no execution-copy mode. The example deliberately contains unresolved\nbracketed drafting directives; filling `{{PLACEHOLDER}}` tokens does not complete\nthose legal provisions. Before preparing an execution document, obtain separate\nreview of the completed clauses, party details, authorized signer, commercial\nterms and exact document version. Preserve the draft and the reviewed execution\ncopy as distinct records. Even a successful DOCX conversion does not authorize an\nupload, send or signature. See the esign-field-placement approval workflow.\n\nBoth output destinations must be direct children of the resolved output directory.\nAn existing symlink at either destination, including a dangling link, is rejected\nbefore either artifact is written, even when DOCX conversion is disabled. Ordinary\nregular files can be rebuilt. Use an output directory you control; these checks\ndo not provide isolation against concurrent hostile filesystem changes. Returned\nartifact paths are absolute.\n\n### Signature page geometry\n\nThe template ends the body with an OpenXML page break so the signature block\nrequests a fresh page in a compatible DOCX renderer:\n\n````markdown\n```{=openxml}\n\u003Cw:p>\u003Cw:r>\u003Cw:br w:type=\"page\"\u002F>\u003C\u002Fw:r>\u003C\u002Fw:p>\n```\n````\n\nThe signature page structure (our block, then the counterparty block, each with\nBy, Name, Title, Email, Date) is consistent, but pagination can change with text,\nfonts, renderer or format. Inspect the actual reviewed document and its page\ngeometry before placing fields; see the esign-field-placement skill.\n\n### Schedule A append workflow\n\nUse the executed agreement's actual authority and notice requirements:\n\n1. Review opportunity economics and negotiation strategy in an **internal**\n   negotiation\u002Fapproval channel. Obtain commitment approval before sending\n   contractual content. A shared counterparty channel is not an internal channel.\n2. Confirm that the proposed entry, role, terms, fee and effective date fall\n   within the agreement's express Schedule A notice authority. Changes to\n   standing terms, or variations outside that authority, require the applicable\n   amendment procedure; a notice cannot create its own exception.\n3. Draft an approved, counterparty-specific dated notice for the recipient and\n   notice channel authorized by the executed agreement. Include useful business\n   content: the protected counterparty or lot, authorized role, commercial terms\n   and applicable fee. Exclude internal margins, negotiation strategy, other\n   parties' economics, system traces, raw errors and internal filing notices.\n4. File the exact notice for operator approval before sending; see\n   operator-approval-loop. Preserve silence in the counterparty channel while\n   approval or participation authority is absent. Approval is distinct from\n   evidence that an authorized sender actually delivered the notice.\n5. Record the authorized delivery evidence, effective date and any objection\n   under the executed agreement's actual requirements. Example periods are not\n   defaults. Keep the executed document immutable; update the tracked schedule\n   record and rebuild a **draft consolidated view** for internal review, with a\n   reference to the executed version and approved notice. This rebuild does not\n   replace the signed agreement or prove legal effect.\n\n## Examples\n\n### Notice text\n\nIllustrative draft only: use these terms and dates solely when the executed\nagreement authorizes them and the operator approves this exact recipient notice.\n\n```text\nSchedule A notice, 2026-09-02\nAgreement: Master Agreement dated 2026-08-14 between Us and Acme\nEntry 2: Lot B, 8 nodes, region EU-West\nRole: introducer\nTerms: 6 month term, start no later than 2026-10-01\nFee: standard\nThis entry takes effect today unless you object within ten business days\nwith dated written evidence of a prior relationship with the counterparty.\n```\n\n### Adding the entry to the spec\n\n```json\n\"schedule\": [\n  [\"1\", \"2026-08-20\", \"Lot A (16 nodes)\", \"introducer\", \"12 months\", \"standard\"],\n  [\"2\", \"2026-09-02\", \"Lot B (8 nodes, EU-West)\", \"introducer\", \"6 months\", \"standard\"]\n]\n```\n\nRebuild, diff the draft Markdown, and attach the consolidated draft to the\ninternal record alongside the unchanged executed document and notice evidence.\n\n### Counterparty fills its own details at signing\n\nFor drafting, omit `legal`, `juris`, `addr`, `signer`, `title`, `email` from the\nspec to render blank lines. A separately reviewed execution workflow must decide\nwhich details may be completed by the counterparty and verify the actual fields;\nthe generator does not create or approve an e-sign envelope.\n",{"name":5,"description":7},"main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fmaster-agreement-generator","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill master-agreement-generator",{"tool":37,"command":38},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill master-agreement-generator",{"tool":40,"command":41},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill master-agreement-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmaster-agreement-generator\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fmaster-template.example.md","REFERENCE","参考文档",4256,"https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmaster-agreement-generator\u002Freferences\u002Fmaster-template.example.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fspec.example.json",460,"https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmaster-agreement-generator\u002Freferences\u002Fspec.example.json",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fbuild-agreement.js","SCRIPT","脚本",9597,"https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fmaster-agreement-generator\u002Fscripts\u002Fbuild-agreement.js",[62,68,74,80,86,92],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]