intendant-memory

Propose and search durable machine-wide claims on the Intendant daemon's Memory plane.

14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/intendant-dev/Intendant --skill intendant-memory-intendant-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intendant-memory
Source: https://github.com/intendant-dev/Intendant/tree/main/skills/intendant-memory
Command: npx skills add https://github.com/intendant-dev/Intendant --skill intendant-memory-intendant-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents lose hard-won knowledge between sessions, forcing every new session to re-derive facts about the machine, its owner, and its projects. This Skill provides a shared, provenance-labeled Memory plane on the Intendant daemon where durable claims persist and are searchable by every agent and the owner. ## Core Features & Use Cases - Claim proposals: Record observations, decisions, procedures, preferences, and episodes as claims with automatic session attribution and sensitivity labels. - Deliberate search: Query the Memory plane before assuming or re-deriving machine-wide facts, with candidate claims shown only on request. - Owner-governed judgment: Agents author candidates only; the owner accepts, disputes, supersedes, or retires claims, and disagreements are handled via counter-proposals. - Use Case: After discovering that the CI mac leg doubles as the dev box, propose it as an observation so future sessions find it via memory search instead of re-investigating. ## Quick Start Ask the agent to search Intendant memory for what earlier sessions learned about this machine, then propose any new durable fact as a claim.

Frequently Asked Questions about intendant-memory

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

FAQPage Schema
How do I propose a memory claim to the Intendant daemon?▼

Run intendant ctl memory propose with the statement text, a --kind flag (observation, decision, episode, procedure, or preference), and optional --label or --sensitivity flags. Direct tool callers use the memory_propose tool with the same vocabulary.

How do I search Intendant memory before starting a task?▼

Run intendant ctl memory search with your query terms, adding --candidates to include unjudged candidate claims, which are hidden by default. Use memory read with a claim id prefix of at least 8 hex characters to fetch one claim.

Can an agent accept or dispute memory claims itself?▼

No. Judgment verbs like accept, dispute, retire, and supersede are owner-only acts; agents calling them receive an actor-not-permitted refusal. An agent that disagrees should propose a counter-claim with its evidence instead.

Does Intendant memory work without a running daemon?▼

No. The skill requires a reachable Intendant daemon; supervised sessions get $INTENDANT and INTENDANT_MCP_URL injected. If the CLI resolves but the daemon does not answer, the daemon is down and the skill cannot operate.

Does Intendant memory replace my agent's own memory system?▼

No. The Memory plane is only for knowledge the whole machine should share; session-private and project-private notes stay in your native memory. Never bulk-copy private memory into the shared plane.