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…
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.
/save-insightContext 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
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.
$WORK_COMPLETED: What did you just complete? (project milestone, tricky problem, meeting, workflow improvement, etc.)
Ask the user (or extract from recent work context):
1. **What was the situation?**
2. **What approach worked?**
3. **What would you do differently?**
4. **What's reusable?**
Store in: `06-Resources/Learnings/[Category]_Learnings.md`
**Categories:**
Create new category files as needed for domain-specific learnings.
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]
If the learning relates to:
1. Ask reflection questions (or extract from context) 2. Create/update the appropriate learning file 3. Suggest any cross-links 4. Confirm saved
> "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.
---
Update `System/usage_log.md` to mark learning capture as used.
**Analytics (Silent):**
Call `track_event` with event_name `insight_saved` and properties:
This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
A personal operating system for your work. Strategic work management, meeting intelligence, relationship tracking, daily planning — all configured for your specific role.
Repo: davekilleen/Dex
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…
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying…
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…
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design…
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills,…