Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Agent skill
by brycewang-stanford in brycewang-stanford/Auto-Empirical-Research-Skills
Audit and rewrite content to remove AI writing patterns ("AI-isms").
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --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/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .claude/skills/avoid-ai-writing && 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 "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .claude/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writingType 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .agents/skills/avoid-ai-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .agents/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .cursor/skills/avoid-ai-writing && 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 "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .cursor/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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/brycewang-stanford/Auto-Empirical-Research-Skills.git --path skills/47-conorbronsdon-avoid-ai-writing--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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .gemini/skills/avoid-ai-writing && 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 "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .gemini/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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 brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writingInstalls 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .github/skills/avoid-ai-writing && 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 "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .github/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .opencode/skills/avoid-ai-writing && 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 "avoid-ai-writing" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/47-conorbronsdon-avoid-ai-writing into .opencode/skills/avoid-ai-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "avoid-ai-writing", 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.
avoid-ai-writingAudit and rewrite content to remove AI writing patterns ("AI-isms").
Avoid AI Writing is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detection-only mode that flags patterns without rewriting.
Its SKILL.md is about 8.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `CHANGELOG.md`, `CLAUDE.md` and `README-original.md`). Compatibility notes: Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No…
It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: 🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库,覆盖8大社会科学学科的实证研究。CoPaper.AI… The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9fa87d8. 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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom 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.
Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required.
From compatibility in the SKILL.md frontmatter.
Avoid AI Writing loads about 8.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 4,586 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 brycewang-stanford/Auto-Empirical-Research-Skills at commit 9fa87d8, republished under its MIT licence (© brycewang-stanford). 4,586 words, ~8,430 tokens.
.claude/skills/avoid-ai-writing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.You are editing content to remove AI writing patterns ("AI-isms") that make text sound machine-generated.
This skill operates in one of two modes:
rewrite (default) — Flag AI-isms and rewrite the text to fix them.
detect — Flag AI-isms only. No rewriting. Use this mode when:
Trigger detect mode when the user says "detect," "flag only," "audit only," "just flag," "scan," "what AI patterns are in this," or similar. Default to rewrite mode if not specified.
In rewrite mode, your job is to:
In detect mode, your job is to:
## 🚀 What This Means. Exception: social posts may use one or two emoji sparingly — at the end of a line, never mid-sentence.genuine, real (as in "a real improvement"), truly, quite frankly, to be honest, let's be clear, it's worth noting that. Just state the fact.worth reading, worth paying attention to, worth a look, worth exploring, worth checking out, worth your time. These substitute a generic thumbs-up for a specific reason. Say why something matters instead.perhaps, could potentially, it's important to note that, to be clear. Make the point directly.Words are organized into three tiers based on how reliably they signal AI-generated text. This tiered approach — adapted from brandonwise/humanizer's vocabulary research — reduces false positives on words that are fine in isolation but suspicious in clusters.
| Replace | With |
|---|---|
| delve / delve into | explore, dig into, look at |
| landscape (metaphor) | field, space, industry, world |
| tapestry | (describe the actual complexity) |
| realm | area, field, domain |
| paradigm | model, approach, framework |
| embark | start, begin |
| beacon | (rewrite entirely) |
| testament to | shows, proves, demonstrates |
| robust | strong, reliable, solid |
| comprehensive | thorough, complete, full |
| cutting-edge | latest, newest, advanced |
| leverage (verb) | use |
| pivotal | important, key, critical |
| underscores | highlights, shows |
| meticulous / meticulously | careful, detailed, precise |
| seamless / seamlessly | smooth, easy, without friction |
| game-changer / game-changing | describe what specifically changed and why it matters |
| hit differently / hits different | (say what specifically changed, or cut) |
| utilize | use |
| watershed moment | turning point, shift (or describe what changed) |
| marking a pivotal moment | (state what happened) |
| the future looks bright | (cut — say something specific or nothing) |
| only time will tell | (cut — say something specific or nothing) |
| nestled | is located, sits, is in |
| vibrant | (describe what makes it active, or cut) |
| thriving | growing, active (or cite a number) |
| despite challenges… continues to thrive | (name the challenge and the response, or cut) |
| showcasing | showing, demonstrating (or cut the clause) |
| deep dive / dive into | look at, examine, explore |
| unpack / unpacking | explain, break down, walk through |
| bustling | busy, active (or cite what makes it busy) |
| intricate / intricacies | complex, detailed (or name the specific complexity) |
| complexities | (name the actual complexities, or use "problems" / "details") |
| ever-evolving | changing, growing (or describe how) |
| enduring | lasting, long-running (or cite how long) |
| daunting | hard, difficult, challenging |
| holistic / holistically | complete, full, whole (or describe what's included) |
| actionable | practical, useful, concrete |
| impactful | effective, significant (or describe the impact) |
| learnings | lessons, findings, takeaways |
| thought leader / thought leadership | expert, authority (or describe their actual contribution) |
| best practices | what works, proven methods, standard approach |
| at its core | (cut — just state the thing) |
| synergy / synergies | (describe the actual combined effect) |
| interplay | relationship, connection, interaction |
| in order to | to |
| due to the fact that | because |
| serves as | is |
| features (verb) | has, includes |
| boasts | has |
| presents (inflated) | is, shows, gives |
| commence | start, begin |
| ascertain | find out, determine, learn |
| endeavor | effort, attempt, try |
| keen (as intensifier) | interested, eager, enthusiastic (or cut — just state the interest) |
| symphony (metaphor) | (describe the actual coordination or combination) |
| embrace (metaphor) | adopt, accept, use, switch to |
These words are legitimate on their own. When two or more show up together, the paragraph likely needs a rewrite.
| Replace | With |
|---|---|
| harness | use, take advantage of |
| navigate / navigating | work through, handle, deal with |
| foster | encourage, support, build |
| elevate | improve, raise, strengthen |
| unleash | release, enable, unlock |
| streamline | simplify, speed up |
| empower | enable, let, allow |
| bolster | support, strengthen, back up |
| spearhead | lead, drive, run |
| resonate / resonates with | connect with, appeal to, matter to |
| revolutionize | change, transform, reshape (or describe what changed) |
| facilitate / facilitates | enable, help, allow, run |
| underpin | support, form the basis of |
| nuanced | specific, subtle, detailed (or name the actual nuance) |
| crucial | important, key, necessary |
| multifaceted | (describe the actual facets, or cut) |
| ecosystem (metaphor) | system, community, network, market |
| myriad | many, numerous (or give a number) |
| plethora | many, a lot of (or give a number) |
| encompass | include, cover, span |
| catalyze | start, trigger, accelerate |
| reimagine | rethink, redesign, rebuild |
| galvanize | motivate, rally, push |
| augment | add to, expand, supplement |
| cultivate | build, develop, grow |
| illuminate | clarify, explain, show |
| elucidate | explain, clarify, spell out |
| juxtapose | compare, contrast, set side by side |
| paradigm-shifting | (describe what actually shifted) |
| transformative / transformation | (describe what changed and how) |
| cornerstone | foundation, basis, key part |
| paramount | most important, top priority |
| poised (to) | ready, set, about to |
| burgeoning | growing, emerging (or cite a number) |
| nascent | new, early-stage, emerging |
| quintessential | typical, classic, defining |
| overarching | main, central, broad |
| underpinning / underpinnings | basis, foundation, what supports |
These are normal words. Only flag them when the text is saturated with them — a sign that AI filled space with vague praise instead of specifics.
| Word | What to do |
|---|---|
| significant / significantly | Replace some with specifics: numbers, comparisons, examples |
| innovative / innovation | Describe what's actually new |
| effective / effectively | Say how or cite a metric |
| dynamic / dynamics | Name the actual forces or changes |
| scalable / scalability | Describe what scales and to what |
| compelling | Say why it compels |
| unprecedented | Name the precedent it breaks (or cut) |
| exceptional / exceptionally | Cite what makes it an exception |
| remarkable / remarkably | Say what's worth remarking on |
| sophisticated | Describe the sophistication |
| instrumental | Say what role it played |
| world-class / state-of-the-art / best-in-class | Cite a benchmark or comparison |
These slot-fill constructions signal that a sentence was generated, not written. If a phrase has a blank where a noun or adjective could go and still sound the same, it's too generic.
These aren't individual word or phrase problems — they're patterns in how the text flows as a whole. AI text is metronomic; human text has varied rhythm.
Structure is the #1 detection signal. AI detection tools (including Pangram, which trains a classifier on 28M human documents) weight structural regularity higher than vocabulary. Consistent sentence construction, uniform pacing, and symmetrical phrasing patterns are harder to mask than swapping out a few flagged words. If you fix every word on the Tier 1 list but leave the rhythm untouched, the text still reads as AI-generated.
If the text has 5+ flagged vocabulary hits across multiple categories, 3+ distinct pattern categories triggered, and uniform sentence/paragraph length, patching individual phrases won't fix it — the structure itself is AI-generated. Advise a full rewrite: state the core point in one sentence, then rebuild from there.
Not all AI-isms are equal. When doing a quick pass or triaging a large document, prioritize by tier:
Use P0+P1 for quick passes. Full audit covers all three tiers.
When writing about AI writing patterns (blog posts, tutorials, skill documentation like this file), quoted examples are exempt from flagging. Text inside quotation marks, code blocks, or explicitly marked as illustrative ("for example, AI might write...") should not be rewritten. Only flag patterns that appear in the author's own prose, not in cited examples of bad writing.
Pass an optional context hint to adjust rule strictness. If no context is specified, auto-detect from content cues (short + hashtags = social, code blocks = technical, salutation = email, default = blog).
linkedin � Short-form social. Punchy fragments, visual formatting matter.
blog � Default. Standard long-form prose. All rules apply at full strength.
technical-blog � Long-form with code, architecture, APIs. Technical terms get a pass.
investor-email � High-trust audience. Tighten everything; promotional language is the biggest risk.
docs � Documentation, READMEs, guides. Clarity over voice.
casual � Slack messages, internal notes, quick replies. Only catch the worst offenders.
Rules not listed in the table apply at full strength across all profiles.
| Rule | blog | technical-blog | investor-email | docs | casual | |
|---|---|---|---|---|---|---|
| Em dashes | relaxed (2/post OK) | strict | strict | strict | relaxed | skip |
| Bold overuse | relaxed (bold hooks OK) | strict | strict | strict | relaxed | skip |
| Emoji in headers | relaxed (1-2 end-of-line OK) | strict | strict | strict | skip | skip |
| Excessive bullets | skip (lists work on LinkedIn) | strict | relaxed (technical lists OK) | strict | skip (lists are docs) | skip |
| Hedging | strict | strict | relaxed ("may" is accurate in technical) | strict | relaxed | skip |
| Word table (full list) | strict | strict | partial (see below) | strict | relaxed | P0 only |
| Promotional language | relaxed (some sell is expected) | strict | strict | extra strict | strict | skip |
| Significance inflation | strict | strict | strict | extra strict | relaxed | skip |
| Copula avoidance | skip | strict | relaxed | strict | skip | skip |
| Uniform paragraph length | skip (short-form) | strict | strict | strict | relaxed | skip |
| Numbered list inflation | relaxed | strict | relaxed | strict | skip | skip |
| Rhetorical questions | relaxed (1 as hook OK) | strict | strict | strict | strict | skip |
| Transition phrases | skip (short-form) | strict | strict | strict | relaxed | skip |
| Generic conclusions | skip | strict | strict | extra strict | skip | skip |
Technical-blog word table exceptions: These terms have legitimate technical meaning and should not be flagged in technical context: robust, comprehensive, seamless, ecosystem, leverage (when discussing actual platform leverage/APIs), facilitate, underpin, streamline. Still flag: delve, tapestry, beacon, embark, testament to, game-changer, harness.
"Extra strict" means: flag even borderline instances. In investor emails, a single "thriving ecosystem" can undermine the whole message.
"Skip" means: don't audit this category for this profile. The rule doesn't apply or isn't worth the edit.
When no context is specified, infer from these signals:
| Signal | Inferred context |
|---|---|
| Under 300 words + hashtags or mentions | linkedin |
| Code blocks, API references, or technical architecture | technical-blog |
| Salutation ("Hi [name]", "Dear") + investor/fundraising language | investor-email |
| Step-by-step instructions, parameter docs, README structure | docs |
| No strong signals | blog (safest default � all rules apply) |
If auto-detection feels wrong, say which profile you're using and why. The user can override.
Return your response in four sections:
1. Issues found A bulleted list of every AI-ism identified, with the offending text quoted.
2. Rewritten version The full rewritten content. Preserve the original structure, intent, and all specific technical details. Only change what the guidelines require.
3. What changed A brief summary of the major edits made. Not every word, just the meaningful changes.
4. Second-pass audit Re-read the rewritten version from section 2. Identify any remaining AI tells that survived the first pass — recycled transitions, lingering inflation, copula avoidance, filler phrases, or anything else from the categories above. Fix them, return the corrected text inline, and note what changed in this pass. If the rewrite is clean, say so.
Return your response in two sections:
1. Issues found A bulleted list of every AI-ism identified, with the offending text quoted. Group by severity (P0, P1, P2).
2. Assessment For each flag, note whether it's a clear problem or a judgment call. Some AI-associated patterns are effective writing techniques — uniform paragraph length is a problem, but a well-placed "however" isn't. Call out which flags the writer should definitely fix vs. which ones are worth a second look but might be fine in context. If the text is clean, say so.
The goal is writing that sounds like a person wrote it. Direct. Specific. The writing should demonstrate confidence, not assert it.
Five principles for human-sounding rewrites:
If the original writing is already strong, say so and make only the necessary cuts. Don't over-edit for the sake of it.
The replacement table provides defaults, not mandates. If a flagged word is clearly the right choice in context, preserve it.
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/47-conorbronsdon-avoid-ai-writing of brycewang-stanford/Auto-Empirical-Research-Skills.
Open the folder on GitHubat commit 9fa87d8
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 brycewang-stanford/Auto-Empirical-Research-Skills, which our catalogue first saw on October 7, 2026.
Avoid AI Writing 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 |
|---|---|---|---|---|---|---|
| Avoid AI Writing this skillbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | 1 repos | ~8.4k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 172 | 37 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT | |
| Stop SlopXe/site | 732 | 8 repos | ~423 | Automated safety check: Pass | MIT |
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Xe/site
Remove AI writing patterns from prose. An agent skill from Xe/site.
op7418/Humanizer-zh
Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when auditing a finished or near-finished AER, AER:Insights, or AEJ manuscript for internal consistency: headline numbers across abstract, introduction, results, and tables…
brycewang-stanford/Auto-Empirical-Research-Skills
English LaTeX academic paper assistant for existing .tex projects.
brycewang-stanford/Auto-Empirical-Research-Skills
Opinionated Bayesian modeling workflow with PyMC and ArviZ. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when the user asks to "generate daily paper", "search arXiv for EEG papers", "find EEG decoding papers", "review brain-computer interface papers", or wants to create paper…
brycewang-stanford/Auto-Empirical-Research-Skills
Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when a research task needs reproducible Kaggle discovery, metadata inspection, bounded public-data downloads, competition or kernel discovery, model discovery, or an…
Categories
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Avoid AI Writing is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Audit and rewrite content to remove AI writing patterns ("AI-isms").
Avoid AI Writing fits situations like: asked to remove AI-isms; clean up AI writing; edit writing for AI patterns; audit writing for AI tells.
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a claude-code`. Or copy the skill folder (skills/47-conorbronsdon-avoid-ai-writing in brycewang-stanford/Auto-Empirical-Research-Skills) into .claude/skills/avoid-ai-writing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a codex`. Or copy the skill folder (skills/47-conorbronsdon-avoid-ai-writing in brycewang-stanford/Auto-Empirical-Research-Skills) into .agents/skills/avoid-ai-writing 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/avoid-ai-writing, .gemini/skills/avoid-ai-writing, .github/skills/avoid-ai-writing and .opencode/skills/avoid-ai-writing in your project.
SKILL.md names no scripts, command-line tools or credentials: Avoid AI Writing is instructions for the agent only. Compatibility (from SKILL.md): Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required..
SKILL.md names 1 domain. As links in the text: github.com. 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.
Avoid AI Writing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 8.4k tokens (SKILL.md is roughly 34k 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 Avoid AI Writing: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Auto-Empirical-Research-Skills, which has 4,542 GitHub stars. The repository holds 383 skills in this directory. The repository was last updated on October 5, 2026.
Source: brycewang-stanford/Auto-Empirical-Research-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.