brotherhood
Skill1 starsChanged 7 months agoMITView on GitHub
Close male friendship maintenance. The monthly men's dinner, the quarterly trip, the 3am list, the weekly one-sentence check-in. Because male friendship atrophies after 30 unless engineered.
In this repository34 other files it gives its agents.
- accountability-mirrorSkill
- annual-physicalSkill
- bills-and-subsSkill
- conscious-spendingSkill
- date-nightSkill
- decision-journalSkill
- discomfort-doseSkill
- emotion-coachSkill
- enough-checkSkill
- errand-batchSkill
- evening-examenSkill
- father-reviewSkill
- friend-reach-outSkill
- gratitudeSkill
- 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
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Ask the user: "Name the 3 men you would call at 3 a.m.
- Distinctive: line 20
If they have fewer than 3, that is the work of the next year.
- Distinctive: line 35
No agenda required. Conversation is the thing.
- Distinctive: line 37
If this does not exist yet, help the user:
- Distinctive: line 55
Every week, text one friend (rotate through Tier 1) one sentence:
- Distinctive: line 65
Ask the user, once a quarter:
- Distinctive: line 68
When was the last time I saw [each Tier 1] in person?
- Very specific: line 71
If any of those surface a name, message them this week.
≈ “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
/brotherhood
(This skill is framed around men's friendships because that is a documented crisis with a documented fix. The structure works for any tight-knit group of same-gender or mixed friends.)
The data is consistent across studies: adult male friendship declines sharply after age 30 and continues to decline through midlife. By 55, a large share of men report no close friend to call. Isolation is a health risk on par with smoking.
It does not happen because men stop liking each other. It happens because men stop scheduling each other. Wives schedule. Kids schedule. Nobody schedules the men.
This skill makes you the one who schedules.
Step 1: The 3 a.m. list
Ask the user: "Name the 3 men you would call at 3 a.m. in a crisis. Not who should be on the list. Who IS."
If they have fewer than 3, that is the work of the next year. Recruiting a 3 a.m. list is a project, not a skill.
Save as ~/adulting-data/people/3am-list.md.
For each person on the list:
- Have they been told they are on it? (If no, tell them. A text is fine: "I want you to know, you're one of the three men I'd call if my life blew up. You're on my list. I hope I'm on yours.")
- Who is on theirs? If you don't know, ask.
Step 2: The monthly men's dinner
The structure that works:
- 4 to 8 men. Same group, not a revolving cast.
- Recurring calendar invite. First Thursday of the month, or whatever pattern sticks.
- Same venue if possible. Friction is the enemy of habit.
- Phones face-down or in a basket.
- No agenda required. Conversation is the thing.
If this does not exist yet, help the user:
- Make a list of 6-10 candidates. Men you'd want to spend a long dinner with. Quality over social density.
- Draft the invite. Keep it simple:
"I've been wanting to do this for a while. Once a month, the [pick a day, e.g., first Thursday] — just a dinner with a rotating set of 6 or 7 guys. No agenda, no networking, just the kind of hanging out our wives have figured out and we haven't. You in? I'm proposing [specific date and place] for the first one."
- Send it. The hardest part of brotherhood is sending the text.
Step 3: The quarterly trip
One overnight or weekend trip with the men in your life, every 90 days.
- Fishing, skiing, hiking, poker, whatever.
- The point is 36 to 72 hours of shared time. Men connect in activity, side-by-side, not face-to-face.
- Book the NEXT one before the current one ends. This is the rule. If you leave without scheduling, you will not go again.
Step 4: The weekly one-sentence text
Every week, text one friend (rotate through Tier 1) one sentence:
"How are you, actually?"
The word "actually" is the whole thing. It signals you are not asking for the ritual response. You are asking for a real one.
Expect that the first few times you do this, you will get "I'm good, busy." That is fine. Over time, the texts get real.
Step 5: The crisis check
Ask the user, once a quarter:
- Is anyone on my list going through something hard right now that I've been letting slide?
- When was the last time I saw [each Tier 1] in person?
- Is there anyone who used to be Tier 1 that I've let drift, and who I regret drifting from?
If any of those surface a name, message them this week. Use /friend-reach-out for the draft.
Step 6: The harder one — initiating emotionally
Men are trained to circle the feeling and land on the logistics. Do not. When something is actually going on for a friend, use these openers:
- "That sounds heavy. Tell me more."
- "How are you actually holding up?"
- "I don't have anything smart to say. I just want to be here while you say it."
- "I love you, man. I'm glad you told me."
Saying "I love you" to your close male friends is a standard to hold. It lands differently in hard moments when you've already said it in the easy ones.
Output
Append to ~/adulting-data/journal/brotherhood-log.md:
# <date>
## 3am list status
- <name>: last real contact <when>
- <name>: last real contact <when>
- <name>: last real contact <when>
## This month's dinner
Date: <...>
Attendees: <...>
## Next trip booked
Date: <...>
Where: <...>
Who: <...>
## Weekly one-sentence text
Sent to: <name>
Their reply quality: <surface | real | didn't reply>A line that matters
Remind the user, once in a while: "The friends you have at 70 are the ones you watered in your 30s and 40s. Start now."
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.

