Menu

Individual skill

memory-dream

0upvotes

Curate the workspace memory wiki as its appointed orchestrator. Trigger on a Cloud-scheduled Dream task or a user's direct curation request. Inspect candidates for orphan leaves, near-duplicates, stale pages, remote conflicts and oversized hubs; browse the graph, cluster leaves into INDEX/hub/leaf structure, maintain authored overview prose, split hubs, merge duplicates and verify/report changes. Use memory_curate and memory_browse; preserve machine-generated hub TOCs and graph-derived INDEX Contents. Orchestrator-only: write verbs reject other actors with 403. Follow the body for safe mutation and verification procedures.

sdk/cloud/catalog/skills/memory-dream/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,364
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Memory Dream — orchestrator-driven consolidation

> **Memory pages are PKF (`.pkf`).** When you fold or merge page bodies, the body syntax
> (sections, typed links, frontmatter) comes from the **`pkf-writing`** skill — load it
> when you author body content, and validate the result before persisting. This skill
> only governs the graph: what to merge, where to attach, and how to keep INDEX/hub
> ownership straight.

> **Candidate boundary.** Dream sees authoritative **Memory Pages**, not “all PKF.” A
> message-inline PKF or Library `.pkf` Asset remains outside this loop. Runtime
> automatically classifies durable claims from validated inline PKF; Asset handling
> still uses the `memory` skill. Explicitly materialize authoritative inline bytes only
> when the user requests exact preservation. Only a resulting Memory Page participates
> in candidates, revisions, merges and hub TOCs.
Back to top