agentleFS
edrethardoedrethardo/werkbank-board/.claude/skills/finding-knowledge/SKILL.md

finding-knowledge

Skill0 starsChanged 3 months agoMITView on GitHub

Use before starting any task, investigation, or debugging session, and before answering "how does X work?" — search the project's journal and docs before re-deriving anything.

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:

    Follow tags: pick the relevant tag in docs/TAGS.md, then search tags:.*<tag> across docs/ with the Grep tool (files-with-matches mode).

    line 16
  2. Distinctive:

    Only then grep or read the codebase.

    line 18
  3. Distinctive:

    Never re-investigate what a past entry already answers — cite the entry instead.

    line 22
  4. Distinctive:

    If a found entry is outdated (the code moved on), update or mark it, and journal the correction.

    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

Finding Knowledge

Five minutes of index reading beats an hour of re-derivation. The project's memory lives in two indexes; consult them before touching code.

Search order

  1. docs/journal/INDEX.md — has a past session touched this? Open the matching entries.
  2. docs/INDEX.md — is it documented? Open the matching docs.
  3. Follow tags: pick the relevant tag in docs/TAGS.md, then search tags:.*<tag> across docs/ with the Grep tool (files-with-matches mode).
  4. Only then grep or read the codebase.

Rules

  • Never re-investigate what a past entry already answers — cite the entry instead.
  • If a found entry is outdated (the code moved on), update or mark it, and journal the correction. Stale memory is worse than no memory.
  • Found nothing? Note it in one line ("no prior work on X in journal/docs") so the session's journal entry records that the search happened — that negative result saves the next session the same search.

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.