NodeJSmith/cm-recall-conversations
skills-memory/cm-recall-conversations/SKILL.md
Use when the user asks to recall, search, or continue past conversations. Triggers on "what did we discuss", "continue where we left off", "remember when", "as I mentioned", "you suggested", "we decided", "search my conversations", "find the conversation where", "what did we work on". Also triggers on implicit signals like past-tense references ("the bug we fixed"), possessives without context ("my project"), or assumptive questions ("do you remember").
$ install --global
skillsauthnpx skillsauth add NodeJSmith/Claudefiles cm-recall-conversationsInstall 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: Jun 12, 2026, 2:25 AM197.6s3 files scanned
SKILL.md
- name:
- cm-recall-conversations
- user-invocable:
- true
- description:
- >
Tools
Two scripts retrieve data. For full option catalogs, load references/tool-reference.md.
recent_chats.py — retrieve recent sessions:
cm-recent-chats --n 3
search_conversations.py — keyword search across all sessions:
cm-search-conversations --query "keyword"
Workflow
- Identify the lens from user intent:
| User Says | Lens | |-----------|------| | "where were we", "recap" | restore-context | | "gaps", "struggling" | find-gaps | | "mentor", "review process" | review-process | | "retro", "project review" | run-retro | | "decisions", "CLAUDE.md" | extract-decisions | | "bad habits", "antipatterns" | find-antipatterns |
Load references/lenses.md for per-lens parameters, core questions, and supplementary search patterns.
-
Gather context using lens-appropriate tools:
- For recent context:
cm-recent-chats --n N - For keyword search:
cm-search-conversations --query "keywords"
- For recent context:
-
Apply lens questions to analyze the retrieved conversations.
-
Deepen the search if initial results are insufficient:
- Retrieve more sessions:
--n 20 - Search for specific terms that surfaced
- Filter by project:
--project projectname - Filter by session:
--session <uuid-prefix>(when a specific session ID is known) - If 2 rounds of deepening yield no new relevant sessions, synthesize from available data.
- Retrieve more sessions:
Query Construction
Search terms should be content-bearing words that discriminate between sessions — high information value words that are rare enough to rank relevant sessions above irrelevant ones. BM25 ranking (when FTS5 is available) weights rare terms higher automatically.
Include: specific nouns, technologies, concepts, project names, domain terms, unique phrases. More terms improve ranking precision.
Exclude: generic verbs ("discuss", "talk"), time markers ("yesterday"), vague nouns ("thing", "stuff"), meta-conversation words ("conversation", "chat") — these appear in nearly every session and add noise rather than signal.
Algorithm:
- Extract substantive keywords from user request
- If 0 keywords, ask for clarification ("Which project specifically?")
- If 1+ specific terms, search with those terms; use
--projectto narrow scope
Synthesis
Principles
- 3-5 key findings, not exhaustive lists — each specific (file paths, dates, project names) and backed by a quote or reference.
- Make it actionable — every finding suggests a response.
Structure
## [Analysis Type]: [Scope]
### Summary
[2-3 sentences]
### Findings
[Organized by whatever fits: categories, timeline, severity]
### Patterns
[Cross-cutting observations]
### Recommendations
[Actionable next steps]
Length
Default: 300-500 words. Expand only when data warrants it.
Related Skills
NodeJSmith/mine.humanize
development
VerifiedTrustedCommunity
Use when the user says: "humanize this", "unslop this", "de-slop this", "fix AI writing", "remove AI tells", "clean up AI prose". Edits prose to remove AI writing patterns and add human voice. Analyzes first, then asks how to fix. Prose complement to mine.clean-code.
1SKILL.mdUpdated Jun 9, 2026
NodeJSmith/mine.why
development
VerifiedTrustedCommunity
Use when the user says: "why is this code like this", "why does this exist", "why was this built this way", "decision rationale", "what's the history behind". Decision archaeology — reconstructs historical rationale from evidence, not speculation.
1SKILL.mdUpdated Jun 8, 2026
NodeJSmith/mine.how
development
VerifiedTrustedCommunity
Use when the user says: "how does X work", "walk me through", "explain this subsystem", "explain how", "trace the flow". Complexity-adaptive subsystem explanation — builds mental models conversationally, not documentation artifacts.
1SKILL.mdUpdated Jun 8, 2026
NodeJSmith/mine.create-issue
development
VerifiedTrustedCommunity
Use when the user says: 'create an issue', 'file an issue', 'open an issue', 'write an issue', 'new issue for this'. Codebase-aware issue creation — investigates the code to produce well-structured issues with acceptance criteria, affected areas, and enough detail for automated triage.
1SKILL.mdUpdated May 28, 2026