How do I install the Agentprivacy Wiki Dream Cycle skill?

Run npx skillmds@latest add mitchuski/agentprivacy-wiki-dream-cycle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentprivacy Wiki Dream Cycle safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentprivacy Wiki Dream Cycle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentprivacy Wiki Dream Cycle free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Agentprivacy Wiki Dream Cycle?

mitchuski (@mitchuski) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentprivacy Wiki Dream Cycle by mitchuski

Name: Agentprivacy Wiki Dream Cycle
Author: mitchuski

Agentprivacy Wiki Dream Cycle

The standing research loop that keeps the static guide rebound to the source. Each relevant /mitch repo "dreams" about itself — a deep multi-lap pass that diffs the repo's canon against the live FedWiki, writes a standing `chronicles/DREAM-<date>.md` (its resumable work-ledger), and feeds a single confirm-able GATE document. The First Person ticks the GATE; builders write the approved canon into ~/.wiki; the snapshot publishes it. Activates when planning what to fill into the guide next, running a daily research cycle, fanning out per-directory gap analysis, or turning "what's missing" into ordered next actions. Four stages — RESEARCH → GATE → BUILD → SNAPSHOT — looped until comfortable to push. Authored by the Chronicler 🧙📖, kept by the Librarian 🗃️.

mitchuski Updated Sep 17, 2026

File contents

agentprivacy-wiki-dream-cycle

The dream cycle is how the agentprivacy guide stays rebound to the universe across /mitch. Where agentprivacy-wiki-resync is the per-turn operation ("I changed a repo → rebuild the wiki"), the dream cycle is the discovery layer that runs before you know what to change: every current repo dreams about itself, surfaces its gaps, and proposes what to fill — and the First Person decides.

It is the Chronicler's loop (it produces chronicles) cataloged by the Librarian (the wikis/ keeper). The dream files are standing ledgers that travel with each repo, so the next cycle resumes from them.

The four stages (looped)

1. RESEARCH   scan the source dirs → diff vs the live FedWiki → gap report
2. GATE       the First Person reads the dreams and ticks what to fill   ← the only human step
3. BUILD      builders write the approved canon into ~/.wiki (journal-versioned, [[linked]], hub backlinks)
4. SNAPSHOT   tools/snapshot.mjs → ./site → review on :3200
   ↺ loop until comfortable → push → guide.agentprivacy.ai
              (the live ~/.wiki stays the editable, tunnel-able carry copy)

Two layers of dream

Thematic dreams (flow/dream/): cross-cutting passes by site/topic — grimoire+research, tomes/cast/city, skills/personas, atlas/graph, library/narrative, and the relevance-curated wider-universe pass that triages the ~80 /mitch dirs into current · stale · irrelevant so the fan-out never dreams on cruft.

Per-directory dreams (<repo>/chronicles/DREAM-<date>.md): each current repo dreams about its own state + its link to the guide. This is the daily work-ledger. Template:

# Dream — <DirName> — <date>
## What this is
## Current state & open threads (within the dir)
## Guide coverage (projected vs missing)  | site | item | status | source |
## Suggestions (prioritized)              | suggestion | target | why | H/M/L |
## To get rolling tomorrow (ordered next actions)
## Notes & uncertainties

Discipline (the keeper's rules)

Relevance first. Never treat a stale/duplicate/version-named dir (v4…, nov11…, …copy, …fork) or a system folder as a gap. Triage, then verify each surviving candidate against the live sites before calling it a gap.
No duplicate information flows. Source canon → one guide projection. Fill what's missing; link, don't re-create, what already lives elsewhere (sibling hosts, other sites). Resolve collisions as cleanups, not new dupes.
The dreams are research input, not content to paste. They drive what canon to build; they stay as the working ledger.
Human gate is load-bearing. Nothing is built from a dream without the First Person ticking it; nothing is pushed/published without an explicit ask.
Honest framing carries. e.g. estimation is not attack; vendored work is not the author's — every dream preserves the source's honesty.

Run it

node flow/run.mjs audit              # RESEARCH → flow/gap-report.json
#   (read flow/GUIDE-DREAM-SUGGESTIONS.md — the GATE — and decide)
node flow/run.mjs build <site>       # BUILD the approved gaps into ~/.wiki
node flow/run.mjs snapshot           # SNAPSHOT → ./site → review on :3200
node flow/run.mjs cycle <site>       # audit → build → snapshot → audit, in one

The fan-out of per-directory dreams is driven from the relevance ledger; refresh it when the /mitch layout changes, then dream each current repo. See flow/DREAM-CYCLE.md for the full convention and flow/builders/ for the per-site builders (grimoire and research are the worked examples).

Lineage

Born 2026-06-29 building the guide.agentprivacy.ai static snapshot, when the question shifted from "patch this gap" to "keep the guide standing-rebound to the whole universe." The Chronicler writes the dreams; the Librarian federates them; the First Person decides.

---name: agentprivacy-wiki-dream-cycledescription: The standing research loop that keeps the static guide rebound to the source. Each relevant /mitch repo "dreams" about itself — a deep multi-lap pass that diffs the repo's canon against the live FedWiki, writes a standing `chronicles/DREAM-<date>.md` (its resumable work-ledger), and feeds a single confirm-able GATE document. The First Person ticks the GATE; builders write the approved canon into ~/.wiki; the snapshot publishes it. Activates when planning what to fill into the guide next, running a daily research cycle, fanning out per-directory gap analysis, or turning "what's missing" into ordered next actions. Four stages — RESEARCH → GATE → BUILD → SNAPSHOT — looped until comfortable to push. Authored by the Chronicler 🧙📖, kept by the Librarian 🗃️.license: Apache-2.0---# agentprivacy-wiki-dream-cycleThe **dream cycle** is how the agentprivacy guide stays rebound to the universeacross `/mitch`. Where `agentprivacy-wiki-resync` is the *per-turn* operation("I changed a repo → rebuild the wiki"), the dream cycle is the *discovery* layerthat runs *before* you know what to change: every current repo dreams aboutitself, surfaces its gaps, and proposes what to fill — and the First Persondecides.It is the Chronicler's loop (it *produces chronicles*) cataloged by the Librarian(the `wikis/` keeper). The dream files are standing ledgers that travel **with**each repo, so the next cycle resumes from them.## The four stages (looped)```1. RESEARCH scan the source dirs → diff vs the live FedWiki → gap report2. GATE the First Person reads the dreams and ticks what to fill ← the only human step3. BUILD builders write the approved canon into ~/.wiki (journal-versioned, [[linked]], hub backlinks)4. SNAPSHOT tools/snapshot.mjs → ./site → review on :3200 ↺ loop until comfortable → push → guide.agentprivacy.ai (the live ~/.wiki stays the editable, tunnel-able carry copy)```## Two layers of dream1. **Thematic dreams** (`flow/dream/`): cross-cutting passes by site/topic — grimoire+research, tomes/cast/city, skills/personas, atlas/graph, library/narrative, and the **relevance-curated** wider-universe pass that triages the ~80 `/mitch` dirs into *current · stale · irrelevant* so the fan-out never dreams on cruft.2. **Per-directory dreams** (`<repo>/chronicles/DREAM-<date>.md`): each current repo dreams about its own state + its link to the guide. This is the daily work-ledger. Template: ``` # Dream — <DirName> — <date> ## What this is ## Current state & open threads (within the dir) ## Guide coverage (projected vs missing) | site | item | status | source | ## Suggestions (prioritized) | suggestion | target | why | H/M/L | ## To get rolling tomorrow (ordered next actions) ## Notes & uncertainties ```## Discipline (the keeper's rules)- **Relevance first.** Never treat a stale/duplicate/version-named dir (`v4…`, `nov11…`, `…copy`, `…fork`) or a system folder as a gap. Triage, then verify each surviving candidate against the live sites before calling it a gap.- **No duplicate information flows.** Source canon → one guide projection. Fill what's *missing*; **link**, don't re-create, what already lives elsewhere (sibling hosts, other sites). Resolve collisions as cleanups, not new dupes.- **The dreams are research input, not content to paste.** They drive *what canon to build*; they stay as the working ledger.- **Human gate is load-bearing.** Nothing is built from a dream without the First Person ticking it; nothing is pushed/published without an explicit ask.- **Honest framing carries.** e.g. estimation is not attack; vendored work is not the author's — every dream preserves the source's honesty.## Run it```bashnode flow/run.mjs audit # RESEARCH → flow/gap-report.json# (read flow/GUIDE-DREAM-SUGGESTIONS.md — the GATE — and decide)node flow/run.mjs build <site> # BUILD the approved gaps into ~/.wikinode flow/run.mjs snapshot # SNAPSHOT → ./site → review on :3200node flow/run.mjs cycle <site> # audit → build → snapshot → audit, in one```The fan-out of per-directory dreams is driven from the relevance ledger; refreshit when the `/mitch` layout changes, then dream each current repo. See`flow/DREAM-CYCLE.md` for the full convention and `flow/builders/` for theper-site builders (grimoire and research are the worked examples).## LineageBorn 2026-06-29 building the `guide.agentprivacy.ai` static snapshot, when thequestion shifted from "patch this gap" to "keep the guide standing-rebound to thewhole universe." The Chronicler writes the dreams; the Librarian federates them;the First Person decides.

Frequently asked questions