/legal-demand-letter-response-draft
Map allegations to contract language and draft a response letter with no unintended admissions.
$ npx -y skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/legal-demand-letter-response-draft
Context preview
The summary Claude sees to decide when to auto-load this skill.
Map allegations to contract language and draft a response letter with no unintended admissions.
SKILL.md
legal-demand-letter-response-draft.SKILL.mdname: legal-demand-letter-response-draft
description: "Map allegations to contract language and draft a response letter with no unintended admissions."
Legal Demand Letter Response Draft
Purpose
Map allegations to contract language and draft a response letter with no unintended admissions.
Routing
- Use when: Use when a demand letter must be analyzed and answered against contract language.
- Do not use when: Do not use when the task is generic writing unrelated to legal allegations.
- Outputs: Allegation map and response draft with section-level legal grounding.
- Success criteria: Produces a defensible response draft, avoids unsupported admissions, and writes both artifacts.
Trigger Examples
Positive
- Use the legal-demand-letter-response-draft skill for this request.
- Help me with legal demand letter response draft.
- Use when a demand letter must be analyzed and answered against contract language.
- Legal Demand Letter Response Draft: provide an actionable result.
Negative
- Do not use when the task is generic writing unrelated to legal allegations.
- Do not use legal-demand-letter-response-draft for unrelated requests.
- This request is outside legal demand letter response draft scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | agreement_path | string | No | Optional explicit path to the governing contract | | demand_letter_path | string | No | Optional explicit path to the demand letter | | facts_path | string | No | Optional chronology/facts memo path | | client_role | select | No | Role of your client in the dispute | | response_output_path | string | No | Where to write the draft response letter | | issues_table_output_path | string | No | Where to write the allegation mapping table |
Runtime Prompt
- Current runtime prompt length: 1932 characters.
- Runtime prompt is defined directly in `../legal-demand-letter-response-draft.json`.
Read more
name: legal-demand-letter-response-draft description: "Map allegations to contract language and draft a response letter with no unintended admissions."
Legal Demand Letter Response Draft
Purpose
Map allegations to contract language and draft a response letter with no unintended admissions.
Routing
- Use when: Use when a demand letter must be analyzed and answered against contract language.
- Do not use when: Do not use when the task is generic writing unrelated to legal allegations.
- Outputs: Allegation map and response draft with section-level legal grounding.
- Success criteria: Produces a defensible response draft, avoids unsupported admissions, and writes both artifacts.
Trigger Examples
Positive
- Use the legal-demand-letter-response-draft skill for this request.
- Help me with legal demand letter response draft.
- Use when a demand letter must be analyzed and answered against contract language.
- Legal Demand Letter Response Draft: provide an actionable result.
Negative
- Do not use when the task is generic writing unrelated to legal allegations.
- Do not use legal-demand-letter-response-draft for unrelated requests.
- This request is outside legal demand letter response draft scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | agreement_path | string | No | Optional explicit path to the governing contract | | demand_letter_path | string | No | Optional explicit path to the demand letter | | facts_path | string | No | Optional chronology/facts memo path | | client_role | select | No | Role of your client in the dispute | | response_output_path | string | No | Where to write the draft response letter | | issues_table_output_path | string | No | Where to write the allegation mapping table |
Runtime Prompt
- Current runtime prompt length: 1932 characters.
- Runtime prompt is defined directly in `../legal-demand-letter-response-draft.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill