skills/memories-learn/SKILL.md
Extract learnings from session transcripts and store in semantic memory database
npx skillsauth add mahmoudimus/simba memories-learnInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Check the dispatch mode:
simba config get hooks.learn_async
Then read ~/.claude/transcripts/latest.json to get the transcript path, session ID, and project path.
Build this Task prompt:
Read the transcript at <TRANSCRIPT_PATH> and extract learnings to store in the semantic memory database.
For each learning found, store it by running:
simba memory store --type <TYPE> --content "<LEARNING>" --context "<CONTEXT>" --confidence <SCORE> --session-source "<SESSION_ID>" --project-path "<PROJECT_PATH>"
LEARNING TYPES:
- WORKING_SOLUTION: Commands, code, or approaches that worked
- GOTCHA: Traps, counterintuitive behaviors, "watch out for this"
- PATTERN: Recurring architectural decisions or workflows
- DECISION: Explicit design choices with reasoning
- FAILURE: What didn't work and why
- PREFERENCE: User's stated preferences
RULES:
- Be specific - include actual commands, paths, error messages
- Confidence 0.95+ for explicitly confirmed, 0.85+ for strong evidence
- Skip generic programming knowledge Claude already knows
- Focus on user-specific infrastructure, preferences, workflows
- Keep content under 200 characters, use context field for details
- Preserve proper nouns, file paths, and identifiers verbatim — never replace them with generic words
- Preserve numeric precision: keep exact values exact; never weaken an exact number to a range or approximation
- Resolve relative dates to absolute ones (e.g. "yesterday" -> the actual date)
Extract 5-15 quality learnings.
Dispatch using the Task tool with subagent_type=memory-extractor:
development
Index the current project for optimized search with QMD semantic search and fast file suggestions. Run this when entering a new codebase or after significant changes. Saves 60-80% tokens on exploration tasks.
tools
Show token economics comparing usage with turbo-search vs without. Demonstrates actual savings from search-first approach.
development
Enforce Simba's Codex lifecycle routine for coding tasks. Use when starting or finishing implementation work in a Simba-enabled repo to run `simba codex-status` at start, `simba codex-extract` when extraction is pending, and `simba codex-finalize` before final handoff.
tools
Save the current work session to persistent memory for future context. Summarizes accomplishments, tracks files modified, and stores learnings for cross-session continuity.