agentleFS
erikunhaerikunha/vault-of-loci/.agents/skills/run-checks/SKILL.md

run-checks

Skill0 starsChanged 5 days agoMITView on GitHub

Run every check of this vault (formatting, links, study layer, names, flashcards, skills, alt text, reading index, tests). Use after editing and before committing.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run every check with one command:

    line 6

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

Run every check with one command:

python3 -I 90_System/Scripts/run_checks.py

It runs format_notes.py --check, every validation/check_*.py and every validation/test_*.py, and prints passed or FAILED for each, with the last lines of a failure.

For a report of notes that need attention (orphans, unused or unverified references, concepts in no track, old open questions and clippings), run python3 -I 90_System/Scripts/kb_lint.py. It never edits a note and is not a check.

How to fix the usual failures:

  • Formatting: python3 -I 90_System/Scripts/format_notes.py (without --check).
  • Names: python3 90_System/Scripts/normalize_names.py --write.
  • Reading index: python3 -I 90_System/Scripts/build_index.py.
  • Flashcards: every question::answer card and cloze needs a source link; no question may repeat.
  • Anything else: read the failing check's own message; 90_System/Specs/Tools.md says what each check guards.

Report each check as passed, failed or not run. Not run is never passed.

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.