Automated summary
This skill guides the revision of academic and professional prose by stripping unnecessary caveats, apology-like framing, excessive hedging, and defensive over-explanation, while preserving the limitations that are genuinely required.
Strengths
- Provides a precise detection checklist (redundant disclaimers, caveats in high-impact positions, pointless "not X but Y" structures).
- Explicitly separates a necessary limitation (validity, ethics, law, safety, methodology) from a superfluous disclaimer.
- Offers a step-by-step rewrite procedure with directly applicable before/after examples.
- Enforces disciplined placement of limitations (methods, discussion, dedicated section) instead of scattering them through abstracts and conclusions.
Limitations
- Does not check facts or argument strength: it makes text more direct, not more correct.
- Applied mechanically, it can push a draft into overclaiming if the author misidentifies which limits are actually required.
- Purely stylistic: it performs no automatic analysis of readability or writing quality.
Use it when a draft reads hesitant, verbose, or over-cautious and you want firmer phrasing without sacrificing accuracy.
Avoid it on texts where qualifications are the substance, such as legal opinions, safety warnings, or regulatory clauses.
Security analysis
SafeThis skill contains only writing guidance and contains no executable commands, tool usage, file operations, network calls, credential handling, or instructions to disable safety. Declared allowed-tools are none, so listing it presents no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Here is the abstract of my paper. Rewrite it so it leads with the claim, removes unnecessary caveats and hedges, and keeps only the scope conditions that genuinely affect how the result should be read: [paste abstract]This introduction opens with three sentences about what the paper does not claim. Rebuild the paragraphs around the main contribution, using positive scope statements, and move any real methodological limitation to a single clear sentence: [paste section]Revise this report section to replace stacked hedging ("may suggest", "could potentially") with precise claims, spelling out the source of uncertainty where it is real rather than vague: [paste text]name: anti-defensive-writing 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.
Anti-Defensive Writing
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.
Rewrite Procedure
- Identify the function of the defensive sentence.
Classify it as one of:
- unnecessary disclaimer;
- necessary scope condition;
- real methodological limitation;
- useful conceptual contrast;
- evidence-based qualification;
- redundant clarification.
- Delete unnecessary disclaimers.
Remove any sentence that does not add evidence, scope, logic, conceptual precision, or necessary reader guidance.
- Convert defensive limitation into positive scope.
Prefer:
The analysis focuses on urban governance cases from 2015 to 2023.
Avoid:
We do not claim that these cases are representative of all urban governance contexts.
- Replace hedging with precision.
Prefer:
The evidence indicates that X influences Y in these cases.
Avoid:
This may suggest that X could potentially influence Y.
If uncertainty is real, specify its source:
The available evidence supports this interpretation, although the design does not estimate population-level effects.
- Rebuild the paragraph around the main point.
Ensure the paragraph has:
- a clear topic sentence;
- one main job;
- a logical sequence;
- no repeated caveats;
- no apology-like framing;
- a direct connection to the larger argument.
Writing Principles
Lead with the claim. Start paragraphs with the point, not with a caveat.
Use positive scope. State what the text examines, explains, tests, compares, or contributes.
Strengthen with evidence, not apology. When a claim feels too broad, improve the concepts, evidence, causal logic, scope, or paragraph structure instead of adding protective caveats.
Keep one paragraph, one job. Do not mix argument, caveat, apology, exception, and clarification in the same paragraph.
Use contrast only when the contrast itself is part of the argument. Avoid reflexive "not X but Y", "rather than", "instead of", "to be clear", and "it should be noted that" structures.
Preferred Patterns
Use patterns like:
- "This paper examines..."
- "This study shows..."
- "The analysis focuses on..."
- "The evidence indicates..."
- "This design allows..."
- "The results suggest..."
- "The central contribution is..."
- "This section explains..."
- "The argument proceeds in three steps..."
- "In this setting, X shapes Y by..."
Discouraged Patterns
Avoid these unless they are necessary for accuracy:
- "This paper does not claim..."
- "We do not attempt to..."
- "This is not to say that..."
- "This should not be taken to mean..."
- "The goal is not X but Y..."
- "Rather than arguing X, this paper argues Y..."
- "Although this study has limitations..."
- "Of course, this does not fully capture..."
- "It is worth noting that..."
- "To be clear..."
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.
Final Pass
Before producing the final answer, remove any sentence that exists mainly to protect against a hypothetical objection rather than to advance the text. Deliver text that is concise, direct, confident, logically organized, and free of unnecessary disclaimers.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/anti-defensive-writing-msba3ndz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/anti-defensive-writing-msba3ndz/download' --output '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md.part' && mv '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md.part' '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && test -s '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/anti-defensive-writing' && cp -R '.skill-downloads/anti-defensive-writing-msba3ndz' '.claude/skills/anti-defensive-writing'Cursor
test -f '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && test -s '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/anti-defensive-writing' && cp -R '.skill-downloads/anti-defensive-writing-msba3ndz' '.cursor/skills/anti-defensive-writing'Codex
test -f '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && test -s '.skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/anti-defensive-writing' && cp -R '.skill-downloads/anti-defensive-writing-msba3ndz' '.agents/skills/anti-defensive-writing'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/anti-defensive-writing-msba3ndz'openskills read 'anti-defensive-writing-msba3ndz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/anti-defensive-writing-msba3ndz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Writing Fragments
Content
Mine raw writing fragments through a relentless interview, without imposing structure. Capture ideas, quotes, and leading words for later use.
UI Copywriting & Auditing
Content
Write or audit user-facing UI copy including buttons, errors, empty states, and tooltips across the monorepo, following the design system source of truth.
Music MIDI Extraction
Content
Extracts the MIDI or score from an existing music production via the CogMusic MCP tool and confirms availability.