dream
Skill0 starsChanged 5 days agoMITView on GitHub
Audit recent cross-repo sessions to propose additions, corrections, demotions, and prunes across instructions and skills. Use for /dream, nightly session reviews, or consolidating lessons across recent chats.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- Jewgah/claude-code-skillstheir own version, first seen Nov 16, 2026
- borkweb/skillstheir own version, first seen Nov 15, 2026
- srinator22/agent-kerneltheir own version, first seen Nov 15, 2026
- fjwood69/moritheir own version, first seen Nov 10, 2026
- srinator22/New-Projecttheir own version, first seen Nov 8, 2026
- Melvynx/ai-maxxing-skillstheir own version, first seen Nov 8, 2026
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.
JaimeGBASkillingest
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
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 3 projects that use this
MicrosoftSkillinit
Also in 4 projects that use this
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 3 projects that use this
SentrySkilldeslop
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
AnthropicSkillstart
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
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- Noizefield/audio-plugin-coder★ 334same name
- grandamenium/dream-skill★ 136same name
- sneg55/agent-starter★ 76same name
- oprogramadorreal/optimus-claude★ 75same name
- tranhieutt/software_development_department★ 71same name
- Melvynx/ai-maxxing-skills★ 46same name
- maxvaega/awesome-skills★ 40same name
- seldonframe/seldonframe★ 40same name
- hyperb1iss/hyperskills★ 36same name
- fjwood69/mori★ 32same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- councilSkill
- find-red-flagsSkill
- formatting-pull-requestSkill
- full-sendSkill
- full-stopSkill
- leaving-pr-commentsSkill
- modernizeSkill
- sol-loopSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the time window from the prompt, or default to the last 24 hours.
- Very specific: line 15
Check recent dream sessions and child sessions so you skip proposals the user already archived or declined.
- Distinctive: line 16
If no substantive sessions remain, report that nothing needed review and stop.
- Very specific: line 21
Read small groups (15 total turns or fewer) directly.
- Very specific: line 30
Read ~/.copilot/dream-watchlist.md (if present) and each candidate target file before drafting proposals:
- Very specific: line 39
Update ~/.copilot/dream-watchlist.md per references/rubric.md to prune expired entries, remove promoted matches, and record validated …
- Very specific: line 42
Do not edit ~/.copilot/copilot-instructions.md or ~/.agents/skills/ before explicit user approval.
- Very specific: line 43
Call list_sessions_and_chats and post a digest covering child session links (app_url when present), any ~/.copilot diff, watchlist changes, …
- Very specific: line 47
When the user approves a ~/.copilot/copilot-instructions.md or ~/.agents/skills/ diff in chat, apply that edit in place.
“Common” is measured: kept by at least 6 in 10 of the 43 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.
Files
Dream
Consolidate lessons from recent sessions into reviewable updates across user and repository instructions and skills.
1. Collect sessions
- Use the time window from the prompt, or default to the last 24 hours.
- Collect candidate sessions from
session_store_sql(cloudandlocal) andlist_sessions_and_chatsusing references/rubric.md. - Exclude the current session, previous
dreamruns, no-op automations, and single-turn lookups. - Check recent
dreamsessions and child sessions so you skip proposals the user already archived or declined. - If no substantive sessions remain, report that nothing needed review and stop.
2. Mine transcripts
- Group sessions by repository or
cwdand map configured repositories withlist_repositories. - Read small groups (15 total turns or fewer) directly; for larger groups, spawn one read-only
general-purposesubagent per repository group so it can callsession_store_sql. - Extract four signal types with session IDs and turn numbers:
- User corrections and repeated agent mistakes.
- Commands, flags, workflows, or preferences that succeeded after trial and error.
- Existing instructions or skills that misled the agent, drifted from the code, or went ignored.
- Visible skills that failed to trigger or manual steps that repeated across turns.
3. Audit targets and filter
- Read
~/.copilot/dream-watchlist.md(if present) and each candidate target file before drafting proposals:- User instructions:
~/.copilot/copilot-instructions.md. - User skills:
~/.agents/skills/andagent-skills(main_repo_pathfromlist_repositories, or localmainwhen running in anagent-skillsworktree). - Repository instructions:
<repo>/AGENTS.mdand<repo>/.github/copilot-instructions.md. - Repository skills:
<repo>/.github/skills/and<repo>/.agents/skills/.
- User instructions:
- Match signals against
~/.copilot/dream-watchlist.md, then route and filter candidates with references/rubric.md.
4. Stage proposals
- Update
~/.copilot/dream-watchlist.mdper references/rubric.md to prune expired entries, remove promoted matches, and record validated single-session candidates. - For git-backed targets (each affected repository and
agent-skills), spawn one child worktree session per repository withcreate_sessionusing references/rubric.md. - End your turn while child sessions run; when idle notifications arrive, archive any child with zero changes and keep every child with a diff.
- Do not edit
~/.copilot/copilot-instructions.mdor~/.agents/skills/before explicit user approval; render unifieddiffblocks for them in chat. - Call
list_sessions_and_chatsand post a digest covering child session links (app_urlwhen present), any~/.copilotdiff, watchlist changes, and structural check candidates.
5. Apply non-git proposals
- When the user approves a
~/.copilot/copilot-instructions.mdor~/.agents/skills/diff in chat, apply that edit in place.
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
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.

