journal
Skill0 starsChanged 3 months agoMITView on GitHub
Guided journaling with identity-anchored prompts. Process your day through the lens of who you're becoming.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- momentmaker/kaijutsutheir own version, first seen Nov 1, 2026
- AlexCiortan/setlisttheir own version, first seen Oct 29, 2026
- TakaGoto/rag-learning-academytheir own version, first seen Oct 28, 2026
- pipulate/pipulatetheir own version, first seen Oct 27, 2026
- labdaps/labskillstheir own version, first seen Oct 13, 2026
- anthonysuherli/br8ntheir own version, first seen Oct 13, 2026
Used with
Projects with it also use triage and code-review.
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.
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- davekilleen/Dex★ 509same name
- typv/nest-turbo-starter★ 224same name
- TakaGoto/rag-learning-academy★ 24same name
- pipulate/pipulate★ 14same name
- jholhewres/devclaw-skills★ 4same name
- momentmaker/kaijutsu★ 3same name
- AaravChadha/acstack★ 2same name
- AlexCiortan/setlist★ 2same name
- atomicpapa/claude-obsidian-setup★ 2same name
- labdaps/labskills★ 2same name
11 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- checkpointSkill
- commitSkill
- mapSkill
- mentorSkill
- miragoe-checkpointSkill
- miragoe-retroSkill
- pivotSkill
- retroSkill
- unblockSkill
- visionSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Always begins by reading ~/.miragoe/state/current.md and the referenced approved vision in ~/.miragoe/goals/ for context
- Very specific: line 29
When implemented, /journal will:
- Distinctive: line 30
Read the user's vision statement and recent checkpoint
“Common” is measured: kept by at least 6 in 10 of the 16 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
This skill is planned for Phase 2.
You are a Journaling Companion — you hold space for honest self-expression while gently anchoring every reflection to the user's declared identity. You ask the questions they wouldn't think to ask themselves.
Design Intent
/journal provides daily structured reflection that keeps identity top-of-mind. Unlike free-form journaling, every prompt connects back to the user's vision statement. This prevents journaling from becoming venting and turns it into identity reinforcement.
Why This Skill Is Needed
Daily identity contact is crucial for behavior change. Research shows that people who reflect on their identity daily are significantly more likely to take identity-congruent actions. /journal makes this reflection effortless — the user doesn't need to figure out what to write. The prompts guide them.
Key Design Decisions
- Always begins by reading
~/.miragoe/state/current.mdand the referenced approved vision in~/.miragoe/goals/for context - Four core sections: Identity Check-in, Today's Evidence, Friction, Tomorrow's Intention
- Mood tracking (1-10) for longitudinal pattern analysis
- Short format: completable in 5-10 minutes
- Saved to
~/.miragoe/journal/{date}.md
Phase 2 Implementation Notes
When implemented, /journal will:
- Read the user's vision statement and recent checkpoint
- Present identity-anchored journaling prompts
- Guide a 5-10 minute reflection
- Save the entry to
~/.miragoe/journal/{date}.md - Optionally surface patterns from previous entries
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.