Skill instructions
exomem20.2 KB
View saved version →
---
name: exomem
description: Use Exomem for governed knowledge-base recall, capture, compilation, connections, review, and preservation. Engage for Exomem, KB, vault, Obsidian or notes, including save, log, compile, "interesting, save it", and "what did I conclude"; consult prior project/domain knowledge and capture durable outcomes according to the active engagement policy. Sources and Evidence stay immutable; content outside the managed Knowledge Base stays read-only.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.32.0"
---
# Exomem
Exomem is the connector/MCP; the Knowledge Base is the governed layer inside a
markdown vault (Obsidian optional). Keep temporary working context in the current
conversation. Exomem holds durable preferences, feedback, personal baselines,
project knowledge, sourced conclusions, decisions, failures, and proof-bearing records.
Capture follows the live engagement policy. Use native assistant memory only as
an explicit fallback when Exomem cannot capture; move durable results when it can.
**Sources are immutable. Compiled material is governed. Evidence is preserved.**
Raw inputs go to `Sources/`; proof-bearing artifacts to `Evidence/`; conclusions
to `Notes/`; stable reusable identities to `Entities/`. Sources/Evidence are
append-only. Everything outside `Knowledge Base/` is read-only input, and
in-vault readonly/excluded paths remain protected. Prefer supersession over
removal; never invent IDs, sources, relations, or numeric confidence scores.
Use product tools so validation, indexes, logs, and provenance stay governed.
## Loading the tools
Load only the tools needed for the current intent. With deferred discovery,
Claude Code can use `ToolSearch("select:ask_memory")` for a lookup, then discover
`read_memory` after selecting a hit. Other harnesses use their own tool discovery
or directly call already exposed tools; `select:` is not a portable requirement.
Do not preload the mutation/media catalogue for recall.
Use `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` once
when this session lacks the current `engagement` (including `envelope`) or active
capability information. Reuse it until policy, connection, adapter, or returned
vault configuration/registry state changes. Inspect the exposed bootstrap schema: if it lacks
`skill_contract`, request `bootstrap(profile="compact")` directly. Otherwise request session;
if the server rejects the session profile or argument, request compact once. The static skill
cannot tell you a user's current overrides. Generic MCP clients without this skill
obtain their portable operating contract from compact bootstrap. Use
`profile="diagnostics"` only when investigating compute, timing, reranking, or
retrieval configuration.
Never recommend an unavailable command: `available_product_tools` belongs to the
active adapter, identified by `active_capabilities.active_capability_sha256`;
the canonical MCP discovery fingerprint describes a different, full surface.
Read the linked procedure **before doing the corresponding work**, once per
session unless it changes. For large reference manuals, read the relevant
operation or page-type section, not the entire catalogue. Paths are relative to this skill package: use the
harness's filesystem or bundled-resource reader. Do not bulk-load references.
If a required reference cannot be read, obtain the portable contract through
bootstrap; do not improvise a mutation whose rules remain unavailable.
| Current intent | Tools to discover as needed | Required procedure |
|---|---|---|
| Ordinary recall | `activate_context` for a turn with no prior context, then `ask_memory` and `read_memory`; `browse_memory` for structure | The short recall loop below suffices |
| Filtered/unit/media recall, unresolved identities, or retrieval diagnostics | `ask_memory`, `read_memory`, `connect_memory`, `query_dataset`, `read_media` | [recall](references/recall.md) |Preview of the first 4,000 characters. Read full instructions →
Referenced files: 18 — file references are metadata, not package contents.
exomem-capture20.8 KB
View saved version →
---
name: exomem-capture
description: Preserve a durable conclusion or recurring entity from a conversation without dumping transcripts into compiled memory.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-capture
## Purpose
Save durable conclusions and recurring entities at the right epistemic layer.
## When to use
Use when the user asks to save or the session lands on durable reusable knowledge, including stable context about a recurring entity.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Durable personal baselines
A stable preference, recurring routine, historical baseline, or durable affiliation
is eligible only when both stability or recurrence and reusable comparison,
interpretation, or decision value are clear. Attach a facet or affiliation to a
uniquely resolved Entity; otherwise write one concise compiled observation. Use
Records only for an observed measurement accepted by a compatible existing
collection. Fleeting preferences, one-off activity, incidental associations, trivial
metrics, and tentative events stay quiet. Durable interpretations retain explicit
attribution and uncertainty rather than becoming established facts. Eligibility never creates an Entity,
collection, or schema. Concise observations and narrow additive facts follow
`proactive_capture`; a new Entity or your own affiliation edge follows `proactive_capture`;
accepting a queued relation uses `link_acceptance`; merge or substantial curation uses
confirmed `restructure_execution`.
## Workflow
Before choosing a destination, partition the exchange into independently reusable
objects by retrieval question, subject/domain, temporal episode, and epistemic
role. Reuse current relevant recall and resolve each meaningful cluster against
canonical homes. The open note has no priority; keep details within one coherent
scope together. Preserve durable hypotheses as attributed, uncertain claims.
Perform one completeness/dest
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-continue14.3 KB
View saved version →
---
name: exomem-continue
description: Resume prior project or session context from Exomem when the user wants to continue, pick something back up, or remember what was happening on a topic.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-continue
## Purpose
Resume prior context without guessing from chat history alone.
## When to use
Use when the user asks to continue, resume, pick up a project, recover prior state, or asks what they were doing on a topic.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search first with `ask_memory(detail="compact", rerank=false)`, preferring active compiled notes and project-relevant terms from the prompt.
2. Use `ask_memory(deep=true)` when several hits matter or the state needs synthesis.
3. Read only the top relevant pages with `read_memory` when excerpts are not enough.
4. Prefer recent active compiled notes, then linked sources/evidence when provenance is needed.
5. Read the Planning inventory with `plan_memory(action="inspect")` (no collection) when the topic has one, and read the due-state block any response already carried rather than re-deriving it. Both are read-only and create nothing.
6. Summarize current state, decisions already made, blockers, and likely next actions.
## Relation governance
Resolve typed meaning with `resolve-relation` before authoring. Reuse a specific
truthful match; otherwise choose honest `relates_to` or no edge. Durable recurring
meaning is proposal-first through `propose-relation` and hash-guarded
`save-relations`; corrections use a new canonical key and deprecate the old one.
## Output contract
Return a compact continuation brief with cited Exomem pages and a short next-action list. Say when the search missed or was thin.
## Save rules
Save only if the resumed work produces a new durable decision, solved problem, failure, pattern, or research finding. Use `remember`, `edit_memory`, or `replace_memory` as
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-curate16.3 KB
View saved version →
---
name: exomem-curate
description: Improve Exomem note quality by adding links, clarifying compiled notes, and organizing safely without editing raw Sources or Evidence.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.2.0"
---
# exomem-curate
## Purpose
Improve the KB graph and compiled-note quality without damaging provenance.
## When to use
Use when the user asks to clean up, organize, link, tidy, or improve a set of Exomem notes.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search related notes with `ask_memory`; use `connect_memory(operation="suggest-links")` for link candidates, `"suggest-relations"` when direction matters, and `"graph-context"` for graph shape or inbound links.
2. Identify safe improvements — missing links, stale wording, weak titles, duplicate tags, or unlinked entities — starting from `review_memory(mode="relation-debt")` for pages with no outbound edges and `mode="relation-queue"` for already-reviewed candidates.
3. For a bounded set of explicitly selected pages, call `maintain_memory(mode="curation", curation_action="work-item", refs=[...], paths=[...])`. This is `structural_suggestions`: it assembles recorded context and never chooses semantics or writes content.
4. Author the typed plan yourself, then call `maintain_memory(mode="curation", curation_action="propose", plan={...})`. Inspect it with `maintain_memory(mode="curation", curation_action="preview", run_id=...)`; preview the immutable plan once and surface its exact actions, blockers, fingerprint, and compensation classes.
5. Before any execution, treat the plan as `restructure_execution`: obtain one explicit confirmation for that exact plan fingerprint. Do not infer confirmation from the request to inspect or improve notes, and do not accept standing approval.
6. On confirmation, call `maintain_memory(mode="curation", curation_action="apply", run_id=..., plan_id=..., expected_plan_fingerprint=..., why=...)`. Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-defrag13.7 KB
View saved version →
---
name: exomem-defrag
description: Reconcile duplicate, stale, or conflicting Exomem memory while preserving history through review, merge, or supersession.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-defrag
## Purpose
Reduce duplicate, stale, or conflicting memory without losing provenance.
## When to use
Use when the user asks to defrag a topic, reconcile notes, resolve contradictions, merge duplicates, or inspect what is stale.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search the topic with `ask_memory`, using `ask_memory(deep=true)`, `connect_memory`, or `review_memory` when graph, stale, audit, or evolution context matters.
2. Group findings into keep, merge, supersede, or leave alone.
3. Read candidate pages with `read_memory`, including history when needed.
4. Use `replace_memory` for changed conclusions and `edit_memory` only for minor corrections.
5. Preserve raw sources and evidence; keep superseded history visible.
6. When you supersede or merge, carry the merged notes' `sources:` and outbound links onto the survivor — a merge that drops edges loses graph value the superseded page can no longer carry. Check `review_memory(mode="relation-debt")` on the survivor afterwards.
## Relation governance
Resolve typed meaning with `resolve-relation` before authoring. Reuse a specific
truthful match; otherwise choose honest `relates_to` or no edge. Durable recurring
meaning is proposal-first through `propose-relation` and hash-guarded
`save-relations`; corrections use a new canonical key and deprecate the old one.
## Output contract
Return the reconciliation decision for each candidate and the paths changed or left alone.
## Save rules
Only mutate when the correct action is clear. Use supersession for meaningful changes.
## Mistakes to avoid
Do not auto-delete memory. Do not treat semantic proximity as contradiction by itself. Do not merge notes that answer differen
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-ingest14.9 KB
View saved version →
---
name: exomem-ingest
description: Ingest an external article, PDF, pasted note, dataset, image, audio, or video into Exomem while preserving raw evidence before compiling conclusions.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-ingest
## Purpose
Turn external artifacts into preserved evidence plus useful compiled memory.
## When to use
Use when the user asks to ingest, add, import, process, or preserve an external source or artifact.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Identify the artifact type: text, article, PDF, dataset, image, audio, video, or mixed media.
2. Preserve the raw source first with `capture_source` — `content` for text, `files` for an attached transcript, article, or screenshot. Reach for `preserve_evidence`, `preserve_artifacts`, or the `transfer_artifact` fallback only when the artifact is proof-bearing rather than raw material.
Pass `source_kind` and `domain` on a `capture_source` call — both are open
vocabularies, so name the label that fits even if it is unfamiliar. A kind is
required, and there is no catch-all.
3. Media processing is automatic; use `process_media` for immediate reconciliation, actionable status, or retry, then inspect via `read_media`, extracted text/OCR/transcripts, or media-aware `ask_memory`.
4. If the source is worth distilling, use `compile_source` to plan and draft the compiled note — including the path preserved in step 2 as `sources:`. That is what links the note back to the raw artifact and marks the source processed; omit it and the source stays in the unprocessed backlog forever.
5. Reuse known meaningful connections; use `connect_memory(operation="suggest-links")` when candidates are still missing and review them. Then write with `remember`, carrying the sources and accepted links in this first write.
## Vocabulary
Read [vocabulary](references/vocabulary.md) before changing a registry.
If the vocabula
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-media13.9 KB
View saved version →
---
name: exomem-media
description: Search, inspect, cite, and preserve Exomem media artifacts such as PDFs, images, audio, and video.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-media
## Purpose
Use Exomem's multimodal substrate without flattening every artifact into text.
## When to use
Use when the user asks to find media evidence, look inside a recording, inspect a PDF/image/audio/video, or recall where something appeared.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search with media-aware filters or artifact terms using `ask_memory`.
2. Use artifact-specific product tools: extracted text/OCR/transcripts, `process_media` status/retry, `read_media`, `preserve_artifacts` for file handles, fallback `transfer_artifact`, upload metadata, or preserved evidence paths.
3. Cite raw artifact paths and timestamps/pages/frames when available.
4. Preserve new raw artifacts with `capture_source`, `preserve_evidence`, `preserve_artifacts` for file handles, or fallback `transfer_artifact` before analyzing them.
5. Draft textual conclusions only when there is a durable finding, naming the preserved artifact in `sources:`.
6. Reuse known meaningful connections; use `connect_memory(operation="suggest-links")` when candidates are still missing and review them. Then write with `remember`, carrying the sources and accepted connections in the first write.
## Relation governance
Resolve typed meaning with `resolve-relation` before authoring. Reuse a specific
truthful match; otherwise choose honest `relates_to` or no edge. Durable recurring
meaning is proposal-first through `propose-relation` and hash-guarded
`save-relations`; corrections use a new canonical key and deprecate the old one.
## Output contract
Return matching artifacts, what was inspected, citations, and any compiled conclusion path.
## Save rules
Raw media belongs in `Sources/` or `Evidence/`; textual notes should summarize co
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-reflect13.7 KB
View saved version →
---
name: exomem-reflect
description: Distill a session or project episode into decisions, failures, patterns, open questions, and next actions.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-reflect
## Purpose
Convert experience into reusable memory.
## When to use
Use when the user asks what was learned, asks to reflect, closes a project episode, or wants patterns extracted from a session.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search Exomem with `ask_memory` for the project/topic so reflection builds on existing memory.
2. Extract durable decisions, solved problems, diagnosed failures, reusable patterns, open questions, and next actions.
3. Draft each durable conclusion at the right type: `insight`, `failure`, `pattern`, or `research-note`. Cite the session capture or prior notes it draws on in `sources:`.
4. Prefer one strong note over many weak notes unless the conclusions are genuinely different.
5. Link the pages you already read in step 1 inline, using `connect_memory(operation="suggest-links")` to catch the ones you missed; draft the edges that carry direction under `## Relations`. Then save with `remember`, carrying the sources and accepted links in the first write.
## Relation governance
Resolve typed meaning with `resolve-relation` before authoring. Reuse a specific
truthful match; otherwise choose honest `relates_to` or no edge. Durable recurring
meaning is proposal-first through `propose-relation` and hash-guarded
`save-relations`; corrections use a new canonical key and deprecate the old one.
## Output contract
Return what was saved, what was intentionally not saved, and remaining open questions.
## Save rules
Save conclusions, not a transcript. Keep enough context that the lesson is reusable later.
## Mistakes to avoid
Do not capture every turn. Do not flatten failures and patterns into generic summaries. Do not erase uncertainty or next actions.
<!--
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-research13.9 KB
View saved version →
---
name: exomem-research
description: "Run a focused research loop with Exomem: gather sources, preserve evidence, compile attributed findings, and connect prior notes."
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.1.0"
---
# exomem-research
## Purpose
Answer a focused question and save what should compound.
## When to use
Use when the user asks to research a topic, compare options, investigate a claim, or save findings from a research pass.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Search Exomem first with `ask_memory` for prior conclusions and related sources.
2. Gather external sources only as needed; preserve important raw sources with `capture_source`, passing `files` when the client can hand over an attachment. `preserve_evidence`, `preserve_artifacts`, and the `transfer_artifact` fallback are for proof-bearing artifacts, not for raw material.
3. Attribute findings to sources and distinguish evidence from interpretation.
4. Draft the result as a `research-note` unless another type clearly fits, listing every source preserved in step 2 in `sources:`.
5. Reuse meaningful connections from the research context; use `connect_memory(operation="suggest-links")` when candidates are still missing and review related prior notes. Then write with `remember`, including the sources and accepted connections in the first write.
## Relation governance
Resolve typed meaning with `resolve-relation` before authoring. Reuse a specific
truthful match; otherwise choose honest `relates_to` or no edge. Durable recurring
meaning is proposal-first through `propose-relation` and hash-guarded
`save-relations`; corrections use a new canonical key and deprecate the old one.
## Output contract
Return findings, cited sources, limits, saved path, and follow-up questions.
## Save rules
Save findings that answer the question, change a decision, or create reusable context. Keep source attribution explicit.
## Mistak
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
exomem-review17.3 KB
View saved version →
---
name: exomem-review
description: Use Exomem's Epistemic Inbox and audit queues to surface stale conclusions, contradictions, relation debt, and unprocessed sources safely.
metadata:
skill_contract: 0d23c50d8751e79c26e99bbe70bc7adfcdf460c8ba88dd7bde037f50d2190af0
version: "0.2.0"
---
# exomem-review
## Purpose
Drain Exomem review queues into safe next actions.
## When to use
Use when the user asks to review the KB, see what needs attention, drain backlog,
or inspect stale, contradictory, disconnected, or unprocessed material.
## Portable operating rules
Before the first operation, inspect the exposed bootstrap schema. If it lacks `skill_contract`, obtain `bootstrap(profile="compact")` directly. Otherwise obtain `bootstrap(profile="session", skill_contract=<metadata.skill_contract>)` if current policy or capabilities are missing; honor `engagement.envelope` and `available_product_tools`. Reuse returned state until policy, connection, adapter, or returned vault configuration/registry state changes. If the server rejects the session profile or argument, obtain `bootstrap(profile="compact")` once. Use the harness's supported discovery mechanism and load only the tools needed now. If the applicable local procedure cannot be read, obtain the portable compact contract; do not improvise a write.
Do not invoke tools absent from `available_product_tools`; use the live capability list even when a bundled workflow mentions a withheld operation.
Use `configure_memory` set/clear only for an explicit user request to change saved engagement.
Recall, capture, installation and missing hooks use the existing preference;
none authorizes changing it. Inspect first when the user requests a change.
Sources/Evidence are immutable, and content outside the managed Knowledge Base
is read-only. Before a compiled write: reuse current relevant search/read results,
check for duplicates, and include known source references and reviewed connections
in the first write. Use `connect_memory(operation="suggest-links")` when useful
connections are still unknown, not to recheck links already established in context.
Honor the live confirmation ceiling;
a workflow or standing capture preference does not grant restructure authority.
Inspect mutation results before reporting success. On `success: false`, follow
the structured error. For warming, busy, pending, or
`MUTATION_COMMITTED_ACKNOWLEDGEMENT_UNCERTAIN`, preserve the same mutation identity
and unchanged payload; wait/reconcile/retry only as instructed, never with a new
identity after an uncertain commit.
## Workflow
1. Start with `review_memory(mode="attention")` for the ranked review queue.
2. Use `review_memory(mode="audit")` when the user asks for broader health checks or specific categories.
3. For unprocessed sources, use `compile_source` before writing a compiled note with `remember`, passing those source paths as `sources:` so the source leaves the unprocessed queue.
4. For relation debt, inspect `connect_memory(operation="suggest-relations")` or
`suggest-links`; write accepted note edges under `## Relations`, never from
semantic proximity alone.
5. For stale or contradictory compiled notes, read the relevant pages with `read_memory` and decide keep, `edit_memory`, `replace_memory`, `maintain_memory`, or leave alone.
6. For recurring unregistered relation labels, propose promotion with `schema_memory(subject="relations")` rather than rewriting the notes that use them.
7. Use `triage_memory` only after an explicit decision to dismiss, snooze, or
reopen an Inbox item, and lead its `why` with a review reason code —
`intentional:`, `false_positive:`, `handled:`, `deferred:`, or
`too_frequent:` — so the decision is still legible months later.
8. When the user wants to stop hearing about a whole KIND of signal, quiet that
family rather than lowering prominence, which silences everything:
`triage_memory(ref="exomem://review/family/<family>", action="quiet")` with a
reason
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.