agentleFS
ehnruizehnruiz/claude-skills/skills/no-ai-attribution/SKILL.md

no-ai-attribution

Skill3 starsChanged 31 days agoMITView on GitHub

Keep AI-assistant credit lines out of anything published on the user's behalf. Use before writing a commit message, pull request, issue, comment, review reply, ticket, wiki page or chat message.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit trailers that name an assistant or its vendor, for example Co-Authored-By: <assistant> <noreply@…>.

    line 14
  2. Distinctive:

    Before any tool call that creates or edits published text, re-read the text and delete any attribution line.

    line 21
  3. Distinctive:

    Check the result after posting.

    line 22
  4. Distinctive:

    If something already posted carries a footer and you cannot edit it, tell the user exactly where it is.

    line 23

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

No AI attribution

The user signs what they publish. Text written for them reads as theirs, with no line crediting an AI assistant or tool.

Leave out

  • Footers such as "Generated with …", "Written with …" or a robot emoji followed by a tool name, with or without a --- rule above them.
  • Links to an assistant session.
  • Commit trailers that name an assistant or its vendor, for example Co-Authored-By: <assistant> <noreply@…>. GitHub shows every Co-Authored-By trailer as a co-author on the commit, and squash merges carry it into the PR.
  • An assistant listed as an author, co-author, reviewer or watcher anywhere.

Co-author trailers for real people the user paired with are fine. Add them when the user asks.

How to apply it

  1. Before any tool call that creates or edits published text, re-read the text and delete any attribution line. A commit message ends with its own last line of content; a PR description ends with the last section of the repository's template.
  2. Check the result after posting. Some tools append a footer on their own; edit it out.
  3. If something already posted carries a footer and you cannot edit it, tell the user exactly where it is.

Download now (ZIP)

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.