not-matthias/extract-knowledge
modules/home/programs/cli-agents/shared/skills/workflows/extract-knowledge/SKILL.md
Extract patterns and challenges from past Claude Code conversation logs and convert them into reusable skills or memory entries. Run periodically to capture recurring solutions.
$ install --global
skillsauthnpx skillsauth add not-matthias/dotfiles-nix extract-knowledgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 29, 2026, 5:16 AM198.9s1 file scanned
SKILL.md
- name:
- extract-knowledge
- description:
- Extract patterns and challenges from past Claude Code conversation logs and convert them into reusable skills or memory entries. Run periodically to capture recurring solutions.
- license:
- MIT
- context:
- fork
- agent:
- Explore
Knowledge Extraction from Claude Code Logs
Extract recurring challenges, solutions, and patterns from past Claude Code sessions and distill them into skills or memory entries.
When to Use This Skill
- After intensive development sessions on a new project
- When you notice solving the same problem repeatedly
- Weekly scan to capture recent learnings
- Before a major refactor (capture current best practices first)
Log Location & Format
~/.claude/projects/<path-encoded-dir>/
├── sessions-index.json # Metadata index for all sessions in this project
└── <uuid>.jsonl # Individual session (JSON Lines)
sessions-index.json — use this to quickly find relevant sessions:
[{
"sessionId": "uuid",
"firstPrompt": "what the user asked",
"summary": "auto-generated summary",
"messageCount": 42,
"created": "2025-01-01T00:00:00Z"
}]
Extraction Workflow
1. Find relevant sessions
# List all projects
ls ~/.claude/projects/
# Scan session index for a project
cat ~/.claude/projects/<project>/sessions-index.json | \
jq '.[] | {prompt: .firstPrompt, count: .messageCount}' | head -50
# Filter by topic
cat ~/.claude/projects/<project>/sessions-index.json | \
jq '.[] | select(.firstPrompt | test("error|fix|debug|fail"; "i")) | .firstPrompt'
2. Extract user messages from a session
cat ~/.claude/projects/<project>/<session>.jsonl | \
jq 'select(.type == "user") | .message.content' 2>/dev/null | head -30
3. Categorize findings
| What you found | Target skill |
|----------------|--------------|
| Nix hash errors, build failures, overlays | nix-package |
| CodSpeed integration, benchmark setup | codspeed-bench |
| Binary analysis, unpacking, emulation | reverse-engineer |
4. Write the finding
Use this format when adding to a skill:
### [Problem Title]
**Context**: When does this happen?
**Symptom**: What error/behavior do you see?
**Fix**:
```code```
**Why**: Brief explanation
5. Where to put it
- Skill file (
modules/home/programs/cli-agents/shared/skills/<name>/SKILL.md): reusable techniques, non-obvious gotchas, command patterns - Memory (
~/.claude/projects/<dir>/memory/): project-specific context, preferences
What NOT to Extract
- One-off hacks for a specific version
- Things already in CLAUDE.md
- Long context dumps — summarize to the essential pattern only
Related Skills
not-matthias/personal-notes
documentation
VerifiedTrustedCommunity
Save notes, journal entries, and research to the personal-notes Obsidian vault (personal-vault-v2). Use when the user asks to 'save note', 'save to notes', 'write to personal notes', 'save to daily notes', 'note this down', or wants to persist findings/analysis to their personal vault.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/fix-pr
documentation
VerifiedTrustedCommunity
Use whenever the user asks to address, fix, resolve, review, or respond to pull-request comments or review feedback.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/code-style
development
VerifiedTrustedCommunity
Apply Not Matthias's Rust-first personal coding style. Use whenever the user explicitly asks to apply or review their code style, make Rust match their preferences, perform a style pass, or simplify/refactor according to their conventions. Inspect only task-touched code, honor local project conventions first, and make only safe opt-out style edits.
9SKILL.mdUpdated Jul 29, 2026
not-matthias/ast-grep
development
VerifiedTrustedCommunity
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
9SKILL.mdUpdated Jul 29, 2026