[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CTT55CS5D3ZNSN63XYTQD":3,"skill-same:01M75CTT55CS5D3ZNSN63XYTQD":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},"01M75CTT55CS5D3ZNSN63XYTQD","deal-team-summary",null,"Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says \"brief the deal team\", \"what's the state of diligence\", \"summarize findings for [audience]\", \"deal update\", or on the briefing cadence.","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\u002Fdeal-team-summary\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: deal-team-summary\ndescription: >\n  Aggregate diligence findings into a deal team briefing at the right altitude\n  for the audience — exec summary for leadership, working summary for the team.\n  Use when user says \"brief the deal team\", \"what's the state of diligence\",\n  \"summarize findings for [audience]\", \"deal update\", or on the briefing cadence.\n---\n\n# Deal Team Summary\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\nThe deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → Deal team briefing (cadence, format, what the business reads)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md` → deal lead, timeline\n- Current findings from diligence-issue-extraction output\n\n## Audience tiers\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — what the business reads vs. what's for the file. Default tiers:\n\n| Audience | Gets | Doesn't get |\n|---|---|---|\n| **Board \u002F exec sponsor** | Top 3-5 material issues, price\u002Fstructure impact, decision items | Category detail, green findings, process |\n| **Deal lead** | All reds, all yellows, progress, decision items, next steps | Green finding detail |\n| **Working team** | Everything — full findings, status by category, gaps | Nothing withheld |\n\nAsk which tier if not obvious.\n\n## The summary\n\n### Exec tier\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> This brief aggregates privileged diligence findings and inherits the sources' privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.\n\n# [Deal code] — Diligence Brief — [date]\n\n**Status:** [On track \u002F Issues identified \u002F Material findings]\n**Coverage:** [X]% of VDR reviewed\n\n## Material findings\n\n[3-5 max. One paragraph each. What it is, why it matters to the deal, what\nwe're doing about it.]\n\n## Decisions needed\n\n- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]\n  — [who decides] — [by when]\n\n## Since last brief\n\n[What changed. New findings, findings resolved, coverage progress.]\n```\n\n### Deal lead tier\n\nSame as above plus:\n\n```markdown\n## All open issues by category\n\n### 🔴 Red\n[Finding title + one-line — link to full finding for detail]\n\n### 🟡 Yellow\n[same]\n\n## Progress\n\n| Category | Docs reviewed | Coverage | Reds | Yellows | Status |\n|---|---|---|---|---|---|\n| [name] | [N\u002FM] | [%] | [N] | [N] | [Complete \u002F In progress \u002F Blocked] |\n\n## Gaps and follow-ups\n\n- [Supplemental request items outstanding]\n- [Questions to management]\n\n## Next 72 hours\n\n[What's getting reviewed, what briefings are scheduled]\n```\n\n### Working team tier\n\nFull finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.\n\n## Deltas\n\nIf this is a recurring brief (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` cadence), lead with what changed:\n\n- New findings since last brief\n- Findings upgraded\u002Fdowngraded in severity\n- Findings resolved (consent obtained, issue clarified away)\n- Coverage movement\n\nDeal leads care more about movement than state. \"Still 12 yellows\" is less useful than \"2 new yellows, 3 resolved.\"\n\n## Handoffs\n\n- **From diligence-issue-extraction:** This skill reads the accumulated findings.\n- **To closing-checklist:** Any \"decision needed\" items that resolve into closing conditions go on the checklist.\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 make the materiality call — it reports the calls that were made at extraction time.\n- It doesn't decide what the deal team does about a finding — it surfaces the decision.\n- It doesn't distribute the brief — drafts it, human sends.\n","# Deal Team Summary\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\nThe deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → Deal team briefing (cadence, format, what the business reads)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fdeals\u002F[code]\u002Fdeal-context.md` → deal lead, timeline\n- Current findings from diligence-issue-extraction output\n\n## Audience tiers\n\nPer `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` — what the business reads vs. what's for the file. Default tiers:\n\n| Audience | Gets | Doesn't get |\n|---|---|---|\n| **Board \u002F exec sponsor** | Top 3-5 material issues, price\u002Fstructure impact, decision items | Category detail, green findings, process |\n| **Deal lead** | All reds, all yellows, progress, decision items, next steps | Green finding detail |\n| **Working team** | Everything — full findings, status by category, gaps | Nothing withheld |\n\nAsk which tier if not obvious.\n\n## The summary\n\n### Exec tier\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> This brief aggregates privileged diligence findings and inherits the sources' privilege and confidentiality status. Distribution beyond the privilege circle (including to broader business teams) can waive privilege — confirm the distribution list matches the privilege circle before sending.\n\n# [Deal code] — Diligence Brief — [date]\n\n**Status:** [On track \u002F Issues identified \u002F Material findings]\n**Coverage:** [X]% of VDR reviewed\n\n## Material findings\n\n[3-5 max. One paragraph each. What it is, why it matters to the deal, what\nwe're doing about it.]\n\n## Decisions needed\n\n- [ ] [Specific decision — price adjustment, indemnity ask, walk-away trigger]\n  — [who decides] — [by when]\n\n## Since last brief\n\n[What changed. New findings, findings resolved, coverage progress.]\n```\n\n### Deal lead tier\n\nSame as above plus:\n\n```markdown\n## All open issues by category\n\n### 🔴 Red\n[Finding title + one-line — link to full finding for detail]\n\n### 🟡 Yellow\n[same]\n\n## Progress\n\n| Category | Docs reviewed | Coverage | Reds | Yellows | Status |\n|---|---|---|---|---|---|\n| [name] | [N\u002FM] | [%] | [N] | [N] | [Complete \u002F In progress \u002F Blocked] |\n\n## Gaps and follow-ups\n\n- [Supplemental request items outstanding]\n- [Questions to management]\n\n## Next 72 hours\n\n[What's getting reviewed, what briefings are scheduled]\n```\n\n### Working team tier\n\nFull finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.\n\n## Deltas\n\nIf this is a recurring brief (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` cadence), lead with what changed:\n\n- New findings since last brief\n- Findings upgraded\u002Fdowngraded in severity\n- Findings resolved (consent obtained, issue clarified away)\n- Coverage movement\n\nDeal leads care more about movement than state. \"Still 12 yellows\" is less useful than \"2 new yellows, 3 resolved.\"\n\n## Handoffs\n\n- **From diligence-issue-extraction:** This skill reads the accumulated findings.\n- **To closing-checklist:** Any \"decision needed\" items that resolve into closing conditions go on the checklist.\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 make the materiality call — it reports the calls that were made at extraction time.\n- It doesn't decide what the deal team does about a finding — it surfaces the decision.\n- It doesn't distribute the brief — drafts it, human sends.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdeal-team-summary",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 deal-team-summary",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill deal-team-summary",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill deal-team-summary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdeal-team-summary\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",[],[]]