agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/file/SKILL.md

file

Skill2 starsChanged 25 days agoMITView on GitHub

Use when a fact-checked file under research\verified\ is ready to become or update a verified note. Runs the librarian in a fresh context; files VERIFIED rows only, updates index, registry and curriculum, and runs check_note.py.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    After /verify has written a verified file.

    line 12
  2. Distinctive:

    Read the verified file. Separate VERIFIED and corrected-PARTIAL rows (they go to Facts) from CONTRADICTED and UNVERIFIABLE rows (they go to …

    line 15
  3. Very specific:

    Write or update the note per templates\note.md with Applies to:, Verified: <today>, conditions on every number, a public source URL on …

    line 17
  4. Very specific:

    Run .venv\Scripts\python.exe tools\check_note.py <note path> until PASS.

    line 18
  5. Very specific:

    Update the category index.md, add new URLs to sources\registry.md, tick CURRICULUM.md only where the note covers the line.

    line 19

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

Overview

File: $ARGUMENTS

When to use

After /verify has written a verified file. Never on an inbox file.

Steps

  1. Read the verified file. Separate VERIFIED and corrected-PARTIAL rows (they go to Facts) from CONTRADICTED and UNVERIFIABLE rows (they go to Not verified / open questions).
  2. Pick the knowledge\<NN-category>\ folder that fits; Grep it for an existing note on the topic and merge into it if found.
  3. Write or update the note per templates\note.md with Applies to:, Verified: <today>, conditions on every number, a public source URL on every fact.
  4. Run .venv\Scripts\python.exe tools\check_note.py <note path> until PASS.
  5. Update the category index.md, add new URLs to sources\registry.md, tick CURRICULUM.md only where the note covers the line.
  6. Return: note path, rows filed, rows deferred, files touched, check_note result.

Common rationalizations

RationalizationReality
"New note is cleaner than merging."Grep first. One topic, one file.
"The curriculum line is close enough."Tick only what the note verifies.

Red flags

  • check_note.py not run.
  • A Facts bullet without a URL.

Verification

  • check_note.py PASS.
  • index, registry, curriculum updated where true.
  • Paths returned.

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.