← ClaudeAtlas

journaling-sessionslisted

Capture knowledge from a work or reference-reading session into structured, separable, retrieval-ready entries for a long-term memory store. Use when the user says "journal", "log this", "wrap up", "session summary", "capture what we learned", or "create registries for everything" — and equally on any request to preserve what was worked out for the future, even about one specific topic — phrasings like "record the decisions/dead ends", "note the reasoning", "don't lose this", "before I forget", "so next time we don't relitigate", "so a future session benefits". Activate proactively when a substantive session is ending after 3+ decisions, findings, or ingested reference items. Covers implementation/decision sessions and end-to-end reference ingestion. Not for quick Q&A or sessions with no novel knowledge; not for consolidating prior journals into higher-level patterns (that is a separate downstream pass).
grimaldost/craft-collection · ★ 2 · AI & Automation · score 68
Install: claude install-skill grimaldost/craft-collection
# Journaling Sessions Capture what a session produced as **structured, separable, retrieval-ready entries** — prose with metadata, one idea each — that a future session can find and reason about in isolation. The quality bar is not "does this summarize the session" but "will a future session, retrieving this cold months from now, be measurably better for having it." These entries are raw material: a downstream process clusters many of them into generalizations, and repeated reinforcement promotes the durable ones into long-lived guidance. Write each entry so that clustering works — that is what every rule here optimizes for. This skill produces raw capture. It runs an **automatic multi-pass loop** so you get thorough output from a single invocation — you do not need to ask for "multiple passes." ## What a session produces Three kinds of knowledge; capture all three, not only the most obvious: - **Conclusions** — decisions made, facts discovered, tradeoffs analyzed, hypotheses formed. What a meeting summary would contain. - **Process dynamics** — the shape of the reasoning: where breakthroughs happened, where we got stuck, what surprised us, what assumptions proved wrong. - **Perceptions** — what the user cared about, what engaged them or felt like overhead, what they pushed back on and why. The three-part framing is a coverage checklist, not a prediction of how entries cluster. Underjournaling conclusions is fine; underjournaling perceptions is a systematic blind