gratitude
Skill1 starsChanged 7 months agoMITView on GitHub
Three specific, person-linked gratitude items per day. Not "I'm grateful for my family." "I'm grateful that Maya showed me the bird outside the window at 7:02 AM." Daily, 90 seconds.
In this repository34 other files it gives its agents.
- accountability-mirrorSkill
- annual-physicalSkill
- bills-and-subsSkill
- brotherhoodSkill
- conscious-spendingSkill
- date-nightSkill
- decision-journalSkill
- discomfort-doseSkill
- emotion-coachSkill
- enough-checkSkill
- errand-batchSkill
- evening-examenSkill
- father-reviewSkill
- friend-reach-outSkill
- hard-conversationSkill
- home-maintenanceSkill
- kid-oneononeSkill
- love-map-refreshSkill
- mentor-touchSkill
- money-dateSkill
- morning-resetSkill
- parent-checkinSkill
- partner-checkinSkill
- partner-reviewSkill
- repairSkill
- resetSkill
- screwupSkill
- shutdown-ritualSkill
- sleep-protocolSkill
- training-planSkill
- values-checkSkill
- virtue-reviewSkill
- weekly-reviewSkill
- weekly-serviceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Not just "Elena made me coffee." But also "...which lets me skip 5 minutes of friction every morning when I'm already stressed about the …
- Distinctive: line 30
Every day, three items.
- Distinctive: line 48
Write a short note.
- Distinctive: line 89
If the practice feels impossible, drop to ONE item, for any person or thing, and that is plenty.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/gratitude
Gratitude practice works. The research is consistent across decades. But most of what people call a gratitude practice is the cheap version, and the cheap version does very little.
The cheap version: "I'm grateful for my family, my health, and my job." Fine. Does basically nothing neurologically after the first few weeks, because it is vague and repetitive.
The effective version has three features.
The three rules
1. Specific
Not "my partner." Name the specific thing they did today or this week. Specific enough that another person reading it would be able to picture the moment.
2. Person-linked
Not "I'm grateful for coffee." "I'm grateful that Elena makes coffee for me most mornings even though she doesn't drink it." Attached to a person whose action made the good thing possible.
3. Why-linked
Not just "Elena made me coffee." But also "...which lets me skip 5 minutes of friction every morning when I'm already stressed about the day." What about the thing matters to you, and why.
Daily form
Every day, three items.
Template:
1. Today I'm grateful that <specific thing> that <person> did, because <why it mattered to me>.
2. Today I'm grateful that <specific thing> that <person> did, because <why it mattered to me>.
3. Today I'm grateful that <specific thing> that <person> did, because <why it mattered to me>.Some of the three can be about yourself (you did something hard, you were kind to yourself, you tried). Some can be about circumstances or nature. But at least ONE per day should be person-linked to someone in your life.
The extra step (weekly)
Once a week, pick one item from the week's gratitude log and TELL THE PERSON.
- Text them the specific thing, with the why.
- Mention it in person.
- Write a short note.
This is the part that transforms a private practice into a relational one. Told gratitude is connection. Untold gratitude is just mood management.
Examples
Low-value (don't do this)
- "Grateful for my family."
- "Grateful for my health."
- "Grateful for my job."
Medium-value (better)
- "Grateful my wife made dinner tonight."
- "Grateful my team shipped the release."
- "Grateful the weather was nice."
High-value (do this)
- "Grateful Elena made dinner tonight even though she had a harder day than I did, which freed me to have a real conversation with Lucas about his friend problem instead of managing the kitchen."
- "Grateful Subbu pushed back on my first draft of the investor memo, because it saved me from sending a weaker version and hurting our credibility with that fund."
- "Grateful for the long walk at sunset because I noticed how much I'd been stuck in my head this week and needed the 45 minutes outside."
Output
Append to ~/adulting-data/journal/gratitude-YYYY-MM.md:
## <date>
1. <specific, person-linked, why>
2. <specific, person-linked, why>
3. <specific, person-linked, why>
(weekly) Told <name> about <item>: <Y/N, when>The honest caveat
If you have a streak of hard days or are moving through grief, gratitude practice can feel false. It isn't. You can be both heartbroken and grateful that someone brought you coffee. Naming the small good things does not deny the big hard thing. It keeps you from drowning in it.
If the practice feels impossible, drop to ONE item, for any person or thing, and that is plenty.
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.

