From mosdat
Use when the user invokes /insight, says 'capture insight', or after repeated failures to surface relevant project and personal lessons. Captures structured insight entries and surfaces existing knowledge to prevent repeated mistakes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mosdat:mosdat-insightThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Triggers: `/insight`, "insight", "capture insight"
Triggers: /insight, "insight", "capture insight"
/insight or "capture insight"<project>/.knowledge/**/*.md — project-specific lessons~/.knowledge/**/*.md — personal cross-project lessons<project>/shared/recipes/*.yaml — F2 recipe corpus (if present)--no-autoinsight passed.Elicit or infer from session context:
Determine scope:
project-shared → <project>/.knowledge/ — specific to this codebase/tooling.user-personal → ~/.knowledge/<tech>/ — reusable across projects for this tech.tech-specific → ~/.knowledge/<tech>/ — platform/framework behavior.Determine kind:
war-story — painful failure with root cause and fixlesson — non-obvious discovery about how something workspattern — reusable approach that workedinsight — principle or observation with broad applicabilityWrite the entry (see format below). Keep body under 15 lines — dense, not verbose.
Write path:
<project>/.knowledge/<category>/<slug>.md~/.knowledge/<tech>/<slug>.mdIf scope = user-personal: append entry path to ~/.knowledge/index.md (create if missing).
Report the written path to the user.
---
date: "YYYY-MM-DD"
project: <project-name or "general">
tags:
- <tag1>
- <tag2>
topic: <one-line summary — what future-you will search for>
kind: war-story|lesson|pattern|insight
scope: project-shared|user-personal|tech-specific
category: <tech/subtopic — e.g., electron/ipc, git/rebase>
confidence: high|medium|low
cost: "<N attempts × ~Xmin = ~Yhr>"
---
## Context
<1-2 sentences: what were you doing, what went wrong or what were you exploring>
## Root cause
<The actual reason — not symptoms>
## Pivot
<What fixed it or what the discovery was>
## Rule
<Concrete, actionable rule: one sentence a future agent can apply immediately>
If mastermind is active (check: mastermind --help), use mm_write instead of writing raw markdown for user-personal entries. Mastermind's extract hook (PreCompact) reads the conversation and can auto-extract insights — /insight ensures deliberate, structured capture with frontmatter that matches .knowledge conventions.
For project-shared entries, write raw markdown to .knowledge/ directly — mastermind's suggest hook (PostToolUse on Read/Edit/Write) will surface them automatically on next relevant file touch.
mastermind extract reads conversation transcripts and writes to ~/.knowledge/. Structured .knowledge/*.md entries (with frontmatter) are read by mastermind suggest --from-hook, which fires on every Read/Edit/Write and surfaces matching lessons. Insight entries written here ARE auto-pulled into the knowledge surface — no extra wiring needed.
npx claudepluginhub jeanfbrito/mosdatProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.