popoffvg/context-find
harness/plugins/memory-keeper/skills/context-find/SKILL.md
Search and retrieve insights from persistent memory. This skill should be used when the user says "context find", "recall", "what do I know about", "find my notes on", "search memory", "do I have anything on", or wants to retrieve previously saved knowledge. Always invoke to check memory before answering any topic-based question.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles context-findInstall 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: Apr 16, 2026, 2:26 AM6.1s1 file scanned
SKILL.md
- name:
- context-find
- description:
- Search and retrieve insights from persistent memory. This skill should be used when the user says "context find", "recall", "what do I know about", "find my notes on", "search memory", "do I have anything on", or wants to retrieve previously saved knowledge. Always invoke to check memory before answering any topic-based question.
Context Find
Usage
/context find <query>
Examples:
/context find kubernetes debugging patterns/context find what do I know about the auth service/context find(shows all projects overview)
Search Procedure
- Read
insights_rootfrom~/.claude/memory-keeper.local.mdYAML frontmatter. If the file is missing, stop and ask the user to create it with the required settings (see plugin README). - If no query → read and display
<insights_root>/INDEX.md - Use
mcp__qmd__searchwithcollection: "ctx"for keyword matching - If few results → use
mcp__qmd__deep_searchwithcollection: "ctx"for semantic search - If still insufficient → search
mcp__qmd__searchwithcollection: "z-core"(Obsidian vault) as fallback - Use
mcp__qmd__getor Read tool to retrieve full file content - If nothing found → ask the user where to search (e.g. specific repo, web, docs URL) and use the appropriate tool
- Present results with project/topic context
List Procedure
- Read
<insights_root>/INDEX.mdfor project overview - For specific project → read
<insights_root>/<project>/_summary.md - Present organized summary
Related Skills
popoffvg/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026