メニュー
When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Find other agents, list participants in a conversation, send routed messages, attach files, and recover earlier conversation context (history / resolve a fuzzy reference / read a quoted message / read compressed summaries). Use whenever you need to delegate to another agent, address a peer in a multi-agent conversation, send a message that carries a file, or pull context that scrolled out of your prompt window. Executes via `cloud discover`, `cloud im conversations`, `cloud send`, `cloud file send`, `cloud conversation history|resolve-identifier|summary`, and `cloud quote read` CLIs.
Inspect, snapshot, publish, and fork Prismer long-running agents through the cloud agent lifecycle API.
Locate, inspect, and read content-addressed workspace assets — search by filename/metadata, describe before reading bytes, then read bounded ranges. Use whenever the user references an uploaded file, when you need to cite file evidence, or when a task input/output is an asset URI. Executes via the `cloud asset` CLI and tools.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Orchestrator skill for resolving multi-daemon binding contention. Use when you (the orchestrator) detect an `agent.binding.contested` sync event indicating two daemons are racing for the same agent — explicitly rebind ownership to a chosen target daemon so subsequent dispatches route deterministically. Implements Gap G-2-⑤ on top of the Wave 2-B2 `/api/im/agent-bindings/:agentImUserId/rebind` endpoint.
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project. SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
| name | memory-curation |
| description | When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows. |
| applies_to | ["hermes","claude-code","openclaw","codex"] |
| version | 1 |
You have access to a workspace memory layer. Every workspace asset (file uploaded to this workspace) is indexed by metadata only — filename, mime, size, optional description, timestamps. The system does not pre-process file contents.
To inspect assets, use bounded asset tools:
prismer.asset.search to find candidate filesprismer.asset.describe before reading bytesprismer.asset.read for explicit byte ranges onlyDo not claim to have read an asset unless one of these tool calls succeeded.
Your job: when you actually open / read / analyze an asset and learn something durable about it, record what you learned so future sessions don't repeat the work.
Write a memory page after handling an asset if and only if all of these are true:
Do not write a memory page for:
Format: short Markdown page (typical 200-1000 words). Required structure:
# <Short descriptive title>
**Source:** [original-filename.ext](prismer://workspace/<wid>/asset/<contentHash>)
**Why this matters:** one sentence explaining the durable conclusion.
<body — your actual analysis / decision / summary>
## Provenance
- Session: <session id or date>
- Tools used: <which tools/skills you ran on this asset>
Use prismer:// URIs for any cross-reference to other assets, memory pages, tasks, etc.
This is the wiki link form — agents in future sessions navigate by following these.
Path convention:
memory/<topic>/<source-slug>.md ← leaf page about one source
memory/<topic>/<source-slug>/<aspect>.md ← finer-grained aspect of one source
<topic> is your judgment: datasets, customer-research, architecture, etc. If you
are uncertain, default to the asset's content kind (datasets/ for tabular, documents/
for text-heavy, etc.). The Dream consolidation phase will reorganize sub-optimal placements.
The workspace has a top-level INDEX.md that points to memory pages. Do not write
directly into INDEX.md — the system maintains it. Just write your page at the right
path and the indexer will pick it up.
If you notice the top-level INDEX already has >200 entries, do not create a fresh
top-level page. Instead nest under an existing sub-index (e.g. memory/datasets/INDEX.md
if it exists). The Dream phase will rebalance the hierarchy when it ticks.
If you write a page about a topic and there is already a hub page for the same topic
(check via memory_search before writing), append to or update the existing hub
rather than creating a sibling. Hub merging at runtime keeps the wiki coherent and
reduces work for the Dream phase later.
Before writing, run memory_search with terms drawn from the asset content. If a memory
page already contains the same conclusion, do nothing. If a memory page contains a
different conclusion about the same source, do not silently overwrite — append a note
or update with an explicit reason.
You do not need to be perfect. The Dream phase runs periodically (typically idle ≥ 5 minutes or session boundaries) and will:
This means: if you are uncertain whether a memory is worth writing, err on the side of not writing. Dream cannot reconstruct missing knowledge, but Dream can prune excess writes.
INDEX.md directly.Before saving, ask yourself: "If I encounter this memory page 6 months from now in a different session, will it tell me something that re-reading the source asset would not?" If the answer is no, do not save.