[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CX0K2A0475SW2VXGFWXGC":3,"skill-same:01M75CX0K2A0475SW2VXGFWXGC":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},"01M75CX0K2A0475SW2VXGFWXGC","demand-received",null,"Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says \"we got a demand letter\", \"triage this demand\", or shares an incoming demand to evaluate.","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-received\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: demand-received\ndescription: Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says \"we got a demand letter\", \"triage this demand\", or shares an incoming demand to evaluate.\nargument-hint: \"[path-to-incoming] [--slug=custom-slug]\"\n---\n\n# \u002Fdemand-received\n\n1. Read the incoming document from provided path.\n2. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` for portfolio cross-check.\n3. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration, landscape, demand-letter practice.\n4. Follow the workflow and reference below.\n5. Extract fields; cross-check portfolio; assess merit; present options with recommendation.\n6. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Ftriage.md`. Copy or link incoming to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Fincoming.[ext]`.\n7. Hand off per user choice:\n   - Create matter → `matter-intake` pre-populated\n   - Respond with counter-demand → `demand-intake` pre-populated\n   - Link to existing matter → update `related_matters` in log\n   - Standalone → no further action\n\n---\n\n# Demand Received\n\n## Purpose\n\nInbound demand letters are the bread and butter of an in-house litigation practice. A small fraction need escalation; most can be handled with a structured response or a holding letter. The failure mode is treating them all alike. This skill triages, cross-checks the portfolio, and produces options.\n\n## Load context\n\n- The incoming document (user provides path or drops it in-session)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — scan for related matters (same counterparty, overlapping counterparties via entity relationships, or matter type + recent date)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration (for merit assessment), landscape (is the sender a frequent adversary?), demand-letter practice (house tone and response defaults)\n\n## Workflow\n\n### Step 1: Read the demand\n\nExtract from the incoming:\n\n- **Sender** — entity, signer, counsel (if signed by outside firm)\n- **Recipient** — which entity\u002Fperson at our company\n- **Delivery** — certified, email, courier (matters for deadline calculation)\n- **Date received** vs. **date signed**\n- **Demand type** — payment, breach\u002Fcure, C&D, preservation, settlement, other\n- **Specific asks** — what they want, by when\n- **Facts alleged** — their version of what happened\n- **Legal basis** — statutes, contract provisions, theories they cite\n- **Threats** — what they say they'll do if we don't comply\n- **Settlement-communication framing** — research the settlement-communication protections applicable in the forum (FRE 408 in federal, the state equivalent otherwise). Note whether the demand is marked as a settlement communication, but remember: protection attaches from conduct and context, not merely from labeling. Capture both the label (if any) and a first-pass read of whether the substance is in fact a compromise discussion.\n\n### Step 2: Portfolio cross-check\n\nSearch `_log.yaml` for:\n\n- **Direct match** — matter with same counterparty (their slug matches the sender)\n- **Type match** — similar matter type with this counterparty in the past (closed matters count — they inform pattern)\n- **Subject overlap** — matters where the subject might be the same dispute (e.g., same contract, same product, same project)\n\nPresent findings:\n\n- If **direct match + active:** flag as almost certainly the same matter; recommend adding incoming to the existing matter, not opening a new one. Update `related_matters` if it's a tangent.\n- If **direct match + closed:** flag — counterparty is back. May be a new dispute (open new matter) or a resurrected one (reopen or amend). User decides.\n- If **type match:** note as precedent\u002Fcontext; probably distinct matter but inform the response strategy.\n- If **no match:** novel. Treat as fresh.\n\n### Step 3: Merit assessment\n\nNot a legal opinion — a structured read:\n\n- **Facts** — do the alleged facts align with what we know? Where's the disconnect?\n- **Legal basis** — are the cited provisions\u002Fstatutes actually applicable? (Flag cites for user verification — do not attempt to validate law autonomously.)\n- **Strength on their side** — if they went to court tomorrow, what's their story?\n- **Strength on our side** — what are our likely defenses?\n- **Damages demanded vs. likely** — is the ask proportionate to what a court would award if they won?\n- **Leverage and pressure** — are they credibly prepared to sue? Do they have capacity? Are they a repeat-litigant adversary per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`?\n\nOutput a triage rating: **substantial merit \u002F debatable \u002F weak \u002F frivolous**. Be blunt. The user is triaging, not writing the brief.\n\n### Step 4: Response options\n\nPresent 3-4 options with tradeoffs:\n\n**Option A — substantive response**\n- When: their demand has merit or is at least debatable; a reasoned reply protects the record\n- Tradeoff: commits us to a position in writing\n- Next step: `\u002Fdemand-intake` with pre-populated fields for a counter-response letter\n\n**Option B — holding letter**\n- When: need time to investigate; don't want to concede anything or trigger their deadline math\n- Tradeoff: doesn't resolve anything; buys 2-4 weeks\n- Next step: short acknowledgment draft\n\n**Option C — settlement response**\n- When: early resolution is cheaper than litigation; willing to discuss without admitting\n- Tradeoff: settlement-communication posture required — research the applicable rule (FRE 408 or state equivalent) and structure the response so the substance, not just the label, qualifies as a compromise discussion. Must be careful not to waive claims.\n- Next step: `\u002Fdemand-intake` with `type: settlement-response`\n\n**Option D — ignore + preserve**\n- When: demand is frivolous or the deadline doesn't create legal prejudice\n- Tradeoff: silence can be used against us in some contexts (e.g., account stated); legal hold still required\n- Next step: issue legal hold via `\u002Flegal-hold --issue` if not already; log the demand and move on\n\nRecommend one. Be specific about why.\n\n### Step 5: Deadline triage\n\n- **Their stated deadline** — note it, but it doesn't bind us\n- **Our internal deadline** — when we must decide (often: stated deadline minus 5 business days to draft + approve)\n- **Legal deadlines** — statute of limitations, contractual cure periods, procedural requirements\n\nFlag any legal deadlines that are tight. Calendar them.\n\n**No silent supplement.** If the inbound demand cites rules, cases, or statutes that require verification, and a research query to the configured legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for a given authority, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: \"The search returned [N] results from [tool]. Coverage appears thin for [cite \u002F doctrine]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged `[web search — verify]` and should be checked against a primary source before relying, or (4) leave the `[SME VERIFY]` flag and stop here. Which would you like?\" A lawyer decides whether to accept lower-confidence sources; the skill does not decide for them.\n\n**Source attribution.** Tag every citation carried into the triage — including the sender's cited authorities, our response-option rationales, and any research pulled for merit assessment — with where it came from: `[Westlaw]`, `[CourtListener]`, `[Trellis]`, `[Descrybe]`, or the MCP tool name for citations retrieved from a legal research connector; `[web search — verify]` for web-search citations; `[model knowledge — verify]` for citations recalled from training data; `[user provided]` for citations supplied in the demand itself. Citations tagged `verify` carry higher fabrication risk and should be checked first. Never strip or collapse the tags.\n\n### Step 6: Write triage\n\nOutput: `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Ftriage.md`.\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> **Privilege inheritance.** This triage is derived from the inbound demand and from the portfolio log, and it records our first-pass merit read and response posture. Those internal analyses are attorney-client and\u002For work-product material. Distributing this triage beyond the privilege circle — including forwarding it to the business lead without marking, sharing with the counterparty, or attaching to an insurance tender without scrubbing — can waive protection over both this document and the reasoning inside it. Store with privileged matter material, mark consistently with house privilege conventions, and make distribution decisions deliberately.\n\n# Demand Received — Triage\n\n> **READ FOR TRIAGE, NOT OPINION.** This document is an intake scan and an options analysis — not a legal merit opinion. The `Triage rating` below is a structured read to support the counsel's decision on how to route the demand. It is not a recommendation on the merits and does not substitute for case-specific legal analysis. Every cited statute, rule, or case is flagged for SME verification; every merit call is the counsel's, not this skill's.\n\n**Slug:** [slug]\n**Received:** [YYYY-MM-DD]\n**Received by:** [entity \u002F person]\n**Incoming file:** [path]\n\n---\n\n## The demand\n\n**Sender:** [entity, signer, counsel]\n**Demand type:** [type]\n**Specific asks:** [list]\n**Their stated deadline:** [date]\n**Settlement-communication framing:** [labeled \u002F substantively \u002F neither \u002F ambiguous] — *protection turns on conduct and context, not the label; `[SME VERIFY]` against the forum's applicable rule*\n\n## Facts alleged\n\n[their version, in one paragraph]\n\n## Legal basis cited\n\n[citations — each inline-flagged with `[SME VERIFY: applicability \u002F currency \u002F jurisdiction]` — do not rely on any citation here without independent check]\n\n## Threats \u002F next steps they state\n\n[list]\n\n---\n\n## Portfolio cross-check\n\n**Direct match:** [slug if exists, or \"none\"]\n**Type match \u002F precedent:** [list or \"none\"]\n**Subject overlap:** [list or \"none\"]\n**Recommendation:** [new matter \u002F add to existing \u002F link via related_matters \u002F standalone inbound]\n\n---\n\n## Merit assessment\n\n**Facts:** [alignment with our version; disconnects]\n**Legal basis:** [applicability, with flags]\n**Their case if litigated:** [one paragraph]\n**Our defenses:** [one paragraph]\n**Damages proportionality:** [assessment]\n**Credibility of threat:** [will they sue? capacity? repeat litigant?]\n\n**Triage rating:** [substantial \u002F debatable \u002F weak \u002F frivolous] — *structured read for routing, not a merit opinion; `[SME VERIFY: counsel to confirm before relying on this]`*\n\n---\n\n## Response options\n\n### A. Substantive response\n[Rationale, tradeoffs, next step]\n\n### B. Holding letter\n[Rationale, tradeoffs, next step]\n\n### C. Settlement response\n[Rationale, tradeoffs, next step]\n\n### D. Ignore + preserve\n[Rationale, tradeoffs, next step]\n\n**Recommendation:** [A\u002FB\u002FC\u002FD] — [two sentences why] — `[SME VERIFY: counsel to confirm before executing]`\n\n---\n\n## Deadlines\n\n- **Their stated deadline:** [date]\n- **Our internal decision deadline:** [date]\n- **Legal deadlines:** [SoL, cure periods, procedural — with dates]\n\n---\n\n## Immediate actions\n\n- [ ] Legal hold issued — [yes\u002Fno] — if no, run `\u002Flegal-hold [slug] --issue`\n- [ ] Matter created in log — [yes\u002Fno\u002FTBD]\n- [ ] Counsel assigned — [who]\n- [ ] Insurance tendered — [yes\u002Fno\u002FN-A]\n- [ ] Internal escalation (GC\u002FCFO\u002Fbusiness lead) — [who\u002Fwhen]\n```\n\n### Step 7: Hand off\n\nBased on recommendation and user confirmation:\n\n- Matter creation → hand off to `\u002Fmatter-intake` with: counterparty, type, `source: demand-letter` (inbound), initial theory framed defensively, pre-populated.\n- Counter-response as outbound demand → hand off to `\u002Fdemand-intake` with: counterparty, context from triage, desired outcome as the response.\n- Link to existing matter → update that matter's `related_matters` in `_log.yaml`; append event to its `history.md`.\n- Standalone → leave in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F`; no portfolio change.\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- **Validate cited law.** Flags cites for the user to run through a citator (verify it is good law) or check with outside counsel. Inventing legal analysis on inbound demands is malpractice exposure.\n- **Send a response.** Drafts are drafted in `demand-draft`; this skill stops at the triage decision.\n- **Decide merit definitively.** The rating is a read for triage; a formal merit opinion lives with outside counsel or more thorough analysis.\n- **Make the matter-creation call.** Surfaces the recommendation; user decides.\n","# \u002Fdemand-received\n\n1. Read the incoming document from provided path.\n2. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` for portfolio cross-check.\n3. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration, landscape, demand-letter practice.\n4. Follow the workflow and reference below.\n5. Extract fields; cross-check portfolio; assess merit; present options with recommendation.\n6. Write `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Ftriage.md`. Copy or link incoming to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Fincoming.[ext]`.\n7. Hand off per user choice:\n   - Create matter → `matter-intake` pre-populated\n   - Respond with counter-demand → `demand-intake` pre-populated\n   - Link to existing matter → update `related_matters` in log\n   - Standalone → no further action\n\n---\n\n# Demand Received\n\n## Purpose\n\nInbound demand letters are the bread and butter of an in-house litigation practice. A small fraction need escalation; most can be handled with a structured response or a holding letter. The failure mode is treating them all alike. This skill triages, cross-checks the portfolio, and produces options.\n\n## Load context\n\n- The incoming document (user provides path or drops it in-session)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — scan for related matters (same counterparty, overlapping counterparties via entity relationships, or matter type + recent date)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` → risk calibration (for merit assessment), landscape (is the sender a frequent adversary?), demand-letter practice (house tone and response defaults)\n\n## Workflow\n\n### Step 1: Read the demand\n\nExtract from the incoming:\n\n- **Sender** — entity, signer, counsel (if signed by outside firm)\n- **Recipient** — which entity\u002Fperson at our company\n- **Delivery** — certified, email, courier (matters for deadline calculation)\n- **Date received** vs. **date signed**\n- **Demand type** — payment, breach\u002Fcure, C&D, preservation, settlement, other\n- **Specific asks** — what they want, by when\n- **Facts alleged** — their version of what happened\n- **Legal basis** — statutes, contract provisions, theories they cite\n- **Threats** — what they say they'll do if we don't comply\n- **Settlement-communication framing** — research the settlement-communication protections applicable in the forum (FRE 408 in federal, the state equivalent otherwise). Note whether the demand is marked as a settlement communication, but remember: protection attaches from conduct and context, not merely from labeling. Capture both the label (if any) and a first-pass read of whether the substance is in fact a compromise discussion.\n\n### Step 2: Portfolio cross-check\n\nSearch `_log.yaml` for:\n\n- **Direct match** — matter with same counterparty (their slug matches the sender)\n- **Type match** — similar matter type with this counterparty in the past (closed matters count — they inform pattern)\n- **Subject overlap** — matters where the subject might be the same dispute (e.g., same contract, same product, same project)\n\nPresent findings:\n\n- If **direct match + active:** flag as almost certainly the same matter; recommend adding incoming to the existing matter, not opening a new one. Update `related_matters` if it's a tangent.\n- If **direct match + closed:** flag — counterparty is back. May be a new dispute (open new matter) or a resurrected one (reopen or amend). User decides.\n- If **type match:** note as precedent\u002Fcontext; probably distinct matter but inform the response strategy.\n- If **no match:** novel. Treat as fresh.\n\n### Step 3: Merit assessment\n\nNot a legal opinion — a structured read:\n\n- **Facts** — do the alleged facts align with what we know? Where's the disconnect?\n- **Legal basis** — are the cited provisions\u002Fstatutes actually applicable? (Flag cites for user verification — do not attempt to validate law autonomously.)\n- **Strength on their side** — if they went to court tomorrow, what's their story?\n- **Strength on our side** — what are our likely defenses?\n- **Damages demanded vs. likely** — is the ask proportionate to what a court would award if they won?\n- **Leverage and pressure** — are they credibly prepared to sue? Do they have capacity? Are they a repeat-litigant adversary per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`?\n\nOutput a triage rating: **substantial merit \u002F debatable \u002F weak \u002F frivolous**. Be blunt. The user is triaging, not writing the brief.\n\n### Step 4: Response options\n\nPresent 3-4 options with tradeoffs:\n\n**Option A — substantive response**\n- When: their demand has merit or is at least debatable; a reasoned reply protects the record\n- Tradeoff: commits us to a position in writing\n- Next step: `\u002Fdemand-intake` with pre-populated fields for a counter-response letter\n\n**Option B — holding letter**\n- When: need time to investigate; don't want to concede anything or trigger their deadline math\n- Tradeoff: doesn't resolve anything; buys 2-4 weeks\n- Next step: short acknowledgment draft\n\n**Option C — settlement response**\n- When: early resolution is cheaper than litigation; willing to discuss without admitting\n- Tradeoff: settlement-communication posture required — research the applicable rule (FRE 408 or state equivalent) and structure the response so the substance, not just the label, qualifies as a compromise discussion. Must be careful not to waive claims.\n- Next step: `\u002Fdemand-intake` with `type: settlement-response`\n\n**Option D — ignore + preserve**\n- When: demand is frivolous or the deadline doesn't create legal prejudice\n- Tradeoff: silence can be used against us in some contexts (e.g., account stated); legal hold still required\n- Next step: issue legal hold via `\u002Flegal-hold --issue` if not already; log the demand and move on\n\nRecommend one. Be specific about why.\n\n### Step 5: Deadline triage\n\n- **Their stated deadline** — note it, but it doesn't bind us\n- **Our internal deadline** — when we must decide (often: stated deadline minus 5 business days to draft + approve)\n- **Legal deadlines** — statute of limitations, contractual cure periods, procedural requirements\n\nFlag any legal deadlines that are tight. Calendar them.\n\n**No silent supplement.** If the inbound demand cites rules, cases, or statutes that require verification, and a research query to the configured legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for a given authority, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: \"The search returned [N] results from [tool]. Coverage appears thin for [cite \u002F doctrine]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged `[web search — verify]` and should be checked against a primary source before relying, or (4) leave the `[SME VERIFY]` flag and stop here. Which would you like?\" A lawyer decides whether to accept lower-confidence sources; the skill does not decide for them.\n\n**Source attribution.** Tag every citation carried into the triage — including the sender's cited authorities, our response-option rationales, and any research pulled for merit assessment — with where it came from: `[Westlaw]`, `[CourtListener]`, `[Trellis]`, `[Descrybe]`, or the MCP tool name for citations retrieved from a legal research connector; `[web search — verify]` for web-search citations; `[model knowledge — verify]` for citations recalled from training data; `[user provided]` for citations supplied in the demand itself. Citations tagged `verify` carry higher fabrication risk and should be checked first. Never strip or collapse the tags.\n\n### Step 6: Write triage\n\nOutput: `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F[slug]\u002Ftriage.md`.\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n> **Privilege inheritance.** This triage is derived from the inbound demand and from the portfolio log, and it records our first-pass merit read and response posture. Those internal analyses are attorney-client and\u002For work-product material. Distributing this triage beyond the privilege circle — including forwarding it to the business lead without marking, sharing with the counterparty, or attaching to an insurance tender without scrubbing — can waive protection over both this document and the reasoning inside it. Store with privileged matter material, mark consistently with house privilege conventions, and make distribution decisions deliberately.\n\n# Demand Received — Triage\n\n> **READ FOR TRIAGE, NOT OPINION.** This document is an intake scan and an options analysis — not a legal merit opinion. The `Triage rating` below is a structured read to support the counsel's decision on how to route the demand. It is not a recommendation on the merits and does not substitute for case-specific legal analysis. Every cited statute, rule, or case is flagged for SME verification; every merit call is the counsel's, not this skill's.\n\n**Slug:** [slug]\n**Received:** [YYYY-MM-DD]\n**Received by:** [entity \u002F person]\n**Incoming file:** [path]\n\n---\n\n## The demand\n\n**Sender:** [entity, signer, counsel]\n**Demand type:** [type]\n**Specific asks:** [list]\n**Their stated deadline:** [date]\n**Settlement-communication framing:** [labeled \u002F substantively \u002F neither \u002F ambiguous] — *protection turns on conduct and context, not the label; `[SME VERIFY]` against the forum's applicable rule*\n\n## Facts alleged\n\n[their version, in one paragraph]\n\n## Legal basis cited\n\n[citations — each inline-flagged with `[SME VERIFY: applicability \u002F currency \u002F jurisdiction]` — do not rely on any citation here without independent check]\n\n## Threats \u002F next steps they state\n\n[list]\n\n---\n\n## Portfolio cross-check\n\n**Direct match:** [slug if exists, or \"none\"]\n**Type match \u002F precedent:** [list or \"none\"]\n**Subject overlap:** [list or \"none\"]\n**Recommendation:** [new matter \u002F add to existing \u002F link via related_matters \u002F standalone inbound]\n\n---\n\n## Merit assessment\n\n**Facts:** [alignment with our version; disconnects]\n**Legal basis:** [applicability, with flags]\n**Their case if litigated:** [one paragraph]\n**Our defenses:** [one paragraph]\n**Damages proportionality:** [assessment]\n**Credibility of threat:** [will they sue? capacity? repeat litigant?]\n\n**Triage rating:** [substantial \u002F debatable \u002F weak \u002F frivolous] — *structured read for routing, not a merit opinion; `[SME VERIFY: counsel to confirm before relying on this]`*\n\n---\n\n## Response options\n\n### A. Substantive response\n[Rationale, tradeoffs, next step]\n\n### B. Holding letter\n[Rationale, tradeoffs, next step]\n\n### C. Settlement response\n[Rationale, tradeoffs, next step]\n\n### D. Ignore + preserve\n[Rationale, tradeoffs, next step]\n\n**Recommendation:** [A\u002FB\u002FC\u002FD] — [two sentences why] — `[SME VERIFY: counsel to confirm before executing]`\n\n---\n\n## Deadlines\n\n- **Their stated deadline:** [date]\n- **Our internal decision deadline:** [date]\n- **Legal deadlines:** [SoL, cure periods, procedural — with dates]\n\n---\n\n## Immediate actions\n\n- [ ] Legal hold issued — [yes\u002Fno] — if no, run `\u002Flegal-hold [slug] --issue`\n- [ ] Matter created in log — [yes\u002Fno\u002FTBD]\n- [ ] Counsel assigned — [who]\n- [ ] Insurance tendered — [yes\u002Fno\u002FN-A]\n- [ ] Internal escalation (GC\u002FCFO\u002Fbusiness lead) — [who\u002Fwhen]\n```\n\n### Step 7: Hand off\n\nBased on recommendation and user confirmation:\n\n- Matter creation → hand off to `\u002Fmatter-intake` with: counterparty, type, `source: demand-letter` (inbound), initial theory framed defensively, pre-populated.\n- Counter-response as outbound demand → hand off to `\u002Fdemand-intake` with: counterparty, context from triage, desired outcome as the response.\n- Link to existing matter → update that matter's `related_matters` in `_log.yaml`; append event to its `history.md`.\n- Standalone → leave in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Finbound\u002F`; no portfolio change.\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- **Validate cited law.** Flags cites for the user to run through a citator (verify it is good law) or check with outside counsel. Inventing legal analysis on inbound demands is malpractice exposure.\n- **Send a response.** Drafts are drafted in `demand-draft`; this skill stops at the triage decision.\n- **Decide merit definitively.** The rating is a read for triage; a formal merit opinion lives with outside counsel or more thorough analysis.\n- **Make the matter-creation call.** Surfaces the recommendation; user decides.\n",{"name":5,"description":7,"argument-hint":23},"[path-to-incoming] [--slug=custom-slug]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdemand-received",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-received",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill demand-received",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill demand-received","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdemand-received\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",[],[]]