Guide · Agent skill
How to use the Avoid AI Writing agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The avoid-ai-writing skill is a set of instructions and reference files for an AI agent that audits prose for patterns that make text read as machine-generated, then helps fix them. It is useful for developers polishing READMEs, changelogs, release notes and PR descriptions, and for writers who want drafts to sound less generic. After this guide you will know what the skill does, how to install it, how to ask for each of its three modes, and what limits to keep in mind.
Quick start
- 1Download the ZIP. Get the avoid-ai-writing ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Pick a mode. Ask in plain words for detect, rewrite or edit, or pass --mode explicitly.
- 5Set a context. Name a profile such as docs, blog or linkedin, or let the skill infer it.
- 6Review the output. Check each flag and each rewrite against the facts you know.
What agent skills are and what this one does
An agent skill is a folder of instructions and reference files that an AI agent can load when a task matches the skill's description. This skill is named avoid-ai-writing and its job is to review a piece of writing, point out phrases and structures that read as machine-generated, and suggest or make fixes without removing the author's voice.
It works from reference files that grade how severe each pattern is, a tiered vocabulary list, and context profiles such as LinkedIn, docs, or investor email that change how strictly the rules apply.
- Detect mode: lists the flags only, grouped by severity, and separates clear problems from judgment calls.
- Rewrite mode (the default): returns a cleaned-up version with a summary of what changed, then re-checks its own rewrite.
- Edit mode: changes a prose file in place with minimal, targeted edits, then re-opens the file to confirm the flagged patterns are gone.
Install the avoid-ai-writing skill
Download the ZIP for this skill from our page. Then choose one of two routes depending on how you use your agent.
For a personal setup, unzip the download into ~/.claude/skills/. To make it available only inside one project, unzip it into that project's .claude/skills/ folder instead.
If you use the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills rather than unzipping it by hand.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Trigger the skill with natural requests
You do not need a special command. The skill's description lists the kinds of requests that should activate it, such as asking to remove AI-isms, clean up AI writing, edit a draft for AI tells, or audit a README, changelog, release note, PR description, or blog post for machine-sounding prose.
To pick a mode in plain language, use words the skill recognises. For detect mode, words like "detect", "flag only", "audit only", "scan" or "what AI patterns are in this" work. Explicit options are also accepted: --mode rewrite|detect|edit, --voice, --context, --file PATH, and --iterate N for rewrite mode, where N is the total pass count including the built-in corrective pass, capped at 2.
- "Scan this README for AI patterns, flag only."
- "Clean up the AI writing in this release note."
- "Edit docs/CHANGELOG.md in place to remove AI-isms."
- "Make this blog draft sound less like AI, context blog."
Choose a context profile
A context profile sets how strict the skill is for a given audience. You can name one or let the skill infer it from the text. The available profiles are linkedin, blog (the default, with every rule at full strength), technical-blog, investor-email, docs, and casual.
Docs and technical writing get a lighter touch: the docs profile favours clarity over voice, and technical-blog lets technical terms pass. The skill says which profile it used, so check that it matches your audience.
--context docsRead the results carefully
Every flag is a writing-quality signal, not proof of how the text was produced. The skill's own documentation warns that AI detectors are unreliable, with high false-positive rates in some scenarios, so flags should not be used to decide academic integrity, hiring, or attribution questions.
The skill also forbids inventing personality, facts, or numbers during a rewrite. If a fix would require a new claim, it flags the gap and leaves it for you to fill.
- Check every rewrite against your own knowledge of the facts.
- Treat wordiness fixes as style suggestions, not evidence about authorship.
- Quoted, attributed, or third-party text is protected: tells inside it are reported but not rewritten.
What the skill needs and its safety notes
The skill lists no requirements. It does not run scripts and does not use the network, according to its listing. It is licensed under MIT.
Edit mode refuses source code, configuration files, and generated data. Point it at prose files such as Markdown documents.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
- Licence: MIT
What people use it for
- Polishing a README or changelog before publishing a release.
- Cleaning up a PR description so it states what changed without filler.
- Scanning a blog draft for generic phrasing and tightening it.
- Checking your own English prose so your voice comes through clearly.
- Auditing a document in detect mode when you want to decide the fixes yourself.
Frequently asked questions
How do I install the avoid-ai-writing skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
Is the avoid-ai-writing skill free?
The skill is listed under the MIT licence. Check the licence file in the source repository for the exact terms before reusing it.
What does the skill require?
Its listing shows no requirements, does not run scripts, and does not use the network.
Can this tool tell whether text was written by AI?
No. The skill states that its flags are writing-quality signals only, and that AI detectors are unreliable. Do not use its output for academic-integrity, hiring, or attribution decisions.
Will it change my source code or config files?
No. Edit mode refuses source code, configuration, and generated data files, and works on prose files only.
Does the rewrite add new facts or a different personality?
The skill forbids adding invented personality, facts, or numbers during a rewrite. Where a fix would need new information, it flags the gap and leaves it in place.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers preparing READMEs, changelogs, release notes and PR descriptions, and writers who want drafts to read less generically. It is a poor fit for any decision about whether someone used AI, and for quoted or third-party text you do not own, where detect mode is the safer choice.
Download the skill