agentleFS
Sign inStart free
pantheon-orgpantheon-org/tekhne/skills/agentic-harness/vault-capture/SKILL.md

vault-capture

Skill10 starsChanged 39 days agoMITView on GitHub

Captures an important insight, decision, constraint, pattern, or discovery to persistent memory via the vault CLI — distinct from general note-taking in that entries are tagged, tiered, and retrievable across future sessions. Use when the user says "save this", "remember this", "note for later", "don't forget", or "keep this in mind", or when the conversation produces something worth preserving: architectural decisions, recurring bugs, hard-won constraints, naming conventions, or user preferences.

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

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before capturing, answer two questions:

    line 20
  2. Very specific:

    Is this time-bound?: If yes → episodic. If no, continue.

    line 22
  3. Very specific:

    Is this a how-to process?: If yes → procedural. If no → semantic.

    line 23
  4. Very specific:

    Always capture with --project when working in a project context.

    line 25
  5. Distinctive:

    Use whenever the conversation produces:

    line 31
  6. Very specific:

    Always double-quote the --text value to handle apostrophes and special characters.

    line 44
  7. Very specific:

    Never omit --project: when working inside a project — global memories pollute cross-project searches

    line 73

“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

vault-capture

Persist a memory to the vault so it can be retrieved in future sessions.

Mindset

Before capturing, answer two questions:

  1. Is this time-bound? If yes → episodic. If no, continue.
  2. Is this a how-to process? If yes → procedural. If no → semantic.

Always capture with --project when working in a project context. Always add --tags with at least two relevant keywords — they are the primary BM25 signal for future retrieval.

When to use

Use whenever the conversation produces:

  • A confirmed decision ("we're using X instead of Y")
  • A constraint that must not be violated
  • A recurring bug or workaround
  • A project convention or naming pattern
  • A user preference expressed explicitly

How to use

vault-cli capture --text "<memory content>" [--tier episodic|semantic|procedural] [--project <id>] [--tags tag1,tag2]

Always double-quote the --text value to handle apostrophes and special characters.

Or pipe from stdin:

echo "<memory content>" | vault-cli capture

Tier selection

QuestionAnswerTier
Is this tied to today's session or a specific event?Yesepisodic (default)
Is this a rule, fact, or convention that should persist indefinitely?Yessemantic
Is this a step-by-step process or how-to?Yesprocedural

Examples

vault-cli capture --text "Decided to use Bun instead of Node for all scripts. Reason: workspace protocol support." --tier semantic --tags bun,tooling --project vault-core

vault-cli capture --text "Never use --force-push on main. CI enforces branch protection." --tier procedural --tags git,ci

vault-cli capture --text "Auth service fails silently when DB not ready — add depends_on with condition: service_healthy in docker-compose." --tier episodic --tags docker,auth,bug --project api

Never

  • Never omit --tier for a rule or convention — defaulting to episodic means it will decay and be consolidated away
  • Never capture without --tags — untagged memories score poorly in BM25 retrieval
  • Never omit --project when working inside a project — global memories pollute cross-project searches
  • Never use single quotes around --text — apostrophes in content will break the shell command

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