Skip to content
Skill

anti-defensive-writing

by Kiterlin

AI Summary

Advance the claim directly. Say what is true, what the text argues, what the evidence shows, or what the method does. Do not default to explaining what the text does not claim, does not prove, does not imply, does not cover, or does not attempt. Use a calm, competent authorial posture. Write as an a

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "anti-defensive-writing" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/anti-defensive-writing && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/anti-defensive-writing/SKILL.md "https://raw.githubusercontent.com/Kiterlin/anti-defensive-writing/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use when drafting or revising academic writing, papers, essays, abstracts, introductions, contribution statements, discussions, conclusions, technical explanations, grant writing, product writing, policy writing, professional reports, or any text the user wants to be clearer, stronger, more direct, more concise, more confident, less verbose, less caveated, less apologetic, or less defensive.

Examples

Defensive: > We do not claim that these cases are representative of all contexts. Stronger: > The cases show how the mechanism operates across three institutional settings. Defensive: > This paper is not intended to provide a comprehensive theory of platform governance, but rather to examine one specific mechanism. Stronger: > This paper identifies a mechanism through which platform governance reshapes participation. Defensive: > This does not mean that policy design alone determines implementation outcomes. Stronger: > Implementation outcomes depend on how policy design interacts with administrative capacity. Defensive: > While the sample is limited and cannot capture every variation, it still offers useful insights. Stronger: > The sample captures the variation most relevant to the study's theoretical question. Defensive: > We are not arguing that this model is superior in every situation. Stronger: > The model is most useful when the task requires interpretable comparisons across cases.

Core Rule

Advance the claim directly. Say what is true, what the text argues, what the evidence shows, or what the method does. Do not default to explaining what the text does not claim, does not prove, does not imply, does not cover, or does not attempt. Use a calm, competent authorial posture. Write as an author explaining an argument to the reader, not as an author negotiating with an imagined critic.

Preserve Necessary Precision

Keep limitations when they are necessary for accuracy, ethics, law, safety, or methodological transparency. A limitation is necessary when it affects: • the validity of the claim; • the interpretation of the evidence; • the scope of application; • the research design; • the reader's ability to use the result correctly. Write necessary limitations once, clearly and calmly. Place them in the appropriate section, usually methods, discussion, or limitations. Do not scatter them through abstracts, introductions, contribution paragraphs, topic sentences, conclusions, or executive summaries unless the limitation is essential to that exact sentence.

Detection Checklist

Before finalizing a draft or revision, check for: • unnecessary disclaimers; • repeated statements of what the text does not claim; • excessive hedging; • caveats in high-impact positions; • paragraphs that start with limitations; • negative framing where positive framing would work; • explanations added only to prevent hypothetical misunderstanding; • self-undermining contribution statements; • unnecessary "not X but Y" structures; • redundant "however", "nevertheless", or "although" transitions. Revise any item that weakens the text without improving accuracy.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 2mo ago
Active
AdoptionUnder 100 stars
59 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars59
Forks2
Issues0
Updated2mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code