journal
Skill2 starsChanged 8 months agoMITView on GitHub
Quick journal entries with mood detection, tagged and linked to your daily page
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.
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
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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- checkinSkill
- code-reviewSkill
- eod-reviewSkill
- meeting-prepSkill
- morning-kickoffSkill
- plantsSkill
- read-laterSkill
- recipeSkill
- researchSkill
- standupSkill
- todoSkill
- tripSkill
- watchlistSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
If the entry is just a trigger phrase with no content (e.g., "journal:"), ask: "What's on your mind?"
- Distinctive: line 49
If mood is ambiguous, default to Neutral
- Distinctive: line 50
Do not ask the user to confirm the mood — just detect it quietly
- Very specific: line 66
Search {{notes}} for today's daily page.
- Distinctive: line 68
If it exists, the journal entry will be linked to it
- Distinctive: line 69
If it doesn't exist, create the entry standalone (don't create a daily page just for a journal entry)
- Very specific: line 73
Write the entry to {{notes}} with this structure:
- Distinctive: line 83
If today's daily page exists, also add a brief reference to the journal entry in the daily page under a "Journal" section
- Distinctive: line 84
Keep the reference minimal: just the mood and first line of the entry
- Distinctive: line 101
Ask follow-up questions (unless entry was empty)
- Distinctive: line 110
If the user writes multiple sentences, keep them as one entry — don't split into separate entries
- Very specific: line 112
If the {{notes}} integration is not configured, fall back to writing a local markdown file at ~/.ai-workflow/journal/[date].md
“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
Journal
Trigger Phrases
- "journal:"
- "reflect:"
- "today I"
- "feeling [emotion]"
- "grateful for"
- "on my mind:"
Inputs
The user provides a journal entry inline with the trigger phrase. The entry can be:
- A sentence or two: "journal: Had a breakthrough on the caching layer today"
- A mood expression: "feeling overwhelmed — too many threads open"
- A gratitude note: "grateful for Sarah's help debugging that race condition"
- A reflection: "reflect: I notice I default to building instead of asking for help"
Workflow
Step 1: Parse the Entry
Extract the journal content from the user's message.
- Strip the trigger prefix ("journal:", "reflect:", etc.)
- Preserve the user's exact words — do not rewrite, summarize, or polish
- If the entry is just a trigger phrase with no content (e.g., "journal:"), ask: "What's on your mind?"
Step 2: Detect Mood
Analyze the entry for mood signals. Assign one primary mood:
| Mood | Signals |
| Energized | excitement, momentum, breakthrough, shipped, crushed it |
| Focused | deep work, flow state, locked in, making progress |
| Neutral | status updates, factual observations, no strong emotion |
| Overwhelmed | too much, scattered, can't focus, drowning, behind |
| Tired | drained, exhausted, low energy, long day, need a break |
| Frustrated | stuck, blocked, annoyed, broken, doesn't work, ugh |
| Grateful | thankful, grateful, appreciate, lucky, helped by |
- If mood is ambiguous, default to Neutral
- Do not ask the user to confirm the mood — just detect it quietly
Step 3: Detect Tags
Assign 1-3 tags based on content:
| Tag | Signals |
| Work | code, meeting, ticket, PR, deploy, team, project |
| Personal | family, health, hobby, weekend, home, friends |
| Reflection | I notice, pattern, thinking about, wondering, realized |
| Gratitude | grateful, thankful, appreciate, helped by |
| Learning | learned, TIL, figured out, discovery, insight |
Step 4: Check for Today's Daily Page
Search {{notes}} for today's daily page.
- If it exists, the journal entry will be linked to it
- If it doesn't exist, create the entry standalone (don't create a daily page just for a journal entry)
Step 5: Create the Journal Entry
Write the entry to {{notes}} with this structure:
Date: [today's date]
Mood: [detected mood]
Tags: [detected tags]
[User's journal entry, exactly as written]- If today's daily page exists, also add a brief reference to the journal entry in the daily page under a "Journal" section
- Keep the reference minimal: just the mood and first line of the entry
Step 6: Confirm
Respond with a single line confirming the save:
Logged — [Mood] [Tags]. [brief acknowledgment]Examples of confirmations:
- "Logged — Energized, Work. Nice breakthrough."
- "Logged — Overwhelmed, Work. That's a lot of threads."
- "Logged — Grateful, Personal. Noted."
Do NOT:
- Offer advice or coaching
- Ask follow-up questions (unless entry was empty)
- Restate the journal entry back to the user
- Add motivational commentary
The confirmation should feel like a nod, not a conversation.
Notes
- Journal entries are private by default. Never post them to
{{chat}}or any shared space - If the user writes multiple sentences, keep them as one entry — don't split into separate entries
- Mood detection is a convenience, not a judgment. Keep it neutral in tone
- If the
{{notes}}integration is not configured, fall back to writing a local markdown file at~/.ai-workflow/journal/[date].md
Examples
User: "journal: Had a breakthrough on the caching layer. The problem was stale invalidation keys — once I switched to content-based hashing, everything clicked." Mood: Energized Tags: Work, Learning Response: "Logged — Energized, Work + Learning. Good solve."
User: "feeling overwhelmed — three PRs in review, two meetings back to back, and a production alert I haven't triaged yet" Mood: Overwhelmed Tags: Work Response: "Logged — Overwhelmed, Work. Full plate today."
User: "grateful for Jordan pairing with me on that flaky test. Would've taken me hours solo." Mood: Grateful Tags: Gratitude, Work Response: "Logged — Grateful, Work. Noted."
User: "reflect: I keep volunteering for tasks outside my sprint scope. Need to get better at saying 'not this sprint' without guilt." Mood: Neutral Tags: Reflection, Work Response: "Logged — Reflection, Work."
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.

