five-hard
Skill6 starsChanged 2 months agoMITView on GitHub
Have the second brain ask the owner five hard questions about their own long-held beliefs and codex entries that have not been revisited, so assumptions stop fossilizing. Monthly or on demand. Triggers: "/five-hard", "challenge my beliefs", "pressure-test my views".
In this repository100 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 03Skill
- 1Skill
- agendaSkill
- alfa-search-recall-deepresearchSkill
- alpha-judgeSkill
- alpha-reviewSkill
- archSkill
- askSkill
- bibleSkill
- brainSkill
- busSkill
- canon-revisionSkill
- ccSkill
- chatgpt-syncSkill
- chat-searchSkill
- chatSkill
- claudeai-syncSkill
- coachSkill
- codex-mirrorSkill
- codex-reviewSkill
- cofounderSkill
- cofounder-watchSkill
- commentsSkill
- community-alphaSkill
- content-mineSkill
- crm-syncSkill
- declinedSkill
- dedupSkill
- defuddleSkill
- dr-fanoutSkill
- episodeSkill
- faaa-syncSkill
- faSkill
- fb-postSkill
- fb-replySkill
- fb-watchSkill
- findSkill
- fireflies-syncSkill
- fleetSkill
- follower-onboardSkill
- geminiSkill
- gitbook-importSkill
- gmailSkill
- granola-syncSkill
- handoffSkill
- health-syncSkill
- inboxSkill
- intakeSkill
- intentionSkill
- introSkill
- issue-matchSkill
- journeySkill
- last30daysSkill
- local-chatgpt-token-healSkill
- mcpSkill
- migrateSkill
- mine-channelSkill
- n8nSkill
- notebooklmSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 22
Read each note IN FULL and give ONE hard question per note:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
/five-hard — five hard questions
🧒 When reporting to a non-technical operator, end with a child-simple "In plain words" recap in their language.
Why: the identity layer (belief-* + concept-bible-*, ~24 notes) is "how I think".
That gets dangerous once part of it is wrong and nobody has checked. Here the brain itself starts the pressure-test.
Run
python "$IMPORTS_ROOT/five_hard_pick.py" -> the 5 most stagnant notes (oldest mtime)
-> $IMPORTS_ROOT/_five_hard_pick.json. Override: env FIVE_HARD_N=7.
The questions (top-model quality — identity synthesis, not grunt work)
Read each note IN FULL and give ONE hard question per note:
N. **[<stem>]** — <the owner's thesis in your own words>
Question: <sharp, Socratic, capable of forcing a rethink>
Why it is hard: <which counter-fact or trend could flip it>Style: Socratic — not "you are wrong" but "what makes you sure today?"; lean on CONCRETE recent
signals; epistemic-neutrality; aim at the UNTESTED edge (the "tension / nuance" section),
not at the part already reflected on. "The rule still stands" is a valid answer (bible-as-prompt).
Recording the answer (long memory; backup-first: vault_backup.py)
-> $OBSIDIAN_VAULT/04-Coach/_Five-Hard/five-hard-YYYY-MM-DD.md
Frontmatter: title, date, type: five-hard, source: claude-session,
tags: [five-hard, coach, identity-layer]. Body: the questions + the owner's answers verbatim;
if they changed position, propose a diff to the belief/bible note with supersedes: (via /intake). NO 🧒 block inside the note.
Scheduled twin
Cron five-hard-monthly: 1st of the month, 05:25 Lisbon (the briefing window, routines-run-at-night).
Picker -> questions (top-model subagent) -> the fleet log chat via python $USERPROFILE/.claude/scripts/bus_ping.py --post "..."
(canon: alerts go to the fleet log chat, never to Saved Messages) + "answer by voice or text, I will file it into the vault".
The manual twin is this skill; the single source of truth is the picker.
Related
[[self-bible-identity-layer]] · [[bible-as-prompt]] · [[epistemic-neutrality]] · /coach (daily) vs /five-hard (monthly). Active-brain map A-E: item B. ⚠️ Restored 2026-07-04 after the 2026-06-24 migration wipe.
<!--kit-footer-->Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.
Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).
Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_
Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.
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.

