[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BMEAFHQ111G5VN7A4G2J7":3,"skill-same:01M75BMEAFHQ111G5VN7A4G2J7":48},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75BMEAFHQ111G5VN7A4G2J7","amendment-history",null,"Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says \"what changed in this contract over time\", \"show me the amendment history\", \"where's the latest [clause]\", \"how has [provision] evolved\", or uploads multiple versions of an agreement.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Famendment-history\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: amendment-history\ndescription: >\n  Trace how a contract has changed across its base agreement and all amendments —\n  either a summary of all changes over time, or a provision trace for a specific\n  clause. Use when the user says \"what changed in this contract over time\", \"show\n  me the amendment history\", \"where's the latest [clause]\", \"how has [provision]\n  evolved\", or uploads multiple versions of an agreement.\nargument-hint: \"[file(s) | [CLM ID (coming soon)] | [repository link (coming soon)]] [--provision \u003Cclause name>]\"\n---\n\n# \u002Famendment-history\n\nLoads a base agreement and all amendments, then either summarizes what\nchanged over time or traces a specific provision to its current\ncontrolling language.\n\n## Instructions\n\n1. **Get the documents:** From file upload, [CLM ID (coming soon)], or [repository link (coming soon)]. Accept multiple files in one invocation. If none\n   provided, ask.\n\n2. **Detect the mode** by parsing the request per the mode\n   detection rules below. If a provision name is clearly stated, go straight\n   to Mode 2. If no provision is mentioned, run Mode 1. Ask only if\n   genuinely ambiguous.\n\n3. **Run the workflow below.** Follow it fully.\n\n4. **Offer follow-ups after output:**\n   - \"Want me to trace another provision?\"\n   - \"Want a full playbook review of the current agreement as amended?\"\n     (routes to vendor-agreement-review)\n   - \"Want a stakeholder summary of the key changes?\"\n     (routes to stakeholder-summary)\n\n## Examples\n\n```\n\u002Fcommercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf\n```\n\n```\n\u002Fcommercial-legal:amendment-history --provision indemnity\n```\n\n```\n\u002Fcommercial-legal:amendment-history\n[paste agreement and amendment text]\n```\n\n---\n\n## Matter context\n\n**Matter context.** Check `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗` (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: \"Which matter is this for? Run `\u002Fcommercial-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nContracts accumulate amendments. By the third amendment, nobody remembers\nwhat the original said or which version of a clause controls. This skill\nreads the base agreement and all amendments in chronological order and\neither summarizes what changed across the whole contract or traces a\nspecific provision through every version to find the current controlling\nlanguage.\n\n## Mode detection\n\nParse the user's request to determine which mode to run. Do not ask\nwhich mode unless the request is genuinely ambiguous.\n\n**Mode 1 — Summary** (no specific provision mentioned)\nTrigger phrases: \"what changed\", \"amendment history\", \"show me changes\nover time\", \"summarize amendments\", \"what does this contract look like now\"\n\n**Mode 2 — Provision trace** (specific clause or topic named)\nTrigger phrases: \"where's the [clause]\", \"latest [provision]\", \"how did\n[term] change\", \"find the indemnity\", \"what does it say now about [topic]\"\n\nCommon provision mappings:\n- \"indemnity\" \u002F \"indemnification\" → indemnification section\n- \"liability\" \u002F \"liability cap\" → limitation of liability\n- \"termination\" → term and termination\n- \"data\" \u002F \"privacy\" \u002F \"DPA\" → data protection provisions\n- \"IP\" \u002F \"intellectual property\" → IP ownership and licenses\n- \"price\" \u002F \"fees\" \u002F \"payment\" → payment terms\n- \"auto-renewal\" \u002F \"renewal\" → renewal mechanics\n\nIf the term is ambiguous and maps to more than one provision, list the\ncandidates and ask which one:\n> \"I found [N] provisions related to [term] — [list them]. Which one?\"\n\nIf the overall request is ambiguous between modes, ask one question:\n> \"Summary of all changes across the contract, or trace a specific\n> provision — like indemnity, liability, or termination?\"\n\n---\n\n## Step 1: Load and order the documents\n\nAccept documents from any of these sources:\n\n**[CLM integration coming soon] (if connected):**\nSearch by counterparty name or agreement title. Pull the base agreement\nand all amendments. Record metadata typically includes execution dates —\nuse these to establish chronological order.\n\n**[Document repository integration coming soon] (if connected):**\nSearch by counterparty name or filename. Look for files matching patterns\nlike \"Amendment\", \"Addendum\", \"Amendment No. 1\", \"First Amendment\", or\nnumbered suffixes. Pull all matches and sort by file date or filename\nnumbering.\n\n**Direct upload:**\nUser provides files directly. In most cases the ordering is\nself-explanatory from document titles (e.g., \"Amendment No. 1\",\n\"Second Amendment\", \"Addendum A\") or dates visible in the filename\nor document header — proceed without asking.\n\nOnly ask the user to confirm ordering if:\n- Filenames give no indication of sequence (e.g., \"agreement-final.pdf\",\n  \"agreement-v2.pdf\", \"agreement-markup.pdf\")\n- Dates are absent from both filenames and document headers\n- Two documents appear to be the same amendment version\n\nIf ordering was inferred rather than confirmed, note confidence at the\ntop of the output only where uncertain:\n> \"Order inferred from document titles — one item I was less certain\n> about: [specific document]. Confirm if this affects your review.\"\n\n**Ordering rules:**\n- Always establish chronological order before reading content.\n- If execution dates are available in metadata, use them.\n- If not, look for dates in the document header or recitals\n  (\"This Amendment, dated as of...\").\n- Amendments often reference the agreement they modify (\"this Amendment\n  to the Master Services Agreement dated [X]\") — use these references\n  to confirm the chain.\n\n---\n\n## Privilege inheritance\n\nThis skill reads the base agreement and amendments — often privileged or confidential in their own right, and typically used for privileged analysis. The output inherits the source's privilege and confidentiality status. Prepend the work-product header from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` `## Outputs` to every output below, distribute only within the privilege circle, and store it where privileged materials live. Strip the header before any external delivery.\n\n## Step 2: Read and index\n\nRead each document in chronological order. For each, extract:\n- Document type (base agreement, amendment number, addendum, etc.)\n- Execution date\n- Parties (confirm they match across documents — flag if a new party\n  was added or a party name changed)\n- A list of provisions explicitly modified, added, or deleted\n\nBuild a working index before producing output. Use it internally to\ndrive the output — do not show it to the user.\n\n---\n\n## Mode 1: Summary of all changes\n\n### Section reference rule\n\nEvery finding must include an inline section reference so the reader\ncan verify against the source document without searching:\n\n  \"Termination for convenience (§12.3): Added. Customer may terminate\n  on 90 days written notice with no fee after the initial term.\"\n\nIf a provision spans multiple sections or the section number changed\nacross amendments, cite all references:\n  \"Indemnification (§9.1 base; §9.1 restated in Amendment 5)\"\n\n### Output format\n\n```markdown\n# Amendment History: [Counterparty] — [Agreement type]\n\n**Base agreement:** [date]\n**Amendments:** [N] ([date of first] → [date of last])\n**Last amended:** [date]\n\n---\n\n## What changed — chronological\n\n### Amendment 1 — [date]\n**Purpose:** [one sentence — why this amendment existed, from recitals\nor clear from context. If not stated, omit rather than guess.]\n\n**Material changes:**\n- [Provision] (§[X.X]): [what it said before → what it says now,\n  in plain English]\n- [New provision added] (§[X.X]): [what it does]\n- [Provision deleted] (§[X.X]): [what was removed and why it matters]\n\n### Amendment 2 — [date]\n[same structure]\n\n[repeat for each amendment]\n\n---\n\n## Net current state\n\n| Provision | Current position | §Ref | Last changed |\n|---|---|---|---|\n| [clause] | [plain English summary] | §[X.X] | Amendment N, [date] |\n| [clause] | [unchanged from base] | §[X.X] | Base agreement |\n\n---\n\n## Watch items\n[Flag anything that looks inconsistent — e.g., an amendment modifying\na provision that was already deleted, contradictory language between\namendments, a party name that changed without a formal assignment,\nor a provision where the section number shifted across documents.\nInclude section references on every flag.]\n```\n\n---\n\n## Mode 2: Provision trace\n\n### Output format\n\nShow only what changed. Do not list amendments where the provision\nwas untouched — skip them entirely.\n\n```markdown\n# Provision Trace: [Provision name]\n## [Counterparty] — [Agreement type]\n\n---\n\n### Original — [Base agreement date], §[X.X]\n> \"[exact quote]\"\n\n*Plain English:* [one sentence]\n\n---\n\n### Amendment [N] — [date], §[X.X]\n\n**Was:**\n> \"[exact quote of prior language]\"\n\n**Now:**\n> \"[exact quote of replacement language]\"\n\n*What changed:* [one sentence — practical effect on the parties]\n\n---\n\n[Only subsequent amendments that touched this provision appear here.\nAll others are omitted.]\n\n---\n\n## Current controlling language\n\n**§[X.X] — [source document, date]**\n> \"[exact quote]\"\n\n*Plain English:* [one sentence]\n\n---\n\n## Watch items\n[Flags, inconsistencies, open questions — with section references.\nCommon items to check: whether the provision is subject to or carved\nout of the liability cap; whether the section number shifted across\namendments; whether the amendment language conflicts with another\nprovision.]\n```\n\nIf the provision was never amended after the base agreement:\n> \"This provision has not been modified by any amendment. Original\n> language controls. §[X.X], base agreement, [date].\"\n\n---\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- It does not determine which document controls in the event of a\n  conflict between the base agreement and an amendment — that is a\n  legal interpretation question. It flags conflicts and routes to Legal.\n- It does not draft new amendments.\n- It does not compare against the playbook in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` — that is the\n  vendor-agreement-review skill's job. This skill is purely historical.\n- It does not infer what an amendment means if the language is\n  ambiguous — it quotes exactly and flags ambiguity for Legal.\n","# \u002Famendment-history\n\nLoads a base agreement and all amendments, then either summarizes what\nchanged over time or traces a specific provision to its current\ncontrolling language.\n\n## Instructions\n\n1. **Get the documents:** From file upload, [CLM ID (coming soon)], or [repository link (coming soon)]. Accept multiple files in one invocation. If none\n   provided, ask.\n\n2. **Detect the mode** by parsing the request per the mode\n   detection rules below. If a provision name is clearly stated, go straight\n   to Mode 2. If no provision is mentioned, run Mode 1. Ask only if\n   genuinely ambiguous.\n\n3. **Run the workflow below.** Follow it fully.\n\n4. **Offer follow-ups after output:**\n   - \"Want me to trace another provision?\"\n   - \"Want a full playbook review of the current agreement as amended?\"\n     (routes to vendor-agreement-review)\n   - \"Want a stakeholder summary of the key changes?\"\n     (routes to stakeholder-summary)\n\n## Examples\n\n```\n\u002Fcommercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf\n```\n\n```\n\u002Fcommercial-legal:amendment-history --provision indemnity\n```\n\n```\n\u002Fcommercial-legal:amendment-history\n[paste agreement and amendment text]\n```\n\n---\n\n## Matter context\n\n**Matter context.** Check `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗` (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: \"Which matter is this for? Run `\u002Fcommercial-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nContracts accumulate amendments. By the third amendment, nobody remembers\nwhat the original said or which version of a clause controls. This skill\nreads the base agreement and all amendments in chronological order and\neither summarizes what changed across the whole contract or traces a\nspecific provision through every version to find the current controlling\nlanguage.\n\n## Mode detection\n\nParse the user's request to determine which mode to run. Do not ask\nwhich mode unless the request is genuinely ambiguous.\n\n**Mode 1 — Summary** (no specific provision mentioned)\nTrigger phrases: \"what changed\", \"amendment history\", \"show me changes\nover time\", \"summarize amendments\", \"what does this contract look like now\"\n\n**Mode 2 — Provision trace** (specific clause or topic named)\nTrigger phrases: \"where's the [clause]\", \"latest [provision]\", \"how did\n[term] change\", \"find the indemnity\", \"what does it say now about [topic]\"\n\nCommon provision mappings:\n- \"indemnity\" \u002F \"indemnification\" → indemnification section\n- \"liability\" \u002F \"liability cap\" → limitation of liability\n- \"termination\" → term and termination\n- \"data\" \u002F \"privacy\" \u002F \"DPA\" → data protection provisions\n- \"IP\" \u002F \"intellectual property\" → IP ownership and licenses\n- \"price\" \u002F \"fees\" \u002F \"payment\" → payment terms\n- \"auto-renewal\" \u002F \"renewal\" → renewal mechanics\n\nIf the term is ambiguous and maps to more than one provision, list the\ncandidates and ask which one:\n> \"I found [N] provisions related to [term] — [list them]. Which one?\"\n\nIf the overall request is ambiguous between modes, ask one question:\n> \"Summary of all changes across the contract, or trace a specific\n> provision — like indemnity, liability, or termination?\"\n\n---\n\n## Step 1: Load and order the documents\n\nAccept documents from any of these sources:\n\n**[CLM integration coming soon] (if connected):**\nSearch by counterparty name or agreement title. Pull the base agreement\nand all amendments. Record metadata typically includes execution dates —\nuse these to establish chronological order.\n\n**[Document repository integration coming soon] (if connected):**\nSearch by counterparty name or filename. Look for files matching patterns\nlike \"Amendment\", \"Addendum\", \"Amendment No. 1\", \"First Amendment\", or\nnumbered suffixes. Pull all matches and sort by file date or filename\nnumbering.\n\n**Direct upload:**\nUser provides files directly. In most cases the ordering is\nself-explanatory from document titles (e.g., \"Amendment No. 1\",\n\"Second Amendment\", \"Addendum A\") or dates visible in the filename\nor document header — proceed without asking.\n\nOnly ask the user to confirm ordering if:\n- Filenames give no indication of sequence (e.g., \"agreement-final.pdf\",\n  \"agreement-v2.pdf\", \"agreement-markup.pdf\")\n- Dates are absent from both filenames and document headers\n- Two documents appear to be the same amendment version\n\nIf ordering was inferred rather than confirmed, note confidence at the\ntop of the output only where uncertain:\n> \"Order inferred from document titles — one item I was less certain\n> about: [specific document]. Confirm if this affects your review.\"\n\n**Ordering rules:**\n- Always establish chronological order before reading content.\n- If execution dates are available in metadata, use them.\n- If not, look for dates in the document header or recitals\n  (\"This Amendment, dated as of...\").\n- Amendments often reference the agreement they modify (\"this Amendment\n  to the Master Services Agreement dated [X]\") — use these references\n  to confirm the chain.\n\n---\n\n## Privilege inheritance\n\nThis skill reads the base agreement and amendments — often privileged or confidential in their own right, and typically used for privileged analysis. The output inherits the source's privilege and confidentiality status. Prepend the work-product header from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` `## Outputs` to every output below, distribute only within the privilege circle, and store it where privileged materials live. Strip the header before any external delivery.\n\n## Step 2: Read and index\n\nRead each document in chronological order. For each, extract:\n- Document type (base agreement, amendment number, addendum, etc.)\n- Execution date\n- Parties (confirm they match across documents — flag if a new party\n  was added or a party name changed)\n- A list of provisions explicitly modified, added, or deleted\n\nBuild a working index before producing output. Use it internally to\ndrive the output — do not show it to the user.\n\n---\n\n## Mode 1: Summary of all changes\n\n### Section reference rule\n\nEvery finding must include an inline section reference so the reader\ncan verify against the source document without searching:\n\n  \"Termination for convenience (§12.3): Added. Customer may terminate\n  on 90 days written notice with no fee after the initial term.\"\n\nIf a provision spans multiple sections or the section number changed\nacross amendments, cite all references:\n  \"Indemnification (§9.1 base; §9.1 restated in Amendment 5)\"\n\n### Output format\n\n```markdown\n# Amendment History: [Counterparty] — [Agreement type]\n\n**Base agreement:** [date]\n**Amendments:** [N] ([date of first] → [date of last])\n**Last amended:** [date]\n\n---\n\n## What changed — chronological\n\n### Amendment 1 — [date]\n**Purpose:** [one sentence — why this amendment existed, from recitals\nor clear from context. If not stated, omit rather than guess.]\n\n**Material changes:**\n- [Provision] (§[X.X]): [what it said before → what it says now,\n  in plain English]\n- [New provision added] (§[X.X]): [what it does]\n- [Provision deleted] (§[X.X]): [what was removed and why it matters]\n\n### Amendment 2 — [date]\n[same structure]\n\n[repeat for each amendment]\n\n---\n\n## Net current state\n\n| Provision | Current position | §Ref | Last changed |\n|---|---|---|---|\n| [clause] | [plain English summary] | §[X.X] | Amendment N, [date] |\n| [clause] | [unchanged from base] | §[X.X] | Base agreement |\n\n---\n\n## Watch items\n[Flag anything that looks inconsistent — e.g., an amendment modifying\na provision that was already deleted, contradictory language between\namendments, a party name that changed without a formal assignment,\nor a provision where the section number shifted across documents.\nInclude section references on every flag.]\n```\n\n---\n\n## Mode 2: Provision trace\n\n### Output format\n\nShow only what changed. Do not list amendments where the provision\nwas untouched — skip them entirely.\n\n```markdown\n# Provision Trace: [Provision name]\n## [Counterparty] — [Agreement type]\n\n---\n\n### Original — [Base agreement date], §[X.X]\n> \"[exact quote]\"\n\n*Plain English:* [one sentence]\n\n---\n\n### Amendment [N] — [date], §[X.X]\n\n**Was:**\n> \"[exact quote of prior language]\"\n\n**Now:**\n> \"[exact quote of replacement language]\"\n\n*What changed:* [one sentence — practical effect on the parties]\n\n---\n\n[Only subsequent amendments that touched this provision appear here.\nAll others are omitted.]\n\n---\n\n## Current controlling language\n\n**§[X.X] — [source document, date]**\n> \"[exact quote]\"\n\n*Plain English:* [one sentence]\n\n---\n\n## Watch items\n[Flags, inconsistencies, open questions — with section references.\nCommon items to check: whether the provision is subject to or carved\nout of the liability cap; whether the section number shifted across\namendments; whether the amendment language conflicts with another\nprovision.]\n```\n\nIf the provision was never amended after the base agreement:\n> \"This provision has not been modified by any amendment. Original\n> language controls. §[X.X], base agreement, [date].\"\n\n---\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- It does not determine which document controls in the event of a\n  conflict between the base agreement and an amendment — that is a\n  legal interpretation question. It flags conflicts and routes to Legal.\n- It does not draft new amendments.\n- It does not compare against the playbook in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` — that is the\n  vendor-agreement-review skill's job. This skill is purely historical.\n- It does not infer what an amendment means if the language is\n  ambiguous — it quotes exactly and flags ambiguity for Legal.\n",{"name":5,"description":23,"argument-hint":24},"Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says \"what changed in this contract over time\", \"show me the amendment history\", \"where's the latest [clause]\", \"how has [provision] evolved\", or uploads multiple versions of an agreement.\n","[file(s) | [CLM ID (coming soon)] | [repository link (coming soon)]] [--provision \u003Cclause name>]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Famendment-history",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agisota\u002Fold-one --skill amendment-history",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill amendment-history",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill amendment-history","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Famendment-history\u002FSKILL.md",true,[],[49,56,63,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]