agentleFS
noahcostakesnoahcostakes/claudebrain-template/.claude/skills/dream/SKILL.md

dream

Skill0 starsChanged 5 months agoMITView on GitHub

Run the Dream Mode auto-fix pass on demand (catch-up). Pulls the vault, creates today's daily note, auto-applies deterministic hygiene fixes, then resolves the remaining findings with judgment (dangling links, frontmatter, tags, dead files), writes the Morning Brief's Yesterday + Revisit parts, flips the manifest, self-checks, commits, and pushes. Use when the session-start status says last night's dream didn't run.

  • Commits and pushes

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, resume and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 3 projects that use this

  • MicrosoftSkill

    init

    Also in 4 projects that use this

  • Hugging FaceSkill

    simplify

    Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

    Also in 3 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 2 are distinctive, and 16 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 16

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    If --dry-run, report what it printed and stop — do not run Layer B.

    line 37
  2. Very specific:

    Never edit _meta/profile.md or _meta/memory.md.

    line 53
  3. Very specific:

    Never hard-delete a file — archive to 40-archive/ instead.

    line 55
  4. Very specific:

    Flow triage is proposals only: Never move an inbox item out of 00-inbox/, and never archive a note.

    line 61
  5. Very specific:

    Connections are proposals only: Never add a [[wikilink]] to any note, never create a MOC / map note, and never merge, rewrite, or delete a …

    line 67
  6. Very specific:

    Flip hygiene-b in the manifest: After draining the hygiene queue (step 3), edit the > 🌙 manifest v1 | line in today's ## 🌙 Overnight …

    line 78
  7. Very specific:

    Leave Stuck: and Deadlines: (Layer-A facts) untouched.

    line 93
  8. Very specific:

    Flip brief-b in the manifest: After writing the brief parts, edit the > 🌙 manifest v1 | line: change brief-b:pending → brief-b:ok.

    line 95
  9. Very specific:

    active→shipped: when the project says it is delivered/closed/"effectively complete" (e.g.

    line 103
  10. Distinctive:

    active→parked: when an unpark trigger is plainly dead or the line says it is parked.

    line 105
  11. Very specific:

    If nothing qualifies, write - Proposed: — none.

    line 108
  12. Very specific:

    Propose only — never move the file out of 00-inbox/: Leave the - Stale: lines (Layer A's computed orphan facts) untouched.

    line 121
  13. Distinctive:

    If an entry point already exists or it's not worth it, delete the line.

    line 141
  14. Very specific:

    If a stage is not done, set it back to pending so the morning /daily can finish it.

    line 164
  15. Very specific:

    Verify + commit: Run python .claude/hooks/validate_note.py --scan.

    line 167
  16. Very specific:

    If there's no remote configured, dream.py already degrades to commit-only — just commit.

    line 170
  17. Very specific:

    All deterministic file/git work happens in dream.py.

    line 178
  18. Very specific:

    If dream.py exits non-zero, report and stop — do not retry blindly.

    line 180

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dream Skill (autonomous auto-fix)

What this does

Runs the Dream Mode auto-fix pass. An optional nightly scheduler can run /dream autonomously while you sleep (see docs/dream-autonomous-setup.md); otherwise run it manually as a catch-up any time — this skill is the same entrypoint either way, and nothing about the scheduler is required. Two layers:

  • Layer A — dream.py (deterministic): pull + self-re-exec, create today's note (carry-forward + week-focus), apply the no-judgment fixes (markdown→wikilink, missing date:), write the ## 🌙 Overnight section (including the manifest header and the ### Morning Brief block with Yesterday:/Revisit: placeholders and Layer-A facts for Stuck:/Deadlines:), commit + push.
  • Layer B — you (judgment): drain the ### Needs your OK worklist with judgment, honoring the floors; write the Morning Brief's Yesterday: recap and Revisit: pick; propose orient.md section moves into the ### orient.md Proposed: line (never editing orient.md itself); propose a destination for each ### Flow triage inbox item (never moving the file); curate the ### Connections feed into worded Link / MOC / Merge proposals (never adding a link, creating a MOC, or merging a note); flip hygiene-b, brief-b, orient-b, flow-b, and connect-b in the manifest; self-check; commit + push.

Arguments

  • /dream — run the pass for today.
  • /dream --dry-run — print what Layer A would do, change nothing (skip Layer B).
  • /dream --force — re-run even if today already has a ## 🌙 Overnight section.

Steps

  1. Run Layer A via Bash: python .claude/hooks/dream.py (append --dry-run / --force verbatim if passed). If it exits non-zero (pull failed), report and stop. If --dry-run, report what it printed and stop — do not run Layer B.
  2. Read the ### Needs your OK worklist from today's note (50-daily/YYYY/MM/YYYY-MM-DD.md). If it is empty or — none, skip to step 4.
  3. Resolve each finding with judgment, then move it from ### Needs your OK to ### Auto-applied as a one-line done-fact (e.g. - created stub: <path>). Policy:

    FindingResolution
    Missing type/status/tags or no frontmatterInfer from path + content (10-projects/…→type: project, 50-daily/…→type: daily, etc.); add minimal valid frontmatter using approved tags from _meta/tags.md.
    Dangling [[wikilink]]Judge: (a) path-like planned sub-page under a real folder → create a proper stub note with frontmatter + one backlink; (b) dead reference (e.g. a declined project) → remove the link or make it plain text; (c) wrong path to an existing note → repoint. Never stub a bare concept link (e.g. [[SomeConcept]]) — repoint or unlink it.
    Unapproved tagRemap to the nearest approved tag in _meta/tags.md; if genuinely new + useful, add it to _meta/tags.md and note the vocabulary change loudly in the log.
    Whole file dead/orphaned (e.g. stale _audit-*.md)Move to 40-archive/ (never delete).
  4. Floors (never cross):
    • Never edit _meta/profile.md or _meta/memory.md. Leave any such finding in ### Needs your OK and note it is floored.
    • Never hard-delete a file — archive to 40-archive/ instead.
    • _meta/orient.md: Layer A (dream.py) already auto-applied the deterministic heat 🔥/🌡️ + "last touched" refresh in the Active projects block — do not redo or hand-edit those tokens. You only propose section moves (next step), written into the daily note's ### orient.md Proposed: line — never edit orient.md itself, and never touch its ## This week's focus section (that is /weekly's).
    • Flow triage is proposals only. Never move an inbox item out of 00-inbox/, and never archive a note. You only propose a destination for each inbox item (next step) and the stale/orphan list is Layer A's computed facts — leave the - Stale: lines exactly as written. The actual move/archive happens only when the user OKs it (or via the future /process-inbox). Archive always means move to 40-archive/, never delete.
    • Connections are proposals only. Never add a [[wikilink]] to any note, never create a MOC / map note, and never merge, rewrite, or delete a note. The ### Connections feed is Layer A's read-only computation from the optional graphify-out/ graph; you only curate it in place (fill each candidate's _(… pending …)_ placeholder, drop noise lines) inside the daily note's dream section. Leave the > staleness banner exactly as written. Applying an OK'd connection (adding the link, creating the MOC, merging) happens later, by hand — never in this pass. Do not run /graphify — graph refresh is manual and the user's call. (If graphify-out/ is absent, the ### Connections block is - — none — nothing to curate.)
    • The validate_note hook validates each edit live; if it rejects one, fix and retry.
  5. Flip hygiene-b in the manifest. After draining the hygiene queue (step 3), edit the > 🌙 manifest v1 | line in today's ## 🌙 Overnight section: change hygiene-b:pending → hygiene-b:ok. Edit only that token; leave the rest of the line intact. If the queue had floored items you could not resolve, leave the token pending — never mark ok a stage you did not actually complete.
  6. Write the Morning Brief (Layer-B parts). In today's ### Morning Brief block, replace the two _(pending …)_ placeholders:
    • Yesterday: 2–3 lines summarizing the most recent prior daily note — pull from its ## Wins, ## Notes / log, and checked - [x] tasks. Compression, not analysis. If there's nothing to pull, write Yesterday: — quiet day.
    • Revisit: pick ONE older note worth a second look (an orphan, a parked project, or a note untouched for weeks that connects to current focus) and ONE open question/prompt seeded from recent themes. One line: Revisit: [[note]] — why · Prompt: <question>. Leave Stuck: and Deadlines: (Layer-A facts) untouched.
  7. Flip brief-b in the manifest. After writing the brief parts, edit the > 🌙 manifest v1 | line: change brief-b:pending → brief-b:ok. Edit only that token. If you could not fill the placeholders, leave the token pending.
  8. Propose orient.md section moves (Layer-B judgment). In today's ### orient.md block, replace the - Proposed: _(pending …)_ placeholder with section-move proposals — as plain prose / - bullets, never - [ ] checkboxes. Read the Active-projects lines and propose a move only when the line's own text makes it clear:
    • active→shipped when the project says it is delivered/closed/"effectively complete" (e.g. "Phases 3–4 done … confirm and move to shipped").
    • active→parked when an unpark trigger is plainly dead or the line says it is parked. Name the project and give a one-line reason, e.g. Proposed: move **Inbox cleanup** active→shipped — line says "effectively complete; confirm and move to shipped". If nothing qualifies, write - Proposed: — none. Propose only — never move the section, never edit orient.md. The user (or a later /daily) applies an OK'd move by hand. Then flip orient-b in the manifest: change orient-b:pending → orient-b:ok (edit only that token). If you could not evaluate the moves, leave it pending.
  9. Triage the inbox (Layer-B judgment). In today's ### Flow triage block, for each - Inbox: \<path>` → (pending …)line, **read that inbox note** and replace the(pending …)placeholder with ONE proposed destination + a one-line reason — as **plain prose, never a- [ ]checkbox**. Destinations:10-projects/<slug>/(active, time-bounded work),20-areas/<area>/(an ongoing responsibility),30-resources/(reference material the user didn't write), or40-archive/(already-acted-on, dead, or superseded — e.g. an idea already promoted to a workspace). Example:- Inbox: `00-inbox/2026-06-19-some-idea.md` → 40-archive/ — already promoted to a workspace (capture is done).**Propose only — never move the file out of00-inbox/.** Leave the - Stale:lines (Layer A's computed orphan facts) untouched. Then **flipflow-bin the manifest:** changeflow-b:pending→flow-b:ok(edit only that token). If there were no inbox items, the block has none to fill — still flipflow-b:ok. If you could not evaluate the inbox items, leave it pending`.
  10. Curate the Connections feed (Layer-B judgment). In today's ### Connections block, turn Layer A's candidate feed into a bounded, worded set of proposals — as plain - bullets, never - [ ] checkboxes. For each candidate line, either fill its _(… pending …)_ placeholder with the judgment part, or delete the line if it's noise (a pair that's already effectively linked, a community that already has an entry point, two notes that shouldn't merge). Keep it tight — a handful of high-value proposals beats the raw feed.
    • Link - Link: \A` ↔ `B` — … → (theme: pending …): replace the placeholder with the shared **theme** in a few words, e.g. - Link: `20-areas/<area>/log.md` ↔ `20-areas/<area>/README.md` — both track the same plan; don't reference each other.`
    • MOC - MOC: community "X" (N notes) … → _(propose [[…]] map note?: pending …)_: decide whether the cluster deserves an entry point and, if so, propose a stub map note name to confirm (never create it), e.g. - MOC: cluster "<Topic>" (10 notes) is big enough to gather — propose a [[<topic>-moc]] map note (stub to confirm). If an entry point already exists or it's not worth it, delete the line.
    • Merge - Merge: \C` ~ `D` — … → (survivor: pending …): if they really are duplicates, name the suggested **survivor**; otherwise delete the line, e.g. - Merge: `_audit-2026-06-03-1106.md` overlaps `_audit-followups-2026-05-28.md` — candidate duplicate; suggested survivor the newer audit.(Distinct dated artifacts that merely share a topic are **not** a merge — delete.) **Propose only — never add the wikilink, never create the MOC note, never merge/rewrite a note.** Leave the> staleness banner untouched. If the block is- — none(no graph or no candidates), there's nothing to curate. Then **flipconnect-bin the manifest:** changeconnect-b:pending→connect-b:ok(edit only that token). If the feed was empty /— none, still flip connect-b:ok. If you could not evaluate the candidates, leave it pending`.
  11. Self-check before committing (verify, don't assume). Confirm each stage you marked ok is actually done:
  • hygiene-b:ok → queue items resolved (or honestly left floored in ### Needs your OK)
  • brief-b:ok → both _(pending …)_ placeholders are gone from ### Morning Brief
  • orient-b:ok → the ### orient.md Proposed: placeholder is gone (replaced with real move proposals or — none).
  • flow-b:ok → every ### Flow triage - Inbox: line's _(pending …)_ placeholder is gone (replaced with a destination + reason), or there were no inbox items.
  • connect-b:ok → every ### Connections candidate line's _(… pending …)_ placeholder is gone (filled with a theme/survivor/map-note decision or the line was deleted), or the block was - — none. If a stage is not done, set it back to pending so the morning /daily can finish it. Never mark a stage ok you didn't actually do.
  1. Verify + commit. Run python .claude/hooks/validate_note.py --scan. The findings should be zero except floored items. Then commit + push via Bash: git add -A && git commit -m "dream <date>: Layer-B fixes + brief" && git push. If there's no remote configured, dream.py already degrades to commit-only — just commit. If the commit/push fails, report it and continue — never block on git.
  2. Report in a few lines: how many findings Layer A auto-applied, how many you resolved in Layer B, what (if anything) remains floored, whether the Morning Brief was written, and whether the final scan was clean.

Rules

  • All deterministic file/git work happens in dream.py; don't duplicate it.
  • Layer B uses judgment but stays inside the floors above; every change is git-reversible.
  • If dream.py exits non-zero, report and stop — do not retry blindly.
  • Manifest token names must match exactly: hygiene-b, brief-b, orient-b, flow-b, connect-b (case-sensitive).
  • The manifest line format is > 🌙 manifest v1 | ... — edit only the specific tokens you completed; leave all other tokens intact.
  • The Connections feed depends on the optional graphify-out/ directory; if it's absent, /dream degrades gracefully (Connections = — none) — it never errors on a missing graph.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.