/save-insight
Capture a reusable learning from completed work so future similar work is easier. Use when the user says 'save this learning', 'capture this insight', or finishes something tricky. Also use proactively after non-routine work. Not for recording a *decision* and its rationale; use
$ npx -y skills add davekilleen/Dex --skill save-insight --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/save-insight
Context preview
The summary Claude sees to decide when to auto-load this skill.
Capture a reusable learning from completed work so future similar work is easier. Use when the user says 'save this learning', 'capture this insight', or finishes something tricky. Also use proactively after non-routine work. Not for recording a *decision* and its rationale; use
SKILL.md
save-insight.SKILL.mdname: save-insight
description: "Capture a reusable learning from completed work so future similar work is easier. Use when the user says 'save this learning', 'capture this insight', or finishes something tricky. Also use proactively after non-routine work. Not for recording a *decision* and its rationale; use `decision-log`."
Capture what you learned from completing work. This is the "compound" step—making future similar work easier.
Arguments
$WORK_COMPLETED: What did you just complete? (project milestone, tricky problem, meeting, workflow improvement, etc.)
Process
1. Reflection Questions
Ask the user (or extract from recent work context):
1. **What was the situation?**
- Original goal or challenge
- Why it was harder than expected (if applicable)
2. **What approach worked?**
- Strategy or tactic used
- Key decisions made
3. **What would you do differently?**
- Gotchas encountered
- Better approaches discovered late
4. **What's reusable?**
- Patterns that apply elsewhere
- Mental models that help
2. Create or Update Learning Note
Store in: `06-Resources/Learnings/[Category]_Learnings.md`
**Categories:**
- `Working_Preferences` - How you like to work, communication style, tool preferences
- `Mistake_Patterns` - Common errors to avoid, with triggers and corrections
Create new category files as needed for domain-specific learnings.
3. Learning Entry Format
Append to the appropriate file:
---
## [Short Title] — [Date]
**Context:** [1 sentence on what you were doing]
**Challenge:** [What was tricky or non-obvious]
**What Worked:**
[The approach that succeeded]
**Key Insight:**
> [The memorable takeaway—something you'd tell past-you]
**See Also:** [Related notes if any]
4. Cross-Link (Optional)
If the learning relates to:
- A person → Add to their person page
- A project → Add link in project's note
- A recurring workflow → Update relevant template
Output
1. Ask reflection questions (or extract from context) 2. Create/update the appropriate learning file 3. Suggest any cross-links 4. Confirm saved
Philosophy
> "The palest ink is better than the best memory." — Chinese proverb
This isn't documentation for others—it's a gift to future-you. Be specific. Include the gotcha. Make it searchable.
---
Track Usage (Silent)
Update `System/usage_log.md` to mark learning capture as used.
**Analytics (Silent):**
Call `track_event` with event_name `insight_saved` and properties:
- category
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
Read more
name: save-insight description: "Capture a reusable learning from completed work so future similar work is easier. Use when the user says 'save this learning', 'capture this insight', or finishes something tricky. Also use proactively after non-routine work. Not for recording a *decision* and its rationale; use `decision-log`."
Capture what you learned from completing work. This is the "compound" step—making future similar work easier.
Arguments
$WORK_COMPLETED: What did you just complete? (project milestone, tricky problem, meeting, workflow improvement, etc.)
Process
1. Reflection Questions
Ask the user (or extract from recent work context):
1. **What was the situation?**
- Original goal or challenge
- Why it was harder than expected (if applicable)
2. **What approach worked?**
- Strategy or tactic used
- Key decisions made
3. **What would you do differently?**
- Gotchas encountered
- Better approaches discovered late
4. **What's reusable?**
- Patterns that apply elsewhere
- Mental models that help
2. Create or Update Learning Note
Store in: `06-Resources/Learnings/[Category]_Learnings.md`
**Categories:**
- `Working_Preferences` - How you like to work, communication style, tool preferences
- `Mistake_Patterns` - Common errors to avoid, with triggers and corrections
Create new category files as needed for domain-specific learnings.
3. Learning Entry Format
Append to the appropriate file:
--- ## [Short Title] — [Date] **Context:** [1 sentence on what you were doing] **Challenge:** [What was tricky or non-obvious] **What Worked:** [The approach that succeeded] **Key Insight:** > [The memorable takeaway—something you'd tell past-you] **See Also:** [Related notes if any]
4. Cross-Link (Optional)
If the learning relates to:
- A person → Add to their person page
- A project → Add link in project's note
- A recurring workflow → Update relevant template
Output
1. Ask reflection questions (or extract from context) 2. Create/update the appropriate learning file 3. Suggest any cross-links 4. Confirm saved
Philosophy
> "The palest ink is better than the best memory." — Chinese proverb
This isn't documentation for others—it's a gift to future-you. Be specific. Include the gotcha. Make it searchable.
---
Track Usage (Silent)
Update `System/usage_log.md` to mark learning capture as used.
**Analytics (Silent):**
Call `track_event` with event_name `insight_saved` and properties:
- category
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
A personal operating system powered by Claude. Strategic work management, meeting intelligence, relationship tracking, daily planning — all configured for your specific role. No coding required.
Repo: davekilleen/Dex
Other skills on davekilleen-dex.
- /agent-browser
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click
Open skill - /agent-native-architecture
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Open skill - /andrew-kane-gem-writer
This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on
Open skill - /brainstorming
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore
Open skill - /compound-docs
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Open skill - /create-agent-skills
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
Open skill

