agentleFS
AJ-EdelmanAJ-Edelman/GraphPlusContext/skills/context-vault/SKILL.md

context-vault

Skill0 starsChanged 3 months agoMITView on GitHub

The durable context layer for multi-session agent work — dispatch, wind-down, wake, verification, and continuity across model/profile/tool switches. Trigger whenever a session is asked to wind down, hand off, or end; when asked to verify a predecessor's handoff or receipt; when dispatching work to a project; when waking or resuming from a handoff or interruption; when adding a project; when the user switches accounts, subscriptions, or tools; and when starting substantive work with no project named. Also on '/context-vault'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. IgorGanapolsky/mac-yolo-safeguards★ 3same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    The vault for this machine lives at __VAULT_PATH__: Do not restate its contents here or anywhere — read the live files:

    line 12
  2. Very specific:

    Follow the matching procedures.md template verbatim: Never paraphrase a template, never invent a new one inline.

    line 25
  3. Distinctive:

    Pointers only: Never copy source content into the vault.

    line 30
  4. Distinctive:

    Bank before dying: If context is degrading or the session is ending, run the applicable wind-down (§2 or §3) without being asked.

    line 33
  5. Distinctive:

    Every wind-down is followed by outside verification (§4): before any successor launches.

    line 35

≈ “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

Context vault — the durable layer

Sessions are disposable. Context is not. The vault is a folder of plain markdown that outlives every session, model, subscription, and tool, so a fresh agent can reconstruct working state in under a minute.

The vault for this machine lives at __VAULT_PATH__. Do not restate its contents here or anywhere — read the live files:

  1. README.md — conventions (pointers only; one writer per surface; the dispatch template).
  2. procedures.md — the moves. §1 dispatch · §2 standard wind-down · §3 save-point wind-down · §4 outside-in verification · §5 standard wake · §6 sealed-entrance wake · §7 account/tool switches.
  3. boot.md — the live cursor: active projects, current focus, read-first pointers.
  4. projects/<name>/index.md — per project: Goal · Status · Code location · Key docs · Open threads.

Rules of engagement

  • Follow the matching procedures.md template verbatim. Never paraphrase a template, never invent a new one inline. The templates are the interface.
  • One writer per surface. Your writes are limited to the index of a project you actually changed, plus your own seats/YYYY-MM-DD-<seat-name>.md log. boot.md and other projects' indexes belong to the orchestrator.
  • Pointers only. Never copy source content into the vault. Status lines are command-derived at write time (git log, test output, a live probe) — never from memory. Ambiguity is recorded in Open threads, never guessed away.
  • Bank before dying. If context is degrading or the session is ending, run the applicable wind-down (§2 or §3) without being asked.
  • Every wind-down is followed by outside verification (§4) before any successor launches. A predecessor's "DONE" is a claim, not a receipt.
  • Sealed-entrance runs (a long sprint driven by its own execution prompt) bypass the vault at launch and relaunch with the identical one line (§6). Never brief a sealed session about its own interruption — its resume law and its committed receipts already handle it.

The two-line interface

Once installed, the operator's whole vocabulary is:

  • <project>: <what you want> — starts or resumes work.
  • wind down — banks the session to disk.
  • verify the wind-down for <project> — an outside-in check before the successor starts.

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.