agentleFS
Sign inStart free
sammasaksammasak/claude-code-skills/skills/knowledge-vault/SKILL.md

knowledge-vault

Skill1 starsChanged 28 days agoMITView on GitHub

Use when the user mentions a person, company, situation, or prior decision you don't recognise, when you need context from ~/knowledge, or when explicitly asked to write a runbook, ADR, or other durable reference to the vault (not ~/.claude MEMORY.md).

4 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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. Distinctive:

    Search discipline and the write gate are owned by the global CLAUDE.md (subagent-only search.

    line 10
  2. Very specific:

    After adding or renaming files, update the room's INDEX.md to match.

    line 15

“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

Knowledge Vault (~/knowledge)

Plain GFM markdown in a git repo, organised as rooms (INDEX.md for discovery + CONTEXT.md for operating in the room). ~/knowledge/CLAUDE.md is the routing map. Career/people: whoami/; personal admin: personal/; systems: homelab/; multi-step guides: workflows/<name>/CONTEXT.md.

Search discipline and the write gate are owned by the global CLAUDE.md (subagent-only search; durable reference only, commit-first). This skill owns the writing mechanics:

  • Links: relative markdown paths from the current file, e.g. [age keys](../nix/sops-nixos.md#age-keys); check with test -f "$(dirname <file>)/<relpath>". Standard GFM only: no [[...]] links, embeds, or callout syntax.
  • Placement: ADRs at <room>/decisions/ADR-NNN-slug.md, RFCs at <room>/decisions/RFC-YYYY-MM-slug.md, binary sources in a co-located sources/.
  • ADR frontmatter: status (proposed | accepted | deprecated | superseded), date, supersedes, related; sections Context, Decision (one sentence), Options Considered (table), Consequences, Links.
  • After adding or renaming files, update the room's INDEX.md to match. (Naming and the commit+push flow are owned by the global CLAUDE.md.)

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