[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BKKNXM8ND167E4YFSM2SF":3,"skill-same:01M75BKKNXM8ND167E4YFSM2SF":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75BKKNXM8ND167E4YFSM2SF","ai-tool-handoff",null,"Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. Use when user says \"send to Luminance\", \"bulk review\", \"AI extraction\", or when diligence-issue-extraction hits a high-volume category.","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\u002Fai-tool-handoff\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ai-tool-handoff\ndescription: >\n  Detects when Luminance, Kira, or a similar bulk-review tool is in use,\n  hands off the high-volume clause extraction to it, and QAs its output\n  per the trust level in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. Use when user says \"send to Luminance\",\n  \"bulk review\", \"AI extraction\", or when diligence-issue-extraction hits\n  a high-volume category.\n---\n\n# AI Tool Handoff\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 `\u002Fcorporate-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\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nLuminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.\n\nThis skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.\n\n**Before you hand off:** try `tabular-review` first (`\u002Fcorporate-legal:tabular-review`). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance\u002FKira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.\n\n## Load context\n\n`~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → AI-assisted review:\n- Tool in use (Luminance \u002F Kira \u002F none)\n- What it's used for (which clause types)\n- Trust level (use as-is \u002F spot-check \u002F full re-review)\n- Handoff process (who loads, who QAs)\n\nIf `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.\n\n## When to hand off\n\nHand off when all of:\n- Category has >50 documents (below that, faster to just read them)\n- Extraction target is a clause type the tool is good at (CoC, assignment, exclusivity, MFN, termination, auto-renewal)\n- Documents are reasonably uniform (all customer contracts on similar paper — not a mix of contracts, letters, and board minutes)\n\nDon't hand off:\n- Bespoke or heavily negotiated documents\n- Side letters and amendments (context-dependent, tools miss the interaction with the main agreement)\n- Anything where the question is \"what does this mean for the deal\" not \"does this clause exist\"\n\n## The handoff\n\n### Step 1: Prepare the batch\n\n- Identify documents for the batch (from VDR inventory)\n- Specify extraction targets per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (which clause types)\n- Note the materiality threshold so tool output can be filtered\n\n### Step 2: Load (or instruct the loader)\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — who loads. If it's you, generate the load instructions. If it's someone else, generate the request:\n\n```markdown\n## [Tool] Load Request — [Deal code] — [Category]\n\n**Documents:** [N] docs from VDR folder [path]\n**Load to:** [Tool workspace\u002Fmatter]\n**Extraction targets:**\n- Change of control \u002F assignment\n- Exclusivity\n- [etc. per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\n**Filter output:** Flag only where extraction target is present — no need for \"no CoC clause found\" for every doc.\n\n**Return by:** [date]\n```\n\n### Step 3: QA the output\n\nWhen the tool returns results, apply the trust level:\n\n**\"Use as-is\":** Ingest directly into diligence findings. (Only if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says this — it's rare.)\n\n**\"Spot-check X%\":** Randomly sample X% of flagged documents. For each, read the actual clause and compare to the tool's extraction. If error rate is low, accept the batch. If errors found, widen the sample.\n\n**\"Full human review of flagged\":** Tool narrows the universe (500 docs → 80 with CoC clauses). Human reads all 80. Tool saved the time of reading the 420 clean ones.\n\n### Step 4: Judgment layer\n\nThe tool found the clauses. Now apply judgment:\n\nFor each flagged CoC provision: is it actually triggered by this deal?\n- Stock sale vs. asset sale vs. merger — different triggers\n- \"Change of control\" defined how in the contract — majority ownership? board control? something else?\n- Is there a carve-out for this type of transaction?\n\nThis is the part the tool can't do. Output goes to diligence findings in house format.\n\n## Output\n\n> The QA summary below is derived from VDR documents that are privileged, confidential, or both. It inherits the sources' privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Store with the matter's privileged files.\n\n```markdown\n## AI Tool Handoff Summary — [Category]\n\n**Tool:** [Luminance \u002F Kira]\n**Documents processed:** [N]\n**Extraction targets:** [clause types]\n\n### QA\n\n**Trust level:** [per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n**Sample size:** [N] docs spot-checked\n**Error rate:** [X]% — [Accepted \u002F Widened sample \u002F Full re-review triggered]\n\n### Results\n\n| Clause type | Docs flagged | After judgment layer | Material |\n|---|---|---|---|\n| Change of control | [N] | [N actually triggered by deal structure] | [N above threshold] |\n| Assignment | [N] | [N] | [N] |\n\n**→ [N] findings added to diligence issues**\n**→ [N] consents added to closing checklist**\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 doesn't run Luminance or Kira — it manages the handoff and QA. A human (or the tool's own interface) runs the extraction.\n- It doesn't replace the tool's output with its own judgment entirely — if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says spot-check 10%, check 10%, not 100%.\n- It doesn't decide the trust level — that's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`, set at cold-start based on the team's experience with the tool.\n","# AI Tool Handoff\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 `\u002Fcorporate-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\u002Fcorporate-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nLuminance and Kira are good at one thing: reading 500 contracts and finding every change-of-control clause. They're less good at judgment — deciding whether a particular CoC provision is actually triggered by this deal structure.\n\nThis skill hands off the bulk extraction to the right tool, then runs the QA layer on what comes back.\n\n**Before you hand off:** try `tabular-review` first (`\u002Fcorporate-legal:tabular-review`). For anything the user's environment can handle — a few hundred documents, a defined column schema — native tabular review is faster to set up, has no per-document cost, and keeps the work product local. Hand off to Luminance\u002FKira when the corpus is genuinely too large, the team already has a license and workflow, or the matter requires a tool with a validated provenance chain.\n\n## Load context\n\n`~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → AI-assisted review:\n- Tool in use (Luminance \u002F Kira \u002F none)\n- What it's used for (which clause types)\n- Trust level (use as-is \u002F spot-check \u002F full re-review)\n- Handoff process (who loads, who QAs)\n\nIf `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says no AI tool → this skill is a no-op. Everything goes through diligence-issue-extraction directly.\n\n## When to hand off\n\nHand off when all of:\n- Category has >50 documents (below that, faster to just read them)\n- Extraction target is a clause type the tool is good at (CoC, assignment, exclusivity, MFN, termination, auto-renewal)\n- Documents are reasonably uniform (all customer contracts on similar paper — not a mix of contracts, letters, and board minutes)\n\nDon't hand off:\n- Bespoke or heavily negotiated documents\n- Side letters and amendments (context-dependent, tools miss the interaction with the main agreement)\n- Anything where the question is \"what does this mean for the deal\" not \"does this clause exist\"\n\n## The handoff\n\n### Step 1: Prepare the batch\n\n- Identify documents for the batch (from VDR inventory)\n- Specify extraction targets per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (which clause types)\n- Note the materiality threshold so tool output can be filtered\n\n### Step 2: Load (or instruct the loader)\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — who loads. If it's you, generate the load instructions. If it's someone else, generate the request:\n\n```markdown\n## [Tool] Load Request — [Deal code] — [Category]\n\n**Documents:** [N] docs from VDR folder [path]\n**Load to:** [Tool workspace\u002Fmatter]\n**Extraction targets:**\n- Change of control \u002F assignment\n- Exclusivity\n- [etc. per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\n**Filter output:** Flag only where extraction target is present — no need for \"no CoC clause found\" for every doc.\n\n**Return by:** [date]\n```\n\n### Step 3: QA the output\n\nWhen the tool returns results, apply the trust level:\n\n**\"Use as-is\":** Ingest directly into diligence findings. (Only if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says this — it's rare.)\n\n**\"Spot-check X%\":** Randomly sample X% of flagged documents. For each, read the actual clause and compare to the tool's extraction. If error rate is low, accept the batch. If errors found, widen the sample.\n\n**\"Full human review of flagged\":** Tool narrows the universe (500 docs → 80 with CoC clauses). Human reads all 80. Tool saved the time of reading the 420 clean ones.\n\n### Step 4: Judgment layer\n\nThe tool found the clauses. Now apply judgment:\n\nFor each flagged CoC provision: is it actually triggered by this deal?\n- Stock sale vs. asset sale vs. merger — different triggers\n- \"Change of control\" defined how in the contract — majority ownership? board control? something else?\n- Is there a carve-out for this type of transaction?\n\nThis is the part the tool can't do. Output goes to diligence findings in house format.\n\n## Output\n\n> The QA summary below is derived from VDR documents that are privileged, confidential, or both. It inherits the sources' privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. Store with the matter's privileged files.\n\n```markdown\n## AI Tool Handoff Summary — [Category]\n\n**Tool:** [Luminance \u002F Kira]\n**Documents processed:** [N]\n**Extraction targets:** [clause types]\n\n### QA\n\n**Trust level:** [per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n**Sample size:** [N] docs spot-checked\n**Error rate:** [X]% — [Accepted \u002F Widened sample \u002F Full re-review triggered]\n\n### Results\n\n| Clause type | Docs flagged | After judgment layer | Material |\n|---|---|---|---|\n| Change of control | [N] | [N actually triggered by deal structure] | [N above threshold] |\n| Assignment | [N] | [N] | [N] |\n\n**→ [N] findings added to diligence issues**\n**→ [N] consents added to closing checklist**\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 doesn't run Luminance or Kira — it manages the handoff and QA. A human (or the tool's own interface) runs the extraction.\n- It doesn't replace the tool's output with its own judgment entirely — if `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` says spot-check 10%, check 10%, not 100%.\n- It doesn't decide the trust level — that's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`, set at cold-start based on the team's experience with the tool.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fai-tool-handoff",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill ai-tool-handoff",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill ai-tool-handoff",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill ai-tool-handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fai-tool-handoff\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]