← ClaudeAtlas

mc-distilllisted

Propose a reusable SKILL.md from the current session when a hard-won insight — or a newly-discovered capability worth reusing — has emerged. TRIGGER on explicit user request ("/distill", "propose a skill", "do we have a pattern here") OR proactively at a natural breakpoint (end of task, after commit, wrap-up) when a single in-the-moment insight is worth bottling NOW. Cross-session recurrence is the silent Distiller's job (Phase 4). Writes only to data/skills/_proposed/ for human review; never auto-installs.
ronle/clayrune · ★ 13 · AI & Automation · score 80
Install: claude install-skill ronle/clayrune
# Distill a SKILL.md proposal from the current session This skill complements Phase 4 (the cross-session silent Distiller). Phase 4 catches patterns that recur across many sessions; this skill catches the novel in-the-moment insight from THIS session that's worth bottling immediately — because waiting weeks for cross-session recurrence to catch a fresh hard-won discovery is silly. MC owns the skill registry — you propose, the human reviews and promotes by hand. ## Two ways this skill triggers ### 1. Explicit user invocation The user says: "/distill", "propose a skill", "do we have a pattern here", "is this worth bottling". Run through the full Procedure below. ### 2. Proactive (agent-initiated) YOU notice an insight worth bottling and surface it without being asked. **Rules for proactive triggering — ALL must hold:** - **Natural breakpoint:** end of a task, just after a commit, or in a clear wrap-up moment. NEVER trigger mid-task, mid-debug, mid-investigation. - **Strengthened specificity (v2 — pattern-bound vs session-bound):** you can name the insight in one sentence AND a future agent in a *different* session — possibly months later — would recognize the trigger from incoming context. The test: rewrite the proposal's TRIGGER phrasing without naming the specific session's symptom. Does anything reusable remain? - **Pattern-bound** (good): "when CF Access tokens lag in 'last used' display, check session_duration first — the dashboard timestamp is stale by design.