agentleFS
francoisdpfrancoisdp/skills/anti-ai-writing/SKILL.md

anti-ai-writing

Skill2 starsChanged 23 days agoNo licenceView on GitHub

Mandatory writing quality rules that eliminate AI-writing patterns from ALL generated output. This skill applies passively to every response (prose, emails, code comments, creative writing) shaping generation from the start. It also provides an active review pass when invoked explicitly. ALWAYS trigger this skill. It runs silently on every output. Explicitly trigger when user says "review for AI writing", "clean up AI patterns", "audit this draft", "make this sound human", "anti-AI check", or "does this sound like AI". Also trigger for any writing, editing, or document creation task. This skill is foundational and runs alongside all other skills. When the task formats or restructures material the user supplied, Rules 34 and 40 govern content fidelity and the `fix-language` skill must be invoked first.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

51 rules. 0 are common, 44 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 44

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.