From kmgraph
Auto-captures lessons when you solve bugs, make breakthroughs, identify patterns, or complete debugging sessions. Extracts problem, solution, and pattern from conversation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kmgraph:lesson-captureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** Auto-capture lessons when user solves complex bugs, makes breakthroughs, identifies patterns, or completes debugging sessions.
Purpose: Auto-capture lessons when user solves complex bugs, makes breakthroughs, identifies patterns, or completes debugging sessions.
Trigger Keywords (detect any of these):
Behavior: When triggered:
Pre-structure context from the conversation:
Note: When dispatching to lesson capture, the lesson-capture-agent includes a snapshot gate that offers to preserve session context first. This is presented to the user inside the agent flow — do not add a separate snapshot prompt here.
ECC Compatibility: The slash command syntax (/kmgraph:capture-lesson) is Claude Code–specific. On other ECC platforms, the lesson-capture-agent is dispatched directly via agent invocation without a command namespace.
Dispatch to lesson-capture-agent with the pre-structured context as a named payload:
context_provided: true
problem: "[extracted problem]"
solution: "[extracted solution]"
pattern: "[extracted generalizable lesson]"
tags: ["[tag1]", "[tag2]"]
suggested_category: "[architecture|debugging|patterns|process]"
The agent uses context_provided: true to skip its interactive wizard and go directly to draft generation.
Use friendly, user-addressed language — never mention agent mechanics:
Do NOT trigger on:
rules-capture skill. If both a lesson and a rule apply to the same turn, both skills fire independently.Example Trigger:
User: "Figured it out! The issue was the config being cached in memory.
We needed to invalidate on every write."
Skill response:
"Looks like you just solved something worth keeping. Here's what I'd capture:
- Problem: Config being cached in memory between writes
- Solution: Invalidate cache on every write operation
- Pattern: Cache invalidation timing matters in multi-state systems
- Tags: [caching, memory, invalidation]
Want me to document this as a lesson?"
npx claudepluginhub technomensch/knowledge-graph --plugin kmgraphFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.