Tooluck logoTooluck
SKILL.md

anti-defensive-writing-en

Agent skill fromAdkid-Zephyr/anti-defensive-writing-Skill

Stops defensive writing across the entire paper lifecycle — writing, revising, cutting, and organizing experiments. Treats the paper as a press conference, not a project summary, lab log, or self-audit: identify the single most publishable strength of the work and build the most favorable, complete, and persuasive narrative around it. Never present everything evenly, never volunteer weakness, never write an experiment diary, never attack the paper on the reviewer's behalf. Triggers: polish my paper, revise manuscript, write abstract, write introduction, write conclusion, shorten paper, rebuttal, respond to reviewers, organize experiments, defensive writing, AI-flavored academic writing.

How to install anti-defensive-writing-en

install anti-defensive-writing-en
# install the anti-defensive-writing-Skill pack with the skills CLI
npx skills add Adkid-Zephyr/anti-defensive-writing-Skill

# or add only this skill to Claude Code: copy the folder

skills/anti-defensive-writing-en/

# into

~/.claude/skills/anti-defensive-writing-en/ (all projects)

.claude/skills/anti-defensive-writing-en/ (one project)

skills/anti-defensive-writing-en/SKILL.md

MITFull file
1# The Press-Release Principle (Paper as Press Conference)
2
3## One-line principle
4
5A paper is a press conference, not a project summary, a lab log, or a self-audit.
6Your job is not to present every aspect of the work evenly, but to identify its
7most publishable value and build the most favorable, complete, and persuasive
8narrative around it.
9
10## 1. Narrative rules
11
121. **Organize the paper around strengths only.** Look for what is genuinely ahead,
13 unique, or irreplaceable: a new capability, a new problem, a new mechanism, a new
14 perspective, broader applicability, lower cost, higher efficiency, better
15 scalability, or a more meaningful trade-off. Content that forms no advantage
16 does not enter the main storyline.
172. **Do not write a work report.** No "we first did X, then tried Y, and Z failed"
18 chronology. Keep only the final standing logic: why the problem matters → why
19 existing methods fall short → what this paper provides → how the evidence
20 supports it.
213. **Never set a contest you cannot win.** If a metric is not your strength, do not
22 build the narrative on it. Re-choose the task definition, evaluation dimension,
23 application scenario, constraint, or comparison frame that best reflects your
24 value. Name the game this paper actually wins.
254. **State the advantage explicitly.** Do not expect reviewers to discover the
26 contribution from a table. Explain: under which condition the method performs
27…

Excerpt shown under the repository's MIT license.

More skills in anti-defensive-writing-Skill

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates