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…
Map allegations to contract language and draft a response letter with no unintended admissions.
Claude Code
$ npx -y skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft --agent claude-code
Codex
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a codex -y
Cursor
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a cursor -y
Gemini CLI
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a gemini-cli -y
GitHub Copilot
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a github-copilot -y
OpenCode
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a opencode -y
Windsurf
$ npx skills add CoWork-OS/CoWork-OS --skill legal-demand-letter-response-draft -a windsurf -y
name: legal-demand-letter-response-draft description: "Map allegations to contract language and draft a response letter with no unintended admissions." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Map allegations to contract language and draft a response letter with no unintended admissions.
| 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 |
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated…
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate…
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger…
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed…
Use when the user asks for a repository-wide or scoped-path security scan.
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…