nondefensive-writing
Skill4 starsChanged 31 days agoMITView on GitHub
Revise manuscript prose that sounds like a rebuttal, repeats assurances, or accumulates caveats. Separate defensive framing from necessary limitations and retain the scientific meaning while making targeted edits.
In this repository17 other files it gives its agents.
- academic-prose-editingSkill
- academic-writing-auditSkill
- claim-evidence-auditSkill
- experiment-comparison-auditSkill
- figure-caption-auditSkill
- latex-bibliography-auditSkill
- manuscript-release-checkSkill
- method-definition-auditSkill
- reference-authenticity-auditSkill
- related-work-synthesisSkill
- research-manuscript-writingSkill
- results-interpretationSkill
- reviewer-comment-triageSkill
- reviewer-response-writingSkill
- revision-integrity-auditSkill
- scientific-story-auditSkill
- word-citation-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Keep useful Results interpretation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nondefensive Writing
Turn anticipated objections into useful information for the reader. Remove the performance of reassurance while preserving the definitions, boundaries, and interpretation that make a statement accurate.
Establish the passage's job
Read the surrounding sentences and the supplied evidence. Determine the requested scope and whether the user wants diagnosis or replacement text. An authorized revision can proceed directly. A manuscript paragraph and a response letter have different purposes: a response letter may address a reviewer explicitly; the paper should explain the research.
For each questionable sentence, assess three things separately:
- Function: What would readers misunderstand if the underlying fact disappeared?
- Formulation: Does the wording convey that fact, or stage an objection and an assurance?
- Placement: Does the reader need it here, and is the same job already done nearby?
An important fact can have poor wording or excessive repetition. Conversely, negative wording can carry an essential rule. Do not classify a sentence by words such as “not,” “only,” “fixed,” “excluded,” or “limited.”
In an introduction, test each doubtful sentence against the narrowing line from existing progress through gap and motivation to contribution. Remove explanation that merely repeats background or anticipates an objection without advancing that line. Keep the short premise, definition, or consequential boundary needed to understand the next step. A conference introduction may integrate gap and motivation compactly; a journal introduction should make their distinct reasoning explicit according to the target's requirements. Do not turn “avoid explanation for its own sake” into deletion of the rationale that makes the work necessary.
Research preparation may critically test assumptions and alternatives. Manuscript prose should present the resulting reasoning, with the supported contribution stated directly and uncertainty attached to the claim it qualifies. Separate a live scientific uncertainty from resolved exploratory doubt or an imagined objection. Preserve the former when it affects interpretation; do not transplant the entire internal debate into the paper. Good storytelling keeps evidence and material limitations visible while helping the reader follow one scientific question.
Choose a concrete edit
- Keep a clear definition, algorithmic exclusion, study endpoint, assumption, consequential limitation, or supported interpretation.
- Clarify a useful fact hidden behind “we stress,” “it should be emphasized,” or a claim of rigor. State the actual operation or observation.
- Merge assurances that repeat the same protocol fact for the same purpose.
- Move detail only when its new location still supports the relevant inference. Do not hide a consequential limitation in an appendix to improve tone.
- Delete rebuttal staging or repetition that adds no necessary reader information.
Preserve differences in data, tuning, eligibility, or resources when they change the interpretation of a comparison. Preserve what was not measured when readers might otherwise infer that endpoint. A precise boundary can replace several generic disclaimers, but brevity does not justify concealing it.
Keep useful Results interpretation. “Consistent with the proposed explanation” may be appropriate when supported; merely adding “may” cannot rescue an explanation with no evidential link. State the observation and identify the missing link instead. Do not convert descriptive findings into causal or safety claims.
Worked example
Draft: “We emphasize that incomplete measurements were not quietly discarded. They were not assigned a concentration estimate. No one should infer that our system guarantees reliable field operation.”
Supplied facts: Incomplete measurements receive an abstention, remain in the denominator, and have no concentration estimate. Field operation was not evaluated.
Repair: “Incomplete measurements received an abstention rather than a concentration estimate and remained in the evaluation denominator. The study did not evaluate field operation.”
The repair removes accusation and reassurance while retaining two necessary negative facts. If the preceding sentence already explains the measurement challenge clearly, leave it unchanged.
Prose when drafting or revising
When drafting or revising prose, including audit explanations, read prose editing rules. Preserve scientific meaning, necessary reasoning and valid technical terms. Keep sound passages, do not add unreported properties, and limit edits to the requested scope. The local reference covers concept accuracy, clear sentences, repetition and punctuation, including the required exceptions.
Deliver and stop
Return the requested audit or affected replacement text with brief reasons that identify what changed and what was preserved. Mark an unchanged passage explicitly when omission could be mistaken for deletion. Follow the user's requested format rather than imposing a long checklist.
Reread across each edit: the motivation-to-method bridge, endpoint, denominator, operative rule, and inference should retain their meaning wherever relevant. Stop once the defensive framing and actual redundancy are resolved. Do not continue polishing sound prose, add new caveats by habit, or turn an editorial request into an experimental program.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

