agentleFS
mpaaratingmpaarating/ai-workflow-kit/skills/journal/SKILL.md

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

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 CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

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
  1. Distinctive:

    If the entry is just a trigger phrase with no content (e.g., "journal:"), ask: "What's on your mind?"

    line 33
  2. Distinctive:

    If mood is ambiguous, default to Neutral

    line 49
  3. Distinctive:

    Do not ask the user to confirm the mood — just detect it quietly

    line 50
  4. Very specific:

    Search {{notes}} for today's daily page.

    line 66
  5. Distinctive:

    If it exists, the journal entry will be linked to it

    line 68
  6. Distinctive:

    If it doesn't exist, create the entry standalone (don't create a daily page just for a journal entry)

    line 69
  7. Very specific:

    Write the entry to {{notes}} with this structure:

    line 73
  8. Distinctive:

    If today's daily page exists, also add a brief reference to the journal entry in the daily page under a "Journal" section

    line 83
  9. Distinctive:

    Keep the reference minimal: just the mood and first line of the entry

    line 84
  10. Distinctive:

    Ask follow-up questions (unless entry was empty)

    line 101
  11. Distinctive:

    If the user writes multiple sentences, keep them as one entry — don't split into separate entries

    line 110
  12. Very specific:

    If the {{notes}} integration is not configured, fall back to writing a local markdown file at ~/.ai-workflow/journal/[date].md

    line 112

“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.

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

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:

MoodSignals
Energizedexcitement, momentum, breakthrough, shipped, crushed it
Focuseddeep work, flow state, locked in, making progress
Neutralstatus updates, factual observations, no strong emotion
Overwhelmedtoo much, scattered, can't focus, drowning, behind
Tireddrained, exhausted, low energy, long day, need a break
Frustratedstuck, blocked, annoyed, broken, doesn't work, ugh
Gratefulthankful, 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:

TagSignals
Workcode, meeting, ticket, PR, deploy, team, project
Personalfamily, health, hobby, weekend, home, friends
ReflectionI notice, pattern, thinking about, wondering, realized
Gratitudegrateful, thankful, appreciate, helped by
Learninglearned, 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."

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.