[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CWVFRJW3FX376P2R7BVBF":3,"skill-same:01M75CWVFRJW3FX376P2R7BVBF":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75CWVFRJW3FX376P2R7BVBF","demand-intake",null,"Pre-drafting context gathering for a demand letter — parties, facts, basis, leverage, BATNA, and privilege filters — written to a structured intake.md the demand-draft skill reads. Use when the user wants to prep a demand letter, run intake before drafting, or capture context for a payment demand, breach\u002Fcure notice, cease-and-desist, employment separation, or preservation demand.","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\u002Fdemand-intake\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: demand-intake\ndescription: Pre-drafting context gathering for a demand letter — parties, facts, basis, leverage, BATNA, and privilege filters — written to a structured intake.md the demand-draft skill reads. Use when the user wants to prep a demand letter, run intake before drafting, or capture context for a payment demand, breach\u002Fcure notice, cease-and-desist, employment separation, or preservation demand.\nargument-hint: \"[title] [--full]\"\n---\n\n# \u002Fdemand-intake\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → demand-letter practice, landscape, risk calibration.\n2. Follow the workflow and reference below.\n3. Run the adaptive intake (core 8 always; strategic block if material or `--full`).\n4. Generate slug from title + counterparty + year-month.\n5. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F[slug]\u002Fintake.md`.\n6. Confirm with user: \"Intake saved. Run `\u002Flitigation-legal:demand-draft [slug]` when ready.\"\n\n---\n\n# Demand Intake\n\n## Purpose\n\nThe drafting is downstream. The value is in the pre-writing — forcing the questions a careless letter skips. Leverage, BATNA, downside tolerance, privilege filters, the actual audience. A demand letter sent without thinking about those is worse than no letter.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → Demand-letter practice (insurance-tender timing, materiality threshold for matter creation, any seed-doc templates), landscape (counterparty type, repeat-adversary patterns), risk calibration (to pre-estimate materiality), house style. **Tone, compliance period, marking, signer are NOT practice-level defaults — they are set per matter in the `## Posture for this matter` step below.**\n\n## Flags\n\n- `--full` → run the complete intake regardless of materiality heuristics (for counsel who wants thorough every time)\n\n## The intake\n\n### Posture for this matter (ask FIRST, before the core)\n\n> **Posture for this matter.** Demand-letter tone and terms are case-by-case, not a practice default. Ask:\n> - **Tone:** measured \u002F assertive \u002F aggressive? (depends on the relationship, the amount, and whether litigation is likely)\n> - **Response window:** what's reasonable given the claim? (14 days is common for payment demands; 30 days for cure; 7 days for cease-and-desist — but the contract or protocol may set it)\n> - **Marking:** does this need a \"without prejudice\" or \"without prejudice save as to costs\" marking? (settlement communications do; assertions of claim often don't; jurisdiction matters — ask if unsure)\n> - **Signer:** you, the client, the GC, instructed solicitor\u002Fcounsel?\n> Don't assume. Read the prior demand correspondence in the matter file if there is any — it establishes the register.\n\nRecord the answers in the intake under a `## Posture` section before `## Parties`. These answers govern the rest of the intake and the downstream draft — do not fall back to a practice-level default if the user left any of them blank; ask again.\n\n### Core — always asked (8 questions)\n\n**1. Demand type**\n`payment | breach-cure | cease-desist | employment-separation | preservation | other`\n\n**2. Parties**\n- **Sender:** our company (and any specific entity if multi-entity)\n- **Recipient:** counterparty — name, entity, address\n- **Recipient audience:** who actually reads (GC? CEO? individual? in-house legal?)\n- **Relationship:** `customer | vendor | ex-employee | competitor | third-party | other`\n\n**3. Triggering event**\n- What happened and when (dates matter — statute-of-limitations, notice periods)\n- Evidence available (contracts, emails, records, witnesses)\n\n*Seed doc opportunity: \"If you can share the underlying contract, correspondence, or evidence, the draft will be materially sharper. Paths work.\"*\n\n**4. Legal \u002F contractual basis**\n- Which provisions — specific contract sections if applicable\n- Governing law (jurisdiction, choice-of-law clause)\n- Statutes or rules relied on (placeholders OK — the draft will flag `[CITE:___]` anyway)\n\n**5. Desired outcome**\n- Specific asks. Not \"resolution\" — payment of $X by date Y; cessation of specific activity Z; cure within N days; return of specific property.\n- If multiple asks, order them (primary vs. fallback)\n\n**6. Deadlines**\n- External deadline driving this (SoL, ongoing harm window, business event)\n- Demand compliance deadline — how long we give the recipient. Use the response window captured in `## Posture for this matter` above; do not fall back to a practice-level default.\n\n**7. Prior outreach**\n- Has this been raised informally? When, by whom, in what form?\n- Any response so far?\n- Why is escalation to a demand letter happening now?\n\n**8. Distribution**\n- Delivery method (ask; no practice-level default)\n- Signer — captured in `## Posture for this matter` above\n- Copies — internal stakeholders, insurance carrier (if tendering pre-demand per practice-level tender-timing rule), counsel\n\n### Strategic — asked if material, or if `--full`\n\nMateriality heuristic: ask the strategic block if any of the following are true.\n\n- Demand type is `cease-desist`, `breach-cure`, `employment-separation`, or `preservation`\n- Desired outcome dollar value ≥ the medium-severity band from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` risk calibration\n- Counterparty is a customer, competitor, or frequent adversary per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` landscape\n- User ran with `--full`\n\n**Explicit skip option.** When the strategic block is triggered, the user can decline to answer it. Ask plainly:\n\n> This is a material demand by the heuristic. The strategic block (leverage, BATNA, tone, privilege filters) is where most of the pre-writing value lives. Skipping it produces a thinner draft.\n> - **Answer now** — walk the strategic block (5-7 min)\n> - **Answer partial** — walk the subset you feel prepared for\n> - **Skip** — proceed to draft with only the core block; I'll flag `strategic_block: skipped` in the intake\n\nIf the user chooses Skip, the intake file records it:\n\n```yaml\nstrategic_block: skipped        # answered | partial | skipped\nskipped_reason: string | null   # captured if user provided one\n```\n\nThe draft skill honors the skip — pre-draft gate runs regardless, but sections that depend on strategic-block answers get `[SME VERIFY: leverage\u002Ftone\u002Fprivilege not captured in intake]` markers. The `\u002Fdemand-draft` command also prompts a second time, asking whether the user wants to complete the strategic block before drafting.\n\n**9. Leverage and BATNA**\n- What gives us negotiating power (contractual rights, factual leverage, reputational, commercial)\n- What if they refuse — are we prepared to litigate? Go public? Accept a smaller outcome?\n- Their likely BATNA — what's their best alternative? (If they don't think we'll sue, the demand is weak.)\n\n**10. Downside tolerance**\n- Reputational exposure if this becomes public\n- Precedent risk — does this letter set a pattern that affects other matters?\n- Regulatory \u002F disclosure implications (is this the kind of dispute that becomes a 10-Q item?)\n- Insurance implications — does sending without tendering waive coverage?\n\n**11. Tone posture**\n- Already captured in `## Posture for this matter` above. Here, probe the trade-off if the user chose a stronger tone than the facts seem to warrant, or a weaker tone than the facts seem to warrant.\n- Worth naming explicitly: aggressive tone burns the relationship. If you want to keep the business relationship but need to protect the legal position, `measured` is usually the right call.\n\n**12. Settlement-communication posture**\n- Research the settlement-communication protections applicable in the forum (FRE 408 in federal, the state equivalent otherwise). Is this letter a settlement communication that should be protected? Or an assertion of rights that shouldn't be?\n- If protected: the draft will include the settlement-communication marker and will be structured so the substance (a discussion of compromise) — not just the label — supports the posture.\n- Protection attaches from conduct and context, not merely from labeling. The marker is a belt-and-suspenders choice.\n\n**13. Privilege filters**\n- What's in our internal analysis that must NOT appear in the letter? (Facts we haven't verified, our doubts about our case, strategic reasoning, prior settlement discussions)\n- A single badly-worded sentence can waive privilege on related analysis. Be explicit about what stays out.\n\n**14. Admission and accord-and-satisfaction risk**\n- Anything in the letter that the counterparty could later characterize as an admission of fact or liability?\n- Does this demand risk inadvertently satisfying (or purporting to accept) a separate claim? (Accord-and-satisfaction: cashing a check marked \"payment in full\" can end a disputed debt.)\n\n## Writing the intake\n\n### Slug\n\n`[type]-[counterparty-short]-[yyyy-mm]`. Confirm uniqueness in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F`.\n\n### `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F[slug]\u002Fintake.md`\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n# Demand Intake: [title]\n\n**Slug:** [slug]\n**Demand type:** [type]\n**Drafted by:** [counsel]\n**Opened:** [YYYY-MM-DD]\n**Status:** intake | ready-to-draft | drafted | sent | closed\n**Strategic block:** answered | partial | skipped\n**Skipped reason:** [if applicable]\n\n---\n\n## Posture\n\n- **Tone:** [measured \u002F assertive \u002F aggressive — with one-line rationale tied to the relationship and the amount]\n- **Response window:** [N days — tied to the claim \u002F contract \u002F protocol]\n- **Marking:** [none \u002F without prejudice \u002F without prejudice save as to costs \u002F other — with rationale]\n- **Signer:** [name \u002F role — you \u002F client \u002F GC \u002F instructed counsel]\n\n*This is the per-matter posture captured at intake. The draft skill reads from here.*\n\n---\n\n## Parties\n\n- **Sender:** [our entity]\n- **Recipient:** [counterparty, entity, address]\n- **Recipient audience:** [who reads]\n- **Relationship:** [type]\n\n## Triggering event\n\n[What happened, when, evidence]\n\n## Legal \u002F contractual basis\n\n[Provisions, governing law, statutes]\n\n## Desired outcome\n\n[Specific asks in priority order]\n\n## Deadlines\n\n- **External:** [SoL, ongoing harm window]\n- **Compliance:** [how long we give them]\n\n## Prior outreach\n\n[History, most recent first]\n\n## Distribution\n\n- **Delivery:** [method]\n- **Signer:** [name\u002Frole]\n- **Copies:** [list]\n\n---\n\n## Strategic (if applicable)\n\n### Leverage & BATNA\n\n[Our power, their likely response]\n\n### Downside tolerance\n\n[Reputational, precedent, regulatory, insurance]\n\n### Tone posture\n\n[relationship-preserving \u002F measured \u002F scorched-earth — with rationale]\n\n### Settlement-communication posture\n\n[Protected or not in the forum — with reasoning. Cite primary source per the applicable rule (FRE 408 or state equivalent).]\n\n### Privilege filters\n\n[What CANNOT appear in the draft]\n\n### Admission \u002F accord-and-satisfaction risk\n\n[Specific risks flagged]\n\n---\n\n## Seed documents\n\n| Doc | Path |\n|---|---|\n| [underlying contract] | [path or \"not shared\"] |\n| [prior correspondence] | [path or \"not shared\"] |\n| [evidence] | [path or \"not shared\"] |\n\n---\n\n## Materiality assessment\n\n**Auto-heuristic says:** [material \u002F immaterial — with reasoning]\n**User call:** [material \u002F immaterial \u002F TBD at post-send]\n```\n\n## Confirm before writing\n\nShow the user the draft intake. Flag anything thin:\n\n> Here's the intake. I notice [thin spots]. Before I save, anything to add?\n\n## Handoff to drafting\n\nEnd with:\n> Intake saved. When ready: `\u002Flitigation-legal:demand-draft [slug]`\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- Draft the letter. That's `demand-draft` — the two steps are intentionally separate so counsel can pause for business input, outside counsel consult, or insurance tender before drafting.\n- Decide whether to send the letter. Some intake sessions end with \"actually, don't send — let's negotiate directly.\" That's a valid outcome; the intake record still has value.\n- Run the conflicts check. If the counterparty is a customer or known entity, flag that this should clear conflicts (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`) before sending — but the check itself lives in the matter-intake workflow or outside this skill.\n","# \u002Fdemand-intake\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → demand-letter practice, landscape, risk calibration.\n2. Follow the workflow and reference below.\n3. Run the adaptive intake (core 8 always; strategic block if material or `--full`).\n4. Generate slug from title + counterparty + year-month.\n5. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F[slug]\u002Fintake.md`.\n6. Confirm with user: \"Intake saved. Run `\u002Flitigation-legal:demand-draft [slug]` when ready.\"\n\n---\n\n# Demand Intake\n\n## Purpose\n\nThe drafting is downstream. The value is in the pre-writing — forcing the questions a careless letter skips. Leverage, BATNA, downside tolerance, privilege filters, the actual audience. A demand letter sent without thinking about those is worse than no letter.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → Demand-letter practice (insurance-tender timing, materiality threshold for matter creation, any seed-doc templates), landscape (counterparty type, repeat-adversary patterns), risk calibration (to pre-estimate materiality), house style. **Tone, compliance period, marking, signer are NOT practice-level defaults — they are set per matter in the `## Posture for this matter` step below.**\n\n## Flags\n\n- `--full` → run the complete intake regardless of materiality heuristics (for counsel who wants thorough every time)\n\n## The intake\n\n### Posture for this matter (ask FIRST, before the core)\n\n> **Posture for this matter.** Demand-letter tone and terms are case-by-case, not a practice default. Ask:\n> - **Tone:** measured \u002F assertive \u002F aggressive? (depends on the relationship, the amount, and whether litigation is likely)\n> - **Response window:** what's reasonable given the claim? (14 days is common for payment demands; 30 days for cure; 7 days for cease-and-desist — but the contract or protocol may set it)\n> - **Marking:** does this need a \"without prejudice\" or \"without prejudice save as to costs\" marking? (settlement communications do; assertions of claim often don't; jurisdiction matters — ask if unsure)\n> - **Signer:** you, the client, the GC, instructed solicitor\u002Fcounsel?\n> Don't assume. Read the prior demand correspondence in the matter file if there is any — it establishes the register.\n\nRecord the answers in the intake under a `## Posture` section before `## Parties`. These answers govern the rest of the intake and the downstream draft — do not fall back to a practice-level default if the user left any of them blank; ask again.\n\n### Core — always asked (8 questions)\n\n**1. Demand type**\n`payment | breach-cure | cease-desist | employment-separation | preservation | other`\n\n**2. Parties**\n- **Sender:** our company (and any specific entity if multi-entity)\n- **Recipient:** counterparty — name, entity, address\n- **Recipient audience:** who actually reads (GC? CEO? individual? in-house legal?)\n- **Relationship:** `customer | vendor | ex-employee | competitor | third-party | other`\n\n**3. Triggering event**\n- What happened and when (dates matter — statute-of-limitations, notice periods)\n- Evidence available (contracts, emails, records, witnesses)\n\n*Seed doc opportunity: \"If you can share the underlying contract, correspondence, or evidence, the draft will be materially sharper. Paths work.\"*\n\n**4. Legal \u002F contractual basis**\n- Which provisions — specific contract sections if applicable\n- Governing law (jurisdiction, choice-of-law clause)\n- Statutes or rules relied on (placeholders OK — the draft will flag `[CITE:___]` anyway)\n\n**5. Desired outcome**\n- Specific asks. Not \"resolution\" — payment of $X by date Y; cessation of specific activity Z; cure within N days; return of specific property.\n- If multiple asks, order them (primary vs. fallback)\n\n**6. Deadlines**\n- External deadline driving this (SoL, ongoing harm window, business event)\n- Demand compliance deadline — how long we give the recipient. Use the response window captured in `## Posture for this matter` above; do not fall back to a practice-level default.\n\n**7. Prior outreach**\n- Has this been raised informally? When, by whom, in what form?\n- Any response so far?\n- Why is escalation to a demand letter happening now?\n\n**8. Distribution**\n- Delivery method (ask; no practice-level default)\n- Signer — captured in `## Posture for this matter` above\n- Copies — internal stakeholders, insurance carrier (if tendering pre-demand per practice-level tender-timing rule), counsel\n\n### Strategic — asked if material, or if `--full`\n\nMateriality heuristic: ask the strategic block if any of the following are true.\n\n- Demand type is `cease-desist`, `breach-cure`, `employment-separation`, or `preservation`\n- Desired outcome dollar value ≥ the medium-severity band from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` risk calibration\n- Counterparty is a customer, competitor, or frequent adversary per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` landscape\n- User ran with `--full`\n\n**Explicit skip option.** When the strategic block is triggered, the user can decline to answer it. Ask plainly:\n\n> This is a material demand by the heuristic. The strategic block (leverage, BATNA, tone, privilege filters) is where most of the pre-writing value lives. Skipping it produces a thinner draft.\n> - **Answer now** — walk the strategic block (5-7 min)\n> - **Answer partial** — walk the subset you feel prepared for\n> - **Skip** — proceed to draft with only the core block; I'll flag `strategic_block: skipped` in the intake\n\nIf the user chooses Skip, the intake file records it:\n\n```yaml\nstrategic_block: skipped        # answered | partial | skipped\nskipped_reason: string | null   # captured if user provided one\n```\n\nThe draft skill honors the skip — pre-draft gate runs regardless, but sections that depend on strategic-block answers get `[SME VERIFY: leverage\u002Ftone\u002Fprivilege not captured in intake]` markers. The `\u002Fdemand-draft` command also prompts a second time, asking whether the user wants to complete the strategic block before drafting.\n\n**9. Leverage and BATNA**\n- What gives us negotiating power (contractual rights, factual leverage, reputational, commercial)\n- What if they refuse — are we prepared to litigate? Go public? Accept a smaller outcome?\n- Their likely BATNA — what's their best alternative? (If they don't think we'll sue, the demand is weak.)\n\n**10. Downside tolerance**\n- Reputational exposure if this becomes public\n- Precedent risk — does this letter set a pattern that affects other matters?\n- Regulatory \u002F disclosure implications (is this the kind of dispute that becomes a 10-Q item?)\n- Insurance implications — does sending without tendering waive coverage?\n\n**11. Tone posture**\n- Already captured in `## Posture for this matter` above. Here, probe the trade-off if the user chose a stronger tone than the facts seem to warrant, or a weaker tone than the facts seem to warrant.\n- Worth naming explicitly: aggressive tone burns the relationship. If you want to keep the business relationship but need to protect the legal position, `measured` is usually the right call.\n\n**12. Settlement-communication posture**\n- Research the settlement-communication protections applicable in the forum (FRE 408 in federal, the state equivalent otherwise). Is this letter a settlement communication that should be protected? Or an assertion of rights that shouldn't be?\n- If protected: the draft will include the settlement-communication marker and will be structured so the substance (a discussion of compromise) — not just the label — supports the posture.\n- Protection attaches from conduct and context, not merely from labeling. The marker is a belt-and-suspenders choice.\n\n**13. Privilege filters**\n- What's in our internal analysis that must NOT appear in the letter? (Facts we haven't verified, our doubts about our case, strategic reasoning, prior settlement discussions)\n- A single badly-worded sentence can waive privilege on related analysis. Be explicit about what stays out.\n\n**14. Admission and accord-and-satisfaction risk**\n- Anything in the letter that the counterparty could later characterize as an admission of fact or liability?\n- Does this demand risk inadvertently satisfying (or purporting to accept) a separate claim? (Accord-and-satisfaction: cashing a check marked \"payment in full\" can end a disputed debt.)\n\n## Writing the intake\n\n### Slug\n\n`[type]-[counterparty-short]-[yyyy-mm]`. Confirm uniqueness in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F`.\n\n### `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fdemand-letters\u002F[slug]\u002Fintake.md`\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n# Demand Intake: [title]\n\n**Slug:** [slug]\n**Demand type:** [type]\n**Drafted by:** [counsel]\n**Opened:** [YYYY-MM-DD]\n**Status:** intake | ready-to-draft | drafted | sent | closed\n**Strategic block:** answered | partial | skipped\n**Skipped reason:** [if applicable]\n\n---\n\n## Posture\n\n- **Tone:** [measured \u002F assertive \u002F aggressive — with one-line rationale tied to the relationship and the amount]\n- **Response window:** [N days — tied to the claim \u002F contract \u002F protocol]\n- **Marking:** [none \u002F without prejudice \u002F without prejudice save as to costs \u002F other — with rationale]\n- **Signer:** [name \u002F role — you \u002F client \u002F GC \u002F instructed counsel]\n\n*This is the per-matter posture captured at intake. The draft skill reads from here.*\n\n---\n\n## Parties\n\n- **Sender:** [our entity]\n- **Recipient:** [counterparty, entity, address]\n- **Recipient audience:** [who reads]\n- **Relationship:** [type]\n\n## Triggering event\n\n[What happened, when, evidence]\n\n## Legal \u002F contractual basis\n\n[Provisions, governing law, statutes]\n\n## Desired outcome\n\n[Specific asks in priority order]\n\n## Deadlines\n\n- **External:** [SoL, ongoing harm window]\n- **Compliance:** [how long we give them]\n\n## Prior outreach\n\n[History, most recent first]\n\n## Distribution\n\n- **Delivery:** [method]\n- **Signer:** [name\u002Frole]\n- **Copies:** [list]\n\n---\n\n## Strategic (if applicable)\n\n### Leverage & BATNA\n\n[Our power, their likely response]\n\n### Downside tolerance\n\n[Reputational, precedent, regulatory, insurance]\n\n### Tone posture\n\n[relationship-preserving \u002F measured \u002F scorched-earth — with rationale]\n\n### Settlement-communication posture\n\n[Protected or not in the forum — with reasoning. Cite primary source per the applicable rule (FRE 408 or state equivalent).]\n\n### Privilege filters\n\n[What CANNOT appear in the draft]\n\n### Admission \u002F accord-and-satisfaction risk\n\n[Specific risks flagged]\n\n---\n\n## Seed documents\n\n| Doc | Path |\n|---|---|\n| [underlying contract] | [path or \"not shared\"] |\n| [prior correspondence] | [path or \"not shared\"] |\n| [evidence] | [path or \"not shared\"] |\n\n---\n\n## Materiality assessment\n\n**Auto-heuristic says:** [material \u002F immaterial — with reasoning]\n**User call:** [material \u002F immaterial \u002F TBD at post-send]\n```\n\n## Confirm before writing\n\nShow the user the draft intake. Flag anything thin:\n\n> Here's the intake. I notice [thin spots]. Before I save, anything to add?\n\n## Handoff to drafting\n\nEnd with:\n> Intake saved. When ready: `\u002Flitigation-legal:demand-draft [slug]`\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- Draft the letter. That's `demand-draft` — the two steps are intentionally separate so counsel can pause for business input, outside counsel consult, or insurance tender before drafting.\n- Decide whether to send the letter. Some intake sessions end with \"actually, don't send — let's negotiate directly.\" That's a valid outcome; the intake record still has value.\n- Run the conflicts check. If the counterparty is a customer or known entity, flag that this should clear conflicts (per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`) before sending — but the check itself lives in the matter-intake workflow or outside this skill.\n",{"name":5,"description":7,"argument-hint":23},"[title] [--full]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdemand-intake",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill demand-intake",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill demand-intake",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill demand-intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdemand-intake\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]