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.
npx skillsauth add popoffvg/dotfiles context-findInstall 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.
/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)insights_root from ~/.claude/memory-keeper.local.md YAML frontmatter. If the file is missing, stop and ask the user to create it with the required settings (see plugin README).<insights_root>/INDEX.mdmcp__qmd__search with collection: "ctx" for keyword matchingmcp__qmd__deep_search with collection: "ctx" for semantic searchmcp__qmd__search with collection: "z-core" (Obsidian vault) as fallbackmcp__qmd__get or Read tool to retrieve full file content<insights_root>/INDEX.md for project overview<insights_root>/<project>/_summary.mdtesting
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
testing
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
tools
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
development
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.