memory-mining
Authoritative protocol for querying the Memory Core before diagnosing regressions or proposing non-trivial architectural claims. Prevents re-derivation of prior reasoning by surfacing cross-session, cross-harness context via semantic search. Triggers: Use this skill when (1) the user reports a regression symptom ("used to work", "suddenly broken", surprise validation failures, schema mismatches, "additionalProperties" rejections), OR (2) you are about to propose an architectural claim, roadmap, or comparison against external work where prior sessions may have already mapped the territory, OR (3) you are about to begin an implementation or a PR-review — a cheap 3–10-call prior-art sweep before the first design sentence or review verdict.
76
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Memory Mining Skill
If you are diagnosing a regression symptom, about to propose a non-trivial architectural claim, or about to begin an implementation or a PR-review, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/memory-mining/references/memory-mining-protocol.md before running git log, grep, the first design sentence, or a review verdict. Or, if you already have the payload in context, proceed directly to its directives.
- Repository
- neomjs/neo
- Commit
c1ce853
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.