fulcra-vault

Read and write a shared markdown knowledge vault in Fulcra with wikilinks and agent-owned sections.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-vault-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-vault
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/packages/fulcra-vault/skill
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-vault-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents lose durable context between sessions, and shared knowledge about projects, people, and decisions ends up scattered or forgotten. This Skill gives agents a persistent markdown knowledge vault stored in the user's Fulcra account, so durable context survives across sessions and agents. ## Core Features & Use Cases - Session-start loading: Read HOT.md for a compact summary of what's hot, with optional SessionStart hooks for Claude Code or Codex that inject it automatically. - Structured reads and writes: Read notes with backlinks, write only your agent-owned section of a note, and append timestamped entries to the shared append-only Log. - Link index and map: Link notes with [[wikilinks]], then rebuild backlinks and MAP.md/HOT.md with reindex and map commands. - Capability-based routing: Use the CLI when shell access is available, raw HTTP with device-flow auth when only HTTP is possible, or MCP for read-only access. - Use Case: An agent finishes a planning session, logs the decisions made on the relevant project note, updates its owned section with new durable context, and reindexes so the next session's agent sees the current state in HOT.md. ## Quick Start Install the fulcra-vault CLI, run fulcra auth login, then ask the agent to read HOT and write durable context about the current project back to the vault.

Frequently Asked Questions about fulcra-vault

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent persistent memory across sessions?

Store durable context as markdown notes in a Fulcra vault and have the agent read HOT.md at session start. The agent writes updates to its owned section and appends decisions to the shared log, so the next session picks up current state.

How do I set up the fulcra-vault CLI?

Install with uv tool install from the fulcra-tools GitHub repository, then run fulcra auth login to authenticate. Run fulcra-vault init to scaffold meta.json, MAP.md, HOT.md, LOG.md, and seed notes.

Can I use the vault without shell access or the CLI?

Yes, agents with HTTP access can use the Fulcra Files API directly with device-flow authentication, following the tier-2 HTTP reference. Agents with only the Fulcra MCP get read-only access to data the MCP exposes.

How do wikilinks and backlinks work in the vault?

Reference other notes with [[Note Title]] syntax, then run fulcra-vault reindex and map to rebuild the link index. Backlinks for a note are shown with the backlinks command or the --with-backlinks read flag.

What happens if two agents write to the same note?

Each agent edits only its own owned section delimited by HTML markers, and the shared Log is append-only. Writes abort if the note changed between read and write, so the agent re-reads and retries.

Why is HOT.md empty at session start?

Empty HOT.md output means no vault has been initialized yet or no content has been written. Run fulcra-vault init to onboard, then start writing durable context so HOT.md renders notes.