Agent skill

Academic Tone Guide

by wentorai in wentorai/research-plugins

Adjust writing tone and register for academic audiences and venues

MITAuto-check passedWriting & Content

Install Academic Tone Guide

skills CLI
$ npx skills add wentorai/research-plugins --skill academic-tone-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wentorai/research-plugins academic-tone-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
academic-tone-guide
GitHub stars
298
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
240 words
Files
1
Skills in repo
405
Repo updated
First seen
Licence
MIT

At a glance

Adjust writing tone and register for academic audiences and venues

  • Writing & Content work in your project
  • SKILL.md covers Understanding Academic Register, Hedging and Boosting, Common Tone Problems and Fixes and Authorial Voice and Person, plus 1 more section
  • Calls modal

What it does

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.

When your agent uses it

  • Writing & Content work in your project

Example prompts

  • “/academic-tone-guide”

What it can do on your machine

Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • modal

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 240 words, ~1,932 tokens.

Download SKILL.mdSave it as .claude/skills/academic-tone-guide/SKILL.md (or your agent's skills folder).
name
academic-tone-guide
description
Adjust writing tone and register for academic audiences and venues

Academic Tone Guide

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.

Understanding Academic Register

The Register Spectrum

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.

Discipline-Specific Norms
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 common

Hedging and Boosting

Hedging Language

Hedging 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")
When to Hedge and When Not To
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...")

Common Tone Problems and Fixes

Informal Language
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 numbers
Overconfident Claims
Problem: 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."
Emotional Language
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."

Authorial Voice and Person

First Person Usage

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 papers

Practical Revision Checklist

Tone 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

Files

Just SKILL.md in skills/writing/polish/academic-tone-guide of wentorai/research-plugins.

Open the folder on GitHubat commit bf44b3c

Used in 1 other repository

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.

Compare with similar skills

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.

Academic Tone Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Academic Tone Guide this skillwentorai/research-plugins2981 repos~1.9kAutomated safety check: PassMIT
Anti-Defensive Writing EditorKiterlin/anti-defensive-writing875—~3.5kAutomated safety check: PassMIT
Humanities Writing Companiontizzy916/humanities-writing-companion436—~3.4kAutomated safety check: PassCC-BY-NC-4.0
Academic Writing Assistantdonghuixin/AI-Vibe-Writing-Skills497—~616Automated safety check: PassMIT
Academic Prose De-AI Editorheise3/academic-deai254—~1.4kAutomated safety check: PassMIT
Content Trend Researcheralirezarezvani/claude-code-skill-factory8821 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • 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.

    875 GitHub stars~3.5k tokensUpdated 10 days ago
    Writing & ContentAuto-check passed
  • Humanities Writing Companion

    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.

    436 GitHub stars~3.4k tokensUpdated 19 days ago
    Writing & ContentAuto-check passed
  • Academic Writing Assistant

    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.

    497 GitHub stars~616 tokensUpdated 28 days ago
    Writing & ContentAuto-check passed
  • Academic Prose De-AI Editor

    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.

    254 GitHub stars~1.4k tokensUpdated 3 days ago
    Writing & ContentAuto-check passed
  • Content Trend Researcher

    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…

    882 GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed
  • Scholar Anti AI Writing

    catlog22/maestro-flow

    Remove AI writing patterns from academic prose. An agent skill from catlog22/maestro-flow.

    564 GitHub stars~1.7k tokensUpdated 3 days ago
    Writing & ContentAuto-check: notes

More from wentorai/research-plugins

All 405 skills in this repo
  • Abstract Writing Guide

    wentorai/research-plugins

    Craft structured research abstracts that maximize clarity and journal acceptance

    298 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Academic Citation Manager

    wentorai/research-plugins

    Manage academic citations across BibTeX, APA, MLA, and Chicago formats

    298 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Academic Paper Summarizer

    wentorai/research-plugins

    Summarize academic papers with structured extraction of key elements

    298 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Academic Study Methods

    wentorai/research-plugins

    Evidence-based study techniques for academic learning and retention

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Academic Translation Guide

    wentorai/research-plugins

    Academic translation, post-editing, and Chinglish correction guide

    298 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • Academic Web Scraping

    wentorai/research-plugins

    Ethical web scraping and API-based data collection for research

    298 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

Questions about Academic Tone Guide

What does Academic Tone Guide do?

Adjust writing tone and register for academic audiences and venues. Academic Tone Guide is an agent skill from wentorai/research-plugins.

When should I use Academic Tone Guide?

Academic Tone Guide fits situations like: writing & Content work in your project.

How do I install Academic Tone Guide in Claude Code?

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.

How do I install Academic Tone Guide in Codex?

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.

Can I use Academic Tone Guide in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Academic Tone Guide need to run?

Going by SKILL.md and its folder, Academic Tone Guide needs the command-line tools its instructions call (modal).

Does Academic Tone Guide access the network?

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.

Is Academic Tone Guide safe to install?

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.

What licence does Academic Tone Guide use?

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.

How many tokens does Academic Tone Guide use?

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.

What are the alternatives to Academic Tone Guide?

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.

Who maintains Academic Tone Guide?

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.