agentleFS
anurag-rivoraanurag-rivora/product-brain-starter/.claude/skills/brain-health/SKILL.md

brain-health

Skill1 starsChanged 4 days agoMITView on GitHub

Check the health of the product brain and print a short report. Use for the weekly or monthly review, or when someone says "how healthy is the brain" or "run brain health".

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. day-ai/gtm-brain★ 9same name
    2. t0ddharris/compound-marketing★ 1same name
    3. herreraspaintingba-hub/second-brain-starter-kit★ 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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Run python scripts/brain_health.py from the repo root.

    line 10
  2. Distinctive:

    Do not fix anything. Do not approve, move or delete entries.

    line 19
  3. Distinctive:

    No confirmer or owner: ask the area owner to confirm or stop the entry.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 3 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.

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

Brain health

Steps

  1. Run python scripts/brain_health.py from the repo root. If Python is not available, do the checks by hand from the front matter.
  2. The six checks:
    1. Open questions and how long each has waited.
    2. Entries with no confirmer or owner.
    3. Approved entries past review_by, or confirmed more than 90 days ago.
    4. Replaced or stopped entries still cited elsewhere in the repo.
    5. Inbox proposals older than 14 days.
    6. Entries scoped to "all".
  3. Print a short report: one line per check with the count, then the IDs behind any non-zero count and one suggested action each.
  4. Do not fix anything. Do not approve, move or delete entries. A person decides.

Suggested actions

  • Open questions: assign an owner and a date.
  • No confirmer or owner: ask the area owner to confirm or stop the entry.
  • Past review: the owner re-confirms, replaces or stops it.
  • Cited but replaced or stopped: update the citing file to the current entry.
  • Old proposals: approve, change or delete.
  • Scoped to "all": narrow the scope, unless it truly applies everywhere.

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.