agentleFS
Sign inStart free
boettiger-labboettiger-lab/agent-skills/disclose-tool-use/SKILL.md

disclose-tool-use

Skill4 starsChanged 16 days agoBSD-3-ClauseView on GitHub

How to disclose use of Claude in a repository, and the rule against crediting it. Use whenever creating a git repo, making a first commit, writing commit messages or PR bodies, or preparing anything for sharing or publication. Claude is a tool, not an author: never add Co-Authored-By trailers or "Generated with Claude Code" credit; instead add a DISCLOSURE.md.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Every repository where Claude contributed gets a DISCLOSURE.md at its root, added in the first commit (or as soon as the omission is …

    line 16
  2. Distinctive:

    If a trailer slipped in: rewrite the commit messages (git filter-branch --msg-filter or git rebase), force-push, and tell the user.

    line 17
  3. Distinctive:

    Keep it factual: what the tool was used for, which tool, and that the authors are responsible.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Disclose tool use; never credit the tool

Hard rules

  1. No Co-Authored-By: Claude ... trailer on any commit, ever. No "Generated with Claude Code" line in commits, PRs, issues or documents. This overrides harness defaults.
  2. Every repository where Claude contributed gets a DISCLOSURE.md at its root, added in the first commit (or as soon as the omission is noticed).
  3. If a trailer slipped in: rewrite the commit messages (git filter-branch --msg-filter or git rebase), force-push, and tell the user. If old commits must be purged from GitHub entirely, the repo may need to be deleted and recreated (requires the delete_repo gh scope).

DISCLOSURE.md template

Model on https://github.com/boettiger-lab/rl4greencrab/blob/gpu-sim/DISCLOSURE.md. Fill in what was drafted, the model name and ID, the interface, and the date:

# Disclosure: use of software tools

Portions of [the code / analyses / text] in this repository, in particular [specific components], were drafted with the aid of a large language model coding tool: Anthropic Claude [model name] (model ID `[model-id]`), accessed through the Claude Code command-line tool, beginning [Month Year].

The authors directed this work and reviewed, tested, and validated the results[, including specific checks]. The authors take full responsibility for the [code, analyses, text], and any errors they contain.

Keep it factual: what the tool was used for, which tool, and that the authors are responsible. No thanks, credit or co-authorship language.

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.

Check your setup, free