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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplar of progressive disclosure: a minimal SKILL.md that defers all substantive guidance to a single, well-structured reference file with a concrete invocation instruction. The thin body is intentional and well-executed.

Dimension	Reasoning	Score
Conciseness	A single lean paragraph with no padding and no explanation of concepts Claude already knows; every token earns its place and it assumes Claude's competence.	5 / 5
Actionability	Gives a concrete executable instruction (use the `view_file` tool on a specific path, before running `git log`/`grep`/design/review), with the detailed guidance correctly deferred one level deep to the reference.	4 / 5
Workflow Clarity	The single action (read the protocol file before proceeding) is unambiguous with a clear do-before ordering, but explicit checkpoints live in the referenced protocol rather than the body.	4 / 5
Progressive Disclosure	Thin overview body pointing to exactly one well-signaled, one-level-deep reference (`.agents/skills/memory-mining/references/memory-mining-protocol.md`, present in ./references/) that is itself well-organized.	5 / 5
	Total	18 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and gated triggers, using natural user phrases and third-person voice throughout. Minor room to tighten abstract phrasing and add synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("querying the Memory Core", "surfacing cross-session, cross-harness context via semantic search", "prior-art sweep"), but a few remain abstract ("proposing non-trivial architectural claims").	4 / 5
Completeness	Explicitly answers both what (query the Memory Core, surface prior context via semantic search, prevent re-derivation) and when via a concrete numbered "Use this skill when" trigger list.	5 / 5
Trigger Term Quality	Strong natural trigger phrases are quoted directly ("used to work", "suddenly broken", "additionalProperties rejections", "schema mismatches"), with good coverage though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (memory-first reflex before claims/reviews) with distinct triggers and explicit contrast against ask_knowledge_base, though some overlap with general search/KB skills remains.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: neomjs/neo
Path: .agents/skills/memory-mining/SKILL.md
Commit: 210c03c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.