Journal framework
The open Skill Me catalog — every hosted skill as a portable, MIT-licensed SKILL.md
npx -y skills add SkillMedev/skills --skill journal-frameworkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Designs a sustainable daily journaling practice - morning pages, gratitude, intention setting, evening reflection, and weekly review - matched to the user's goal, with copy-paste templates and a rotating prompt library. Use when someone asks "help me start journaling", "give me journal prompts", "I keep abandoning my journal", or "build me a morning pages routine". Do NOT use for building a general habit or streak system - use habit-builder instead; do NOT use for organizing notes and knowledge into a retrieval system - use second-brain instead; for structured end-of-week planning reviews, see weekly-review.
SKILL.md
7.0 KB, as published. Nobody here has run it
Journal Framework
Most journaling practices die within two weeks, and they die for predictable reasons: the ritual is too long, it has no anchor to an existing habit, and the prompts go stale. The fix is not more willpower - it is a practice sized to the user's actual life, with a tiny minimum, a fixed anchor, and prompts matched to what they want out of it.
Journaling supports general wellbeing but is not a substitute for therapy or mental-health care. If the user describes persistent distress, self-harm thoughts, or symptoms interfering with daily life, recommend a licensed professional before continuing.
Operating procedure
Order matters: the goal determines the prompts, and the time budget determines how many components survive - designing components before knowing the budget produces a routine that gets abandoned.
Step 1: Gather inputs
Collect, with defaults:
- Primary goal - pick one: clear mental clutter / build gratitude and mood / self-knowledge and patterns / decision quality / creative unblocking. Default: mental clutter.
- Honest daily time budget. Default: 10 minutes. If the user says 20+, treat it as a guess and design for 10 - beginners overestimate.
- Medium: paper or digital. Either works; pick whichever the user will actually open daily, and place it within arm's reach of where the habit lives (bedside, desk).
- Existing anchor habits (morning coffee, commute, lights-out) to attach the practice to.
- Past attempts and why they died - design directly against that failure.
Step 2: Size the practice to the budget
Assemble from these components, in priority order for the stated goal. Never schedule more than the budget holds; a 10-minute budget gets two components, not four.
- Morning pages (5-15 min): on waking, write freely without editing or judging. The goal is clearing mental clutter, not prose. Stuck prompts: "What is on my mind right now?", "What am I avoiding?", "What would make today a good day?"
- Gratitude (2-3 min): list 3 specific things. Specificity is the active ingredient - "my friend called to check in" beats "my friends." Vary items to avoid autopilot; occasionally note WHY each matters.
- Intention setting (1-2 min): one to three priorities, framed as outcomes or as how to show up ("Top priority: ___ / How I want to feel or act: ___").
- Evening reflection (5-10 min): what went well and my part in it; what drained me or went poorly and the lesson; one thing to do differently tomorrow.
Goal-to-component mapping: mental clutter → morning pages first. Mood/gratitude → gratitude + evening reflection. Self-knowledge → evening reflection + weekly review. Decision quality → evening reflection plus a decision log (pair with decision-making). Creative unblocking → morning pages at full 15 minutes.
Step 3: Install the friction rules
- Set a tiny minimum: two sentences counts as a completed day. The streak metric is "opened the journal," not "wrote something good."
- Anchor to an existing habit: "after I pour coffee" or "when I set my phone to charge at night" - a time of day is a weaker trigger than an existing action.
- Never aim for eloquence; consistency beats quality. Missing one day is noise; missing two in a row is the signal to shrink the practice, not to push harder.
- Protect privacy so writing stays honest: a passcode or encrypted notes app if digital, a physically private notebook if paper.
Step 4: Schedule the review loop
- Weekly (10-15 min): skim the week's entries; note recurring themes, wins, and stressors. This is where journaling turns from venting into self-knowledge.
- Monthly: identify patterns, celebrate progress, reset goals.
Step 5: Rotate prompts before they stale
Swap in one deeper prompt per week from the library: "What belief is no longer serving me?" / "When did I feel most alive recently?" / "What am I tolerating that I could change?" / "Who do I want to thank, and have I told them?" / "What would I do if I knew no one would judge it?" / "What is the story I keep telling myself about this problem?"
Worked artifact: weekly template
Copy-paste; daily block repeats 7 times.
WEEK OF [FILL: date] - goal this week: [FILL]
DAILY (minimum: 2 sentences anywhere below)
Morning - mind-clear: [FILL: unedited, 5 min]
Gratitude x3 (be specific):
1. [FILL] 2. [FILL] 3. [FILL]
Today's one priority: [FILL]
How I want to show up: [FILL]
Evening - went well / my part: [FILL]
drained me / lesson: [FILL]
do differently tomorrow: [FILL]
WEEKLY REVIEW (Sunday, 15 min)
Recurring theme I noticed: [FILL]
Biggest win: [FILL] Biggest stressor: [FILL]
Deep prompt of the week: [FILL: pick from library]
Keep / change for next week: [FILL]
Days completed: [FILL]/7 (2 sentences counts)
Bad daily entry: "Today was fine. Grateful for family, health, job." - autopilot, zero information, teaches nothing at review time. Good daily entry: "Snapped at Sam over the budget email; the real trigger was skipping lunch. Grateful Maya covered my 3pm without being asked. Tomorrow: eat before the standup." - specific, causal, and reviewable.
Deliverable
Produce a personalized journaling kit containing: the chosen components with their time budget and anchor habit, the filled weekly template, a 10+ prompt rotation library ordered for the user's goal, the tiny-minimum and two-day-miss rules stated explicitly, and the weekly review checklist.
Do NOT
- Do not prescribe every component to every user; an over-stuffed ritual is the leading cause of abandonment.
- Do not accept "family, health, job" gratitude entries as the pattern - specificity is what produces the mood effect.
- Do not frame missed days as failure; the recovery rule (shrink after two misses) matters more than the streak.
- Do not turn the journal into a task manager or note archive - route productivity systems to gtd-system and knowledge capture to second-brain.
- Do not continue coaching past signs of clinical distress; recommend professional help.
Quality bar
- Total daily time fits inside the user's stated budget with margin.
- Every component traces to the user's stated goal, not to a generic ideal routine.
- The template is usable as-is: every field is either pre-filled or marked [FILL].
- A tiny minimum, an anchor habit, and a two-day-miss recovery rule are all explicitly stated.
- A weekly review is scheduled with a specific day and duration.
Gives 0 of the 12 instructions most note taking skills give
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 35 of 686, across 11 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 10 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- gather primary goal, time budget, medium, anchors and past failures
- treat any time budget over 20 minutes as 10 minutes
- size the selected components to fit the daily time budget
- map components to the user's stated primary goal
- set a daily two-sentence minimum
- anchor the practice to an existing daily action
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.