Codex skill for removing defensive writing and strengthening prose.
$ npx -y skills add kiterlin/anti-defensive-writing --agent claude-code
Repo: kiterlin/anti-defensive-writing
What's inside
Abstract — Scholarly and technical communication is frequently weakened by defensive writing: an authorial posture characterized by pre-emptive apologies, repetitive disclaimers, stacked modal hedges, and negative self-deprecation. While intended to ward off hypothetical criticism, defensive habits dilute the empirical strength of claims and obscure core scientific contributions.
Anti-Defensive Writing introduces an agentic skill specification that systematically diagnoses and eliminates defensive cognitive overhead while strictly preserving methodological validity, empirical scope, and ethical/legal boundaries. By replacing defensive disclaimers with positive scope definitions and calibrating uncertainty to observed evidence, this framework enables researchers and professionals to communicate findings with authoritative clarity, structural focus, and maximum signal-to-noise ratio.
The complete operational rulebook and multilingual instructions are codified in SKILL.md (comprising English Core Rules, English Extended Guidelines, Chinese Core Rules, and Chinese Extended Guidelines).
The framework establishes four fundamental pillars for rigorous, claim-forward academic communication:
| Pillar | Academic Posture | Operational Directive |
|---|---|---|
| 🎯 Claim-Forward Articulation | Assertive & Direct | Lead paragraphs and contribution sections with empirical discoveries and theoretical arguments, rather than defensive preambles. |
| 📐 Positive Scope Delimitation | Constructive & Bounded | Define boundaries by stating what the investigation does analyze, test, and explain—abandoning reflexive "We do not claim that..." formulations. |
| ⚖️ Calibrated Uncertainty | Rigorous & Precise | Differentiate between legitimate empirical limits and timid hedge stacking ("may potentially suggest"); anchor uncertainty directly to concrete design constraints. |
| 🏗️ Structural Separation of Concerns | Modular & Cohesive | Place necessary methodological limitations in dedicated sections (Methods, Discussion, Limitations), preventing dilution of abstracts, introductions, and conclusions. |
The table below contrasts conventional defensive drafts against revisions generated under the Anti-Defensive Writing paradigm across standard scholarly contexts.
| Rhetorical Dimension | Conventional Defensive Draft (❌) | Anti-Defensive Paradigm (✅) | Cognitive & Rhetorical Gain |
|---|---|---|---|
| Introduction & Hook | "Although it is beyond the scope of this modest preliminary inquiry to resolve platform governance debates, it might tentatively be suggested..." | "Algorithmic content moderation significantly reshapes user participation in online communities." | Immediate Empirical Focus: Commands reader attention by stating observed phenomena without evasive preamble. |
| Scope Delimitation | "We do not claim that our sample is representative of all municipal governance systems across regions." | "The analysis focuses on urban governance cases across three institutional jurisdictions from 2015 to 2023." | Positive Boundary Definition: Conveys exact empirical boundaries without defensive self-deprecation. |
| Uncertainty Calibration | "These experimental outcomes could potentially indicate that variable $X$ might possibly influence metric $Y$." | "The evidence indicates that $X$ influences $Y$ under the examined observational conditions." | Elimination of Hedge Stacking: Replaces multi-layered modal qualifiers with calibrated, evidence-bounded assertion. |
| Metric & Trade-off Framing | "The model achieved lower accuracy (89% vs. 90%), indicating clear performance shortcomings." | "The method reduces inference latency from 100 ms to 60 ms with 89% accuracy (compared to 90% for the baseline)." | Objective Trade-off Exposure: States system trade-offs neutrally without pathologizing valid Pareto frontiers. |
| Authorial Modesty | "This study merely attempts to take a minor exploratory step toward understanding..." | "This study establishes an empirical baseline for analyzing..." | Professional Authorial Posture: Replaces ritual modesty with calm, objective scientific authority. |
Revising text with Anti-Defensive Writing follows a formal 5-stage transformation pipeline:
┌────────────────────────────────────────────────────────┐
│ Input: Defensive Academic Draft │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Stage 1: Functional Diagnosis │
│ Classify defensive units: Unnecessary Disclaimer vs. │
│ Necessary Scope vs. Methodological Constraint │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Stage 2: Disclaimer Pruning │
│ Strip uninformative disclaimers and preemptive │
│ apologies that contribute no empirical value │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Stage 3: Positive Projection │
│ Convert negative denials ("Not X") into │
│ explicit positive definitions ("Focuses on Y") │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Stage 4: Uncertainty Calibration │
│ Collapse stacked modal hedges ("may potentially"); │
│ ground uncertainty in concrete observational limits │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Stage 5: Structural Realignment │
│ Anchor paragraphs with decisive topic sentences; │
│ isolate true constraints to dedicated sections │
└───────────────────────────┬────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────┐
│ Output: Assertive, High-Signal Paper │
└────────────────────────────────────────────────────────┘
The installation is engineered to be minimal, hermetic, and zero-overhead. Only a single specification file is deployed into your target skills environment:
<skills-directory>/
└── anti-defensive-writing/
└── SKILL.md
Zero Runtime Dependencies: The installer streams
SKILL.mddirectly. It does not clone repository archives, nor does it install README files, scripts, images, test suites, or auxiliary configurations. It requires no Git, Python, Node.js, compilation toolchains, or package managers.
| Target Environment | Global (User-Level) Destination | Local (Project-Level) Destination |
|---|---|---|
| Codex (Recommended) | ~/.agents/skills | .agents/skills |
| Codex (Legacy Runtime) | ~/.codex/skills | .codex/skills |
| Claude Code | ~/.claude/skills | .claude/skills |
Note: ~ denotes your user home directory. Relative paths resolve from the execution directory. For project-level installations, execute commands directly from the project root.
Choose one command corresponding to your target agent:
~/.agents/skills)curl -fsSL https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.sh | sh -s -- --dest "$HOME/.agents/skills"
~/.codex/skills)curl -fsSL https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.sh | sh -s -- --dest "$HOME/.codex/skills"
~/.claude/skills)curl -fsSL https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.sh | sh -s -- --dest "$HOME/.claude/skills"
For project-level installation, pass a relative destination such as --dest ".agents/skills", --dest ".codex/skills", or --dest ".claude/skills".
Open PowerShell 7 (pwsh). Configure $skillsDir to your target directory, then execute:
$skillsDir = "$HOME/.agents/skills"
$installSkill = [scriptblock]::Create((Invoke-RestMethod 'https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.ps1'))
& $installSkill -Dest $skillsDir
For alternative environments, set $skillsDir to "$HOME/.codex/skills" or "$HOME/.claude/skills". For project-level scope, specify ".agents/skills" from your project root.
Existing installations remain untouched unless explicitly updated using --force (Shell) or -Force (PowerShell). Atomic replacement guarantees that a failed network download will never corrupt an existing installation.
# Shell: Force update to latest main
curl -fsSL https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.sh | sh -s -- --dest "$HOME/.agents/skills" --force
# Shell: Pin to specific commit, tag, or branch
curl -fsSL https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/install.sh | sh -s -- --dest "$HOME/.agents/skills" --ref <commit-hash>
# PowerShell: Force update
& $installSkill -Dest $skillsDir -Force
# PowerShell: Pin reference
& $installSkill -Dest $skillsDir -Ref <commit-hash> -Force
FAQ
anti-defensive-writing is a Claude Code plugin with 1 hand-picked skill for writing work, indexed on Flowy. Install it with the command on its page. It includes anti-defensive-writing. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it