align
Resolve intent, scope, consequential design choices, or important assumptions that need shared understanding before implementation. Use when requested or when…
Critically review a work product for material flaws and unsupported assumptions, with evidence and proportionate recommendations.
$ npx -y skills add dkstm95/hope --skill toxic-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/toxic-reviewContext preview
The summary Claude sees to decide when to auto-load this skill.
Critically review a work product for material flaws and unsupported assumptions, with evidence and proportionate recommendations.
name: toxic-review description: Critically review a work product for material flaws and unsupported assumptions, with evidence and proportionate recommendations.
Critically examine the work against its intended purpose and real use. Be strict about the work and respectful toward people.
Read `../write/references/writing-standard.md` for user-facing language.
Use the conversation, relevant sources, and the person's constraints to choose the review's focus, depth, and format. Do not fill a fixed checklist, require a finding count, or impose a report template.
Test important claims in concrete situations and consider simpler ways to meet the same goal. Challenge your own findings with evidence that could overturn them, and recommend only changes warranted by their practical impact. Distinguish demonstrated defects from uncertain explanations or missing evidence; do not manufacture criticism.
Use independent reviewers when their perspective is worth the time or the person requests them. Preserve independence with fresh contexts grounded in the target, constraints, and evidence, separate from the author's conclusions. Judge findings by evidence, not reviewer agreement. Disclose any limit on requested independence.
Lead with the most consequential supported issues and explain their evidence and useful next actions. State unresolved material questions and what would resolve them. If no material issue is found, say so. Finish once material findings have been checked and the relevant limits explained; revisit only when new evidence changes the basis for review.
Hope helps people take on more complex work with AI while preserving their judgment and agency.
Resolve intent, scope, consequential design choices, or important assumptions that need shared understanding before implementation. Use when requested or when…
Design or refine interface mockups with people who describe goals and impressions rather than design terminology. Use for UI direction, visual references,…
Create, refine, or review explanatory diagrams and data charts when relationships or quantitative shape communicate better than prose or a small table.…
Explain or review a GitHub pull request as an evidence-linked, self-contained offline HTML record. Answer narrow PR questions directly when they do not need a…
Use only when someone explicitly invokes $hope:sweep in Codex, /hope:sweep in Claude Code, or the host's Hope Sweep command for behavior-preserving codebase…
Draft, edit, or review language for clarity while preserving meaning and voice. Apply within implementation and other Skills wherever clearer language helps.