Skill Repos Should Ship the Synthesis Graph
lat.md maps source corpora, evidence, objections, and offer logic beside SKILL.md files, which is the same receipt-first pattern joelclaw needs for durable skill authoring.
The sharp part of badass-courses/skills isn’t just the SKILL.md files. It’s the lat.md/ folder sitting beside them as an Obsidian graph.
That makes the repo feel less like a pile of prompts and more like a working methodology lab. The public surface is installable skills for email marketing, audience segmentation, Kit automation, and launch operations. The hidden muscle is the graph: pain-library, objections, offer-shapes, proof-bank, source-map, and the synthesis notes that tie Amy Hoy, Alex Hillman, Stacking the Bricks, Just Fucking Ship, Brennan Dunn, Segment With Surveys, and Mastering Kit into operator workflows.
Joel called out that the lat.md/ folder “goes hard af” because it can be opened directly in Obsidian and cross-referenced against egghead Roam Research, Notion, source books, courses, and other corpus material. That’s the useful pattern: don’t let the synthesis disappear into chat exhaust. Keep the graph, provenance, and working notes in the repo, then let the agent skill be the compiled interface.
This maps cleanly to joelclaw and Pi: when a skill is distilled from real source material, the repo should carry both the runnable instruction and the receipts. Otherwise the agent eventually starts freeballing, and that’s where the bullshit creeps in.
Key Ideas
- A
SKILL.mdfile is stronger when it sits next to a browsablelat.md/Obsidian graph with source maps, evidence, objections, proof, and working synthesis. - The badass-courses/skills repo turns Brennan Dunn segmentation and Kit automation material into process-oriented agent skills instead of static notes.
- The
lat.md/README.mdframes Stacking the Bricks / Just Fucking Ship as practical decision discipline: pain first, customer research first, atomization, shipping, and launch mechanics rooted in real audience language. - The newer package shape includes
brain-first-workflow, which makes.brain/canonical before Linear mirrors or tracker artifacts. - The repo-level pattern is portable to joelclaw: keep Vault notes, source corpora, and provenance beside the executable agent surface so future agents can check the receipts before acting.