anti-ai-tells
Skill1 starsChanged 3 months agoMITView on GitHub
Review AI writing signals and humanize copy in English and Brazilian Portuguese. Use for AI writing detector checks, ChatGPT detection concerns, human-sounding rewrites, cliche removal, punctuation review, and pre-publication copy checks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Scratchydisk/claude-skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Scratchydisk/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
No mixed unicode quotation marks (", ", ', ') with straight quotes in the same text.
- Distinctive: line 43
No unsolicited bullet lists, bold emphasis or headers inside short-form copy.
- Distinctive: line 48
No rhetorical questions answered in the next sentence.
- Distinctive: line 49
No parenthetical aposition framed by two em-dashes (consequence of the punctuation rule anyway).
- Distinctive: line 57
No three consecutive sentences with similar length
- Very specific: line 64
Hard ban: Do not use provenance in ordinary project, product, or open-source copy.
- Distinctive: line 83
Prefer this sequence when reviewing copy:
- Very specific: line 107
Final pass: the em-dash sweep: Search for the literal — character one last time.
- Distinctive: line 111
Instead of "X is a visionary who is passionate about transforming..." write:
- Distinctive: line 114
Instead of "In today's fast-paced world, companies navigate unprecedented complexity..." write:
- Distinctive: line 117
Instead of "It's not just about X, it's about Y" write:
- Distinctive: line 120
Instead of "X leverages cutting-edge technology to deliver seamless experiences" write:
- Distinctive: line 125
When instructing an LLM to write copy through this skill, include in the system prompt:
- Very specific: line 137
Read reference.md in this same skill directory for:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What I do
I help strip "AI fingerprints" from copy that is meant to read as human-written. I carry a curated, evidence-backed catalog of the stylistic, lexical, structural and punctuation patterns that flag a text as generated by ChatGPT, Claude or Gemini in 2024 to 2026, for both English and Brazilian Portuguese.
I ship two interchangeable ways to invoke the detection engine:
- MCP tools (preferred from inside OpenCode):
anti-ai-tells_lint_text,anti-ai-tells_lint_file,anti-ai-tells_describe_rules. Registered as theanti-ai-tellsMCP server. No shell overhead. - CLI binary:
$SKILL_DIR/bin/ai-tells-lint. Useful for CI pipelines, shell scripts, or when the MCP is disabled.
Both share the same detection engine, so results are identical.
When to use me
Load this skill whenever you are writing, reviewing or editing any piece of copy that needs to pass as written by a human. That includes:
- Speaker intros, bios, about-me sections, LinkedIn posts
- Press releases, op-eds, blog posts, long-form essays
- Marketing copy, landing pages, product descriptions
- Any final output that will be published publicly and will embarrass the author if detected as AI-written
Also load me if a user explicitly says "make it not sound like AI", "remove the ChatGPT smell", or asks about em-dash overuse, cliche phrasing, or "tells".
Core rules (hard constraints)
These are zero-tolerance. Any violation must be rewritten before shipping.
Punctuation
- No em-dash (
—) anywhere. This is the single most cited AI tell, documented on Reddit r/ChatGPT, HackerNews and even OpenAI's own forum (2024 to 2026). Use period, comma, colon, semicolon or parentheses instead. - No mixed unicode quotation marks (
",",',') with straight quotes in the same text. Pick one and stick with it. - No unsolicited bullet lists, bold emphasis or headers inside short-form copy.
Structure
- Maximum ONE tricolon (rule of three, e.g. "fast, cheap and reliable") per whole text.
- No "not just X but Y" antithesis patterns.
- No rhetorical questions answered in the next sentence.
- No parenthetical aposition framed by two em-dashes (consequence of the punctuation rule anyway).
- Paragraphs should NOT share the same opening syntax or the same rhythm. Vary sentence length deliberately.
Burstiness target
Human text has high burstiness: a mix of short and long sentences. Every published copy should contain:
- At least one sentence below 10 words
- At least one sentence between 12 and 18 words
- At least one sentence above 22 words
- No three consecutive sentences with similar length
Forbidden vocabulary
English (a.k.a. "ChatGPT buzzword bingo")
delve, delve into, tapestry, navigate (the landscape/the complexities), foster, underscore, nuanced, pivotal, elevate, realm (in the realm of), bolster, grapple, myriad, testament (stands as a testament), comprehensive, seamless, embark (embark on a journey), crucial, meticulous, robust, multifaceted, holistic, unprecedented, ever-evolving, cutting-edge, game-changing, transformative, leverage (as verb), resonate, provenance.
Hard ban: Do not use provenance in ordinary project, product, or open-source copy. Say "origin", "source", "history", or the specific fact instead. Keep the word only when discussing a formal metadata, legal, archival, or security standard that actually uses it.
Portuguese (Brazilian, ChatGPT pt-BR tells)
Openings to cut: "no cenário atual", "em um mundo cada vez mais", "nos dias de hoje", "vivemos em uma época", "nessa era digital", "atualmente a tecnologia", "a IA tem revolucionado".
Mechanical connectors: "vale ressaltar", "vale destacar", "vale mencionar", "nesse contexto", "nesse sentido", "é fundamental", "é importante mencionar", "é importante destacar", "dessa forma" (as sentence opener), "desse modo".
Typical antithesis: "não apenas X, mas também Y", "não se trata apenas de X, mas de Y", "mais do que X, é Y".
Cliche closers: "em conclusão", "em suma", "em última análise", "portanto" (as paragraph opener).
Generic AI-flavored adjectives: robusto, multifacetado, inovador, transformador, promissor, desafiador, fascinante, exponencial, revolucionário, holístico.
LinkedIn-motivational vocab: visionário, disruptor, disruptivo, disrupção, mente brilhante, apaixonado por, referência no mercado, fera, monstro, mito, transformacional, mindset, gamechanger, líder nato, inquieto.
Empty-sentence patterns: "com vasta experiência", "com sólida trajetória", "com ampla experiência", "reconhecido internacionalmente" (without naming what for), "um dos maiores nomes", "referência em", slogan-like phrases like "onde erro custa caro" or "transformar X em Y".
How to use me on a draft
Prefer this sequence when reviewing copy:
Run the linter first. Two interchangeable options:
Via MCP (from inside OpenCode, no shell):
anti-ai-tells_lint_file(path="/abs/path/to/draft.md") anti-ai-tells_lint_text(text="<inline snippet>") anti-ai-tells_describe_rules()Via CLI (any shell, any pipeline):
"$SKILL_DIR/bin/ai-tells-lint" <path-to-draft.md>Both report HARD violations (em-dash, forbidden phrases) and SOFT warnings (suspicious quotes, low burstiness). The CLI supports
--strict(exit 1 on HARD hits) and--format jsonfor pipelines. The MCP version also returns averdictfield (ships_clean/needs_cleanup_pass/rewrite_recommended) and a one-linesummary.- Read the draft out loud once. Any sentence that sounds like a LinkedIn motivational post, a TED-talk opening or a press release boilerplate gets rewritten.
- Rewrite with concrete verbs. Replace abstract adjectives with factual verbs that can be proven: built, led, architected, structured, operated, received, founded, took, shipped, deployed.
- Check paragraph rhythm. Open three paragraphs with different syntactic patterns. Vary sentence length. Avoid the "short, medium, long, short, medium, long" loop.
- Final pass: the em-dash sweep. Search for the literal
—character one last time. If any survive, rewrite until zero.
Anti-tells writing patterns (positive guidance)
Instead of "X is a visionary who is passionate about transforming..." write:
- "X built [concrete thing] in [concrete period]. After [concrete event], X now [concrete action]."
Instead of "In today's fast-paced world, companies navigate unprecedented complexity..." write:
- "[Specific industry] changed in [specific year]. Most companies [specific observable behavior]."
Instead of "It's not just about X, it's about Y" write:
- "X matters because Y."
Instead of "X leverages cutting-edge technology to deliver seamless experiences" write:
- "X uses [specific tech stack] to [specific measurable outcome]."
Negative-constraint prompting pattern
When instructing an LLM to write copy through this skill, include in the system prompt:
- The full forbidden-word list above (copy-paste, do not summarize).
- The explicit rule: "Do not use the em-dash character
—anywhere in your output. Zero occurrences. Use periods, commas, colons, parentheses or semicolons instead." - The burstiness rule: "Vary sentence length. At least one sentence below 10 words, one between 12 and 18, one above 22."
- A self-review step: "Before returning, verify your output contains zero em-dashes and no forbidden phrases. If any appear, rewrite until clean."
- Concrete anti-examples (bad -> good) from the sibling
reference.mdfile in this skill's directory.
Low temperature does NOT fix tells. Explicit negative constraints do.
Reference documents
Read reference.md in this same skill directory for:
- The full evidence trail with citations (papers, forum threads, studies)
- Extended anti-example gallery (bad vs. good rewrites, both EN and pt-BR)
- Tool comparison: GPTZero, Binoculars, Originality.ai, Copyleaks
- Vale linter integration blueprint
Directory layout
<skill-directory>/
├── SKILL.md (this file; skill entrypoint)
├── reference.md (evidence base with citations)
├── start-mcp.sh (MCP server wrapper; entry point for OpenCode)
├── mcp_server.py (FastMCP server exposing lint_text, lint_file, describe_rules)
└── bin/
├── ai-tells-lint (shell wrapper, marked executable)
└── ai-tells-lint.py (Python detection engine; shared with MCP server)The MCP server is registered in the user's OpenCode configuration under mcp.anti-ai-tells when enabled. Restart OpenCode after installing or updating.
Related agent
If the task is specifically to review a draft for AI tells (not to write from scratch), delegate to the ai-tells-reviewer subagent via the Task tool. That agent is specialized and read-only: it runs the linter, reads the draft, and returns a structured critique with concrete rewrite suggestions.
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
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.

