Anti-Defensive Writing Editor
Kiterlin/anti-defensive-writing
Edits drafts to strip needless caveats, hedges and disclaimers while keeping the limits that matter for accuracy, ethics, law, safety and method.
Adjust writing tone and register for academic audiences and venues
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins academic-tone-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .claude/skills/academic-tone-guide && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .claude/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins academic-tone-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .agents/skills/academic-tone-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .agents/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins academic-tone-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .cursor/skills/academic-tone-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .cursor/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wentorai/research-plugins.git --path skills/writing/polish/academic-tone-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins academic-tone-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .gemini/skills/academic-tone-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .gemini/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wentorai/research-plugins academic-tone-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .github/skills/academic-tone-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .github/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins academic-tone-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing/polish/academic-tone-guide .opencode/skills/academic-tone-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "academic-tone-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/polish/academic-tone-guide into .opencode/skills/academic-tone-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "academic-tone-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
academic-tone-guideAdjust writing tone and register for academic audiences and venues
Academic Tone Guide is an agent skill from wentorai/research-plugins. Adjust writing tone and register for academic audiences and venues
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
modalFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Academic Tone Guide loads about 1.9k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 240 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 240 words, ~1,932 tokens.
.claude/skills/academic-tone-guide/SKILL.md (or your agent's skills folder).A skill for adjusting the tone, register, and voice of academic writing to match disciplinary expectations and target venue conventions. Covers the spectrum from informal drafts to publication-ready prose, including hedging language, impersonal constructions, discipline-specific stylistic norms, and common tone pitfalls that undermine credibility.
Academic writing occupies a specific position on the formality spectrum. The appropriate register depends on the genre (journal article, conference paper, thesis, grant proposal, blog post) and the discipline (humanities tend toward more elaborate prose; STEM fields favor concise, direct statements).
Register Levels in Academic Writing:
Level 1 - Informal (lab notebooks, internal emails):
"We tried the new method and it worked way better."
Level 2 - Semi-formal (conference talks, blog posts):
"We tested the proposed method and observed significant improvement."
Level 3 - Formal (journal articles, theses):
"The proposed method was evaluated against the baseline, yielding
a statistically significant improvement in accuracy (p < 0.01)."
Level 4 - Highly formal (legal briefs, policy documents):
"The aforementioned methodology was subjected to rigorous
evaluation, the results of which demonstrate a statistically
significant enhancement in predictive accuracy."Most academic papers should aim for Level 3. Level 4 often sounds stilted and impedes readability. Level 2 is acceptable for workshop papers or invited commentaries but too casual for top-tier journals.
STEM Fields:
- Prefer active voice for methods: "We collected samples..."
- Use passive voice for established processes: "Samples were centrifuged..."
- Short sentences, minimal adjectives
- Precision over elegance
- Numbered equations and defined variables
Social Sciences:
- Mix of active and passive voice
- Moderate hedging: "The results suggest..." rather than "The results prove..."
- Theory-heavy introductions with clear operational definitions
- APA style typically required
Humanities:
- Complex sentence structures are acceptable
- Argumentative, first-person voice common in many fields
- Extensive engagement with prior scholarship expected
- Discipline-specific jargon must be deployed precisely
- Chicago or MLA style commonHedging is the use of cautious language to qualify claims. It signals intellectual honesty and awareness of limitations. Over-hedging weakens arguments; under-hedging invites criticism.
Hedging Devices:
Modal verbs (strength order):
might < could < may < can < should < would < will < must
"This approach might explain..." (weak claim)
"This approach may explain..." (moderate claim)
"This approach can explain..." (confident claim)
Hedging phrases:
"It appears that..."
"The evidence suggests..."
"One possible interpretation is..."
"To some extent..."
"Under certain conditions..."
Hedging quantifiers:
"Most participants..." (not "all")
"In many cases..." (not "always")
"A substantial proportion..." (not "everyone")HEDGE when:
- Reporting your own results (findings suggest, data indicate)
- Making causal claims from correlational data
- Generalizing beyond your sample
- Interpreting ambiguous results
- Discussing implications and future directions
DO NOT HEDGE when:
- Stating established facts ("DNA is a double helix")
- Describing your own methodology ("We recruited 200 participants")
- Reporting objective measurements ("The temperature was 37 degrees C")
- Citing published findings ("Smith (2020) demonstrated that...")Problem: Colloquialisms and contractions
Before: "We didn't find any significant results, which was kind of
surprising given that lots of previous studies had found
strong effects."
After: "No statistically significant effects were observed, a finding
that contrasts with the robust effects reported in prior
studies (Smith et al., 2019; Jones, 2020)."
Rules:
- No contractions (didn't -> did not, it's -> it is)
- No colloquialisms (kind of, a lot, pretty much)
- No rhetorical questions in formal papers
- Avoid first-person opinion statements without evidence
- Replace vague quantifiers with specific numbersProblem: Making claims stronger than the evidence supports
Before: "Our results prove that social media causes depression in
teenagers."
After: "Our results indicate a significant positive association
between social media usage and depressive symptoms among
adolescent participants, consistent with the hypothesis
that excessive social media engagement may contribute to
negative mental health outcomes."
Note: "Prove" is almost never appropriate in empirical research.
Use "demonstrate," "indicate," "suggest," or "support."Problem: Using emotionally charged words that bias the reader
Before: "The appalling lack of research on this devastating condition
is shocking and must be remedied immediately."
After: "Despite the substantial disease burden, the existing literature
on this condition remains limited. Further research is needed
to address critical knowledge gaps."The question of whether to use "I" or "we" in academic writing varies by discipline and journal.
Active first person (increasingly accepted in STEM):
"We designed the experiment to test..."
"We propose a novel framework for..."
"In this paper, we argue that..."
Passive alternative:
"The experiment was designed to test..."
"A novel framework is proposed for..."
"This paper argues that..."
Guidance:
- Check your target journal's style guide
- "We" is standard in multi-author papers, even in passive-heavy fields
- Single-author "I" is common in humanities, less so in STEM
- Avoid "the authors" to refer to yourself (awkward in most contexts)
- Never use "you" to address the reader in formal papersTone Audit Checklist:
1. Search for contractions -> expand all
2. Search for colloquialisms -> replace with formal equivalents
3. Check hedging on all claims -> calibrate to evidence strength
4. Verify consistent voice (active/passive) -> match journal norms
5. Remove emotional/judgmental adjectives -> use neutral descriptors
6. Check for rhetorical questions -> convert to declarative statements
7. Ensure technical terms are defined on first use
8. Verify that "significant" always means "statistically significant"
9. Remove filler phrases ("it is important to note that") -> state directly
10. Read abstract aloud -> does it sound like published papers in the venue?This checklist can be applied during the final revision pass, after substantive content editing is complete. Tone adjustments should be among the last changes made, as earlier revisions frequently introduce new informal language that needs to be caught.
© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/writing/polish/academic-tone-guide of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.
Academic Tone Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Academic Tone Guide this skillwentorai/research-plugins | 298 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Anti-Defensive Writing EditorKiterlin/anti-defensive-writing | 875 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Humanities Writing Companiontizzy916/humanities-writing-companion | 436 | — | ~3.4k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| Academic Writing Assistantdonghuixin/AI-Vibe-Writing-Skills | 497 | — | ~616 | Automated safety check: Pass | MIT | |
| Academic Prose De-AI Editorheise3/academic-deai | 254 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Content Trend Researcheralirezarezvani/claude-code-skill-factory | 882 | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Kiterlin/anti-defensive-writing
Edits drafts to strip needless caveats, hedges and disclaimers while keeping the limits that matter for accuracy, ethics, law, safety and method.
tizzy916/humanities-writing-companion
Help with humanities scholarly writing: sharpen research questions, map supplied readings, plan and draft arguments, review chapters, preserve authorial voice, and respond to reviewers.
donghuixin/AI-Vibe-Writing-Skills
Drafts and revises academic prose in the author's voice, repairs sentence flow, traces systems-paper claims to evidence and prepares reviewer responses.
heise3/academic-deai
Edits Chinese or English scholarly writing for natural phrasing and removes AI-sounding templated structure, while keeping claims, citations and author voice intact.
alirezarezvani/claude-code-skill-factory
Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven…
catlog22/maestro-flow
Remove AI writing patterns from academic prose. An agent skill from catlog22/maestro-flow.
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
wentorai/research-plugins
Ethical web scraping and API-based data collection for research
Categories
Adjust writing tone and register for academic audiences and venues. Academic Tone Guide is an agent skill from wentorai/research-plugins.
Academic Tone Guide fits situations like: writing & Content work in your project.
Run `npx skills add wentorai/research-plugins --skill academic-tone-guide -a claude-code`. Or copy the skill folder (skills/writing/polish/academic-tone-guide in wentorai/research-plugins) into .claude/skills/academic-tone-guide in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wentorai/research-plugins --skill academic-tone-guide -a codex`. Or copy the skill folder (skills/writing/polish/academic-tone-guide in wentorai/research-plugins) into .agents/skills/academic-tone-guide in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wentorai/research-plugins --skill academic-tone-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/academic-tone-guide, .gemini/skills/academic-tone-guide, .github/skills/academic-tone-guide and .opencode/skills/academic-tone-guide in your project.
Going by SKILL.md and its folder, Academic Tone Guide needs the command-line tools its instructions call (modal).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Academic Tone Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Academic Tone Guide: Anti-Defensive Writing Editor (Kiterlin/anti-defensive-writing, 875 stars), Humanities Writing Companion (tizzy916/humanities-writing-companion, 436 stars), Academic Writing Assistant (donghuixin/AI-Vibe-Writing-Skills, 497 stars) and Academic Prose De-AI Editor (heise3/academic-deai, 254 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 405 skills in this directory. The repository was last updated on June 19, 2026.
Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.