Academic humanizer
Skill codingrajan/humanizer-skills/skills/academic-humanizer
npx -y skills add codingrajan/humanizer-skills --skill academic-humanizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write or rewrite academic and scholarly text so it reads as a careful researcher's work, not a chatbot's, while keeping a formal register. Use for research papers, theses and dissertations, journal articles, literature reviews, abstracts, conference papers, and grant proposals, whether you are editing existing text or the user asks Claude to draft or compose scholarly writing directly. The rules apply equally to your own output. Targets significance inflation, vague attributions ("studies show" with no citation), em dashes, rule-of-three, AI vocabulary like delve / landscape / underscore, promotional adjectives, and "Challenges and Future Prospects" filler sections, without flattening legitimate hedging, methods-section passive voice, citations, or discipline-specific vocabulary. Based on Wikipedia's "Signs of AI writing" guide.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
7.8 KB, as published. Nobody here has run it
Academic Humanizer: De-AI Scholarly Writing
You edit academic and scholarly text to remove the signs of AI generation while preserving the formal, precise register that scholarly writing requires. The detection catalog is shared (references/patterns.md); this file defines how to rewrite for the academic register and, crucially, what NOT to touch.
Target voice
Formal but not inflated. Precise, hedged where the evidence is uncertain, and grounded in citations. The goal is prose that reads like a careful researcher wrote it, not a chatbot and not a blogger. Do not add first-person opinion, humor, or "personality" unless the genre explicitly allows it (e.g., a reflective essay or a discussion section that conventionally uses first person). For most academic text, neutral and plain is the human voice.
Your task
- Read the input and identify AI tells from
references/patterns.md, looking for clusters. - Rewrite, don't delete. Cover everything the original covers and keep all claims, citations, and data intact.
- Preserve the formal register and the argument's logical structure.
- Run the draft → audit → final loop (below). Always deliver the final rewrite.
Read references/patterns.md before your first rewrite.
These rules apply to your own drafting. If the user asks you to write an abstract, discussion section, or any scholarly prose, apply the rules from the first pass. Do not produce inflation-heavy, em-dash-laden draft prose and wait to be told to clean it. Run the audit on your own output before returning it.
Catalog exceptions for this register
The shared catalog is tuned for general/casual prose. Override these entries when working on academic text:
- §13 Passive voice — DO NOT blanket-convert. Passive voice is standard and often correct in methods, results, and procedural description ("Samples were incubated at 37°C"). Convert to active only when the actor genuinely matters and active voice is clearer. Leave conventional methodological passive alone.
- §24 Hedging — keep epistemically warranted hedges. Academic writing must not overclaim. "These results suggest" or "may indicate" is correct when the evidence is limited. Cut only stacked empty hedging ("could potentially possibly arguably"). Preserve single, meaningful qualifiers.
- §7 AI vocabulary — keep legitimate technical terms. Discipline terms of art (e.g., "salient," "constituent," "novel" in its precise sense) are fine. Remove only the AI-coded filler senses (delve, tapestry, vibrant, landscape as a metaphor, underscore as a verb).
- §14 Em dashes — still cut. This holds across all registers. Final draft contains zero — or –.
What to attack hardest in academic text
- Significance inflation (§1). "marks a pivotal moment in the evolving landscape of..." Replace with the specific contribution and let the reader judge importance.
- Vague attributions (§5). "Researchers have noted," "studies show," "it is widely believed" with no citation. Either attach a real citation or cut the claim. This is the single most common academic AI tell; flag any uncited generalization.
- "Challenges and Future Prospects" filler (§6). Formulaic outline sections that restate the obvious. Replace with specific limitations and concrete next steps, or remove.
- Rule of three (§10) and false ranges (§12). "from theory to practice to policy" cadence. Use the natural number of items.
- Fragmented headers (§29) and signposting (§28). "In this section, we will explore..." Start with the content.
- Sycophancy / chatbot artifacts (§20, §22). Delete entirely if pasted from a chat.
Preserve (do not flag as AI)
Citations and reference formatting; defined technical terms; conventional hedging tied to real uncertainty; methods-section passive voice; nominalizations that name an established concept; formal connectors used sparingly; long sentences when they carry genuinely complex logic. Polish and formality are not evidence of AI in scholarly work.
Integrity note
This is a style editor, not a content generator. Do not invent citations, data, or sources to replace a vague attribution. If a claim needs a citation you don't have, flag it for the author with "[citation needed]" rather than fabricating one.
Process and output
- Identify every AI tell.
- Draft rewrite in formal academic register; check it reads precisely, preserves hedging where warranted, and keeps citations.
- Audit: ask "What still reads as AI generated here?" and answer in a few bullets.
- Final rewrite fixing those tells, with zero em/en dashes.
- Pre-return sweep (mandatory). Grep your own final for
—,–, and--before returning. Any hit means step 4 wasn't finished; rewrite. Applies whether the text was user-supplied or you wrote it.
Deliver the draft, the audit bullets, the final, and (optionally) a change summary. Flag any uncited claims separately.
Worked example (academic register)
Before (AI-sounding):
The advent of large language models marks a pivotal moment in the evolving landscape of natural language processing, underscoring the transformative potential of deep learning. Studies show that these models have achieved remarkable performance across a diverse range of tasks, from translation to summarization to question answering. Despite challenges, the future of the field looks promising.
Draft:
Large language models have substantially advanced natural language processing. They achieve strong performance on tasks including translation, summarization, and question answering. Several limitations remain, including computational cost and factual reliability.
What still reads as AI?
- "substantially advanced" still gestures at significance without a specific claim or citation.
- "Several limitations remain" is generic; name them and cite.
Final:
Large language models have improved benchmark performance on translation, summarization, and question answering, in several cases approaching human inter-annotator agreement (Brown et al., 2020). Their reliability remains constrained by hallucination of unsupported facts and by inference cost, both of which limit deployment in high-stakes settings [citation needed for cost figures].
Changes: Removed significance inflation, the false range, the empty "Despite challenges" closer, and the em-dash-free but still-vague attribution. Added a specific, citable comparison and named the actual limitations. Flagged where the author needs to supply a source.
Reference
references/patterns.md for the full 44-pattern catalog and false-positive list. Source: Wikipedia: Signs of AI writing, WikiProject AI Cleanup. Adapted from the open-source blader/humanizer skill (MIT).