agentleFS
BrightfolkStudioBrightfolkStudio/claude-skills/skills/ai-tells/SKILL.md

ai-tells

Skill0 starsChanged 35 days agoNo licenceView on GitHub

Avoid common AI writing tells, patterns, and linguistic tics in any written output. Use this skill whenever writing copy, content, marketing text, social media posts, website copy, blog posts, LinkedIn posts, emails, taglines, brand messaging, case studies, proposals, or any text intended for others to read. Also trigger when the user says \"HUMAN VOICE\", asks for \"human-sounding\" writing, mentions AI tells, or asks you to write anything that should not sound like it was written by an AI. Also use it to review an existing draft for AI tells, e.g. when asked to \"review for AI tells\", \"does this read AI\" or \"make this less AI\". This skill should be active for ALL copywriting and content creation tasks, even if the user doesn't explicitly mention AI tells. If in doubt about whether to apply this skill, apply it. The only exception is internal working notes, code, or technical documentation where these rules don't apply.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. JetBrains/youtrackdb★ 443same name
    2. kdgbalmer/ai-tells★ 35same name
    3. sublimecoder/aios★ 2same name
    4. SEO-Optimizers/ai-tells★ 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

30 rules. 0 are common, 30 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 30

    Distinctive

    This author's own choices. Worth a look.

  • 0

    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 4 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.