humanizer

Name: humanizer
Author: neuromechanist

37stars7forks

How to install humanizer?

neuromechanist/research-skills/humanizer

$npx -y skills add neuromechanist/research-skills --skill humanizer

Installs into the current project.

Summary

Use this skill for \"humanize this text\", \"remove AI tells\", \"make this less AI-sounding\", \"strip AI patterns\", \"de-AI my writing\", \"reduce AI-isms\", \"final natural-writing pass\", \"check for AI vocabulary\", \"em dash overuse\", \"rule of three overuse\", \"AI vocab

Files · 1

View on GitHub

SKILL.md

1	# Humanizer: Remove AI Writing Patterns
2
3	## Attribution
4
5	This skill is adapted from the upstream `humanizer` skill at https://github.com/blader/humanizer (v2.5.1) by Siqi Chen, released under the MIT License. The upstream patterns are themselves a distillation of [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup.
6
7	Upstream content (preserved with minor copyedits): the 29 AI-writing patterns and their before/after examples, the "Personality and Soul" section, the "Voice Calibration" section, the "Process" and "Output Format" sections, the "Full Example", and the closing "Reference" note.
8
9	Additions for the research-skills marketplace:
10
11	- The YAML frontmatter (rewritten in marketplace `description` style with academic-trigger phrases).
12	- The "Research writing context" section (including the "When to soften or skip a pattern", "Reconciling with research-skills conventions", and "When to invoke this skill in the writing workflow" subsections).
13	- The per-pattern "Research writing note" callouts on 11 of the 29 patterns.
14	- The "Cross-references in the research-skills marketplace" section near the end.
15
16	The MIT license is preserved in the `LICENSE` file in this skill directory; the additions above are released under MIT as well to keep upstream compatibility. National Institutes of Health (NIH), National Science Foundation (NSF), Institute of Electrical and Electronics Engineers (IEEE), American Psychological Association (APA), and American Chemical Society (ACS) referenced later in this file follow standard agency/society abbreviations.
17
18	## Your Task
19
20	You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. When given text to humanize:
21
22	1. Identify AI patterns by scanning for the patterns listed below.
23	2. Rewrite problematic sections by replacing AI-isms with natural alternatives.
24	3. Preserve meaning so the core message stays intact.
25	4. Maintain voice to match the intended tone (formal, casual, technical, academic, grant-style).
26	5. Add soul without just removing bad patterns; inject actual personality where the genre allows it.
27	6. Do a final anti-AI pass. Prompt yourself: "What makes the below so obviously AI generated?" Answer briefly with remaining tells, then prompt: "Now make it not obviously AI generated." and revise.
28
29	## Research writing context
30
31	Academic and grant writing have genre conventions that occasionally override generic "make it sound human" advice. Apply the patterns below with these calibrations:
32
33	### When to soften or skip a pattern
34
35	- Passive voice in Methods. Many biomedical, clinical, and life-sciences journals still prefer passive voice in Methods ("Samples were collected"). Active voice is preferred in research-skills overall, but do not force-rewrite Methods passages that match journal style. Pattern 13 still applies to Introduction, Results interpretation, Discussion, grant Approach narrative.
36	- Hedging in Limitations and Discussion. Pattern 24 (excessive hedging) is real, but Discussion sections legitimately use "may", "suggests", "is consistent with". Trim stacked hedges ("could potentially possibly") to single hedges ("may"). Do not strip hedges to bare assertions you cannot defend.
37	- Significance language in grants. Grant Significance and Specific Aims sections legitimately argue that work matters. Pattern 1 (significance inflation) targets meaningless filler ("pivotal moment", "evolving landscape"), not specific, evidence-backed importance claims ("affects 1.2M patients annually"). Strip the filler, keep the substance.
38	- Title case in journal headings. Pattern 17 prefers sentence case for headings. Defer to the journal's submission guidelines: IEEE, APA, ACS, and many others mandate title case. Apply pattern 17 only where house style is sentence case or unspecified.
39	- Curly quotes (pattern 19). Many publishers' copyeditors convert straight quotes to curly automatically. For LaTeX submissions, use straight quotes (`` `` ... '' ``) since LaTeX renders them correctly. For Word/Markdown drafts, follow the journal's manuscript prep guide.
40	- Boldface in clinical and technical writing. Pattern 15 targets mechanical bolding of every defined term. Selective bold for variable names, gene symbols (`TP53`), or critical war

People who liked this also viewed

6 picks

Type

humanizer

37stars7forks

View on GitHub

How to install humanizer?

neuromechanist/research-skills/humanizer

$npx -y skills add neuromechanist/research-skills --skill humanizer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Humanizer: Remove AI Writing Patterns
2
3	## Attribution
4
5	This skill is adapted from the upstream `humanizer` skill at https://github.com/blader/humanizer (v2.5.1) by Siqi Chen, released under the MIT License. The upstream patterns are themselves a distillation of [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup.
6
7	Upstream content (preserved with minor copyedits): the 29 AI-writing patterns and their before/after examples, the "Personality and Soul" section, the "Voice Calibration" section, the "Process" and "Output Format" sections, the "Full Example", and the closing "Reference" note.
8
9	Additions for the research-skills marketplace:
10
11	- The YAML frontmatter (rewritten in marketplace `description` style with academic-trigger phrases).
12	- The "Research writing context" section (including the "When to soften or skip a pattern", "Reconciling with research-skills conventions", and "When to invoke this skill in the writing workflow" subsections).
13	- The per-pattern "Research writing note" callouts on 11 of the 29 patterns.
14	- The "Cross-references in the research-skills marketplace" section near the end.
15
16	The MIT license is preserved in the `LICENSE` file in this skill directory; the additions above are released under MIT as well to keep upstream compatibility. National Institutes of Health (NIH), National Science Foundation (NSF), Institute of Electrical and Electronics Engineers (IEEE), American Psychological Association (APA), and American Chemical Society (ACS) referenced later in this file follow standard agency/society abbreviations.
17
18	## Your Task
19
20	You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. When given text to humanize:
21
22	1. Identify AI patterns by scanning for the patterns listed below.
23	2. Rewrite problematic sections by replacing AI-isms with natural alternatives.
24	3. Preserve meaning so the core message stays intact.
25	4. Maintain voice to match the intended tone (formal, casual, technical, academic, grant-style).
26	5. Add soul without just removing bad patterns; inject actual personality where the genre allows it.
27	6. Do a final anti-AI pass. Prompt yourself: "What makes the below so obviously AI generated?" Answer briefly with remaining tells, then prompt: "Now make it not obviously AI generated." and revise.
28
29	## Research writing context
30
31	Academic and grant writing have genre conventions that occasionally override generic "make it sound human" advice. Apply the patterns below with these calibrations:
32
33	### When to soften or skip a pattern
34
35	- Passive voice in Methods. Many biomedical, clinical, and life-sciences journals still prefer passive voice in Methods ("Samples were collected"). Active voice is preferred in research-skills overall, but do not force-rewrite Methods passages that match journal style. Pattern 13 still applies to Introduction, Results interpretation, Discussion, grant Approach narrative.
36	- Hedging in Limitations and Discussion. Pattern 24 (excessive hedging) is real, but Discussion sections legitimately use "may", "suggests", "is consistent with". Trim stacked hedges ("could potentially possibly") to single hedges ("may"). Do not strip hedges to bare assertions you cannot defend.
37	- Significance language in grants. Grant Significance and Specific Aims sections legitimately argue that work matters. Pattern 1 (significance inflation) targets meaningless filler ("pivotal moment", "evolving landscape"), not specific, evidence-backed importance claims ("affects 1.2M patients annually"). Strip the filler, keep the substance.
38	- Title case in journal headings. Pattern 17 prefers sentence case for headings. Defer to the journal's submission guidelines: IEEE, APA, ACS, and many others mandate title case. Apply pattern 17 only where house style is sentence case or unspecified.
39	- Curly quotes (pattern 19). Many publishers' copyeditors convert straight quotes to curly automatically. For LaTeX submissions, use straight quotes (`` `` ... '' ``) since LaTeX renders them correctly. For Word/Markdown drafts, follow the journal's manuscript prep guide.
40	- Boldface in clinical and technical writing. Pattern 15 targets mechanical bolding of every defined term. Selective bold for variable names, gene symbols (`TP53`), or critical war

People who liked this also viewed

6 picks

Type