memory-schema

Schema lifecycle management for Basic Memory: discover unschemaed notes, infer schemas, create and edit schema definitions, validate notes, and detect drift. Use when working with structured note types (Task, Person, Meeting, etc.) to maintain consistency across the knowledge graph.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

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

The body is highly actionable with executable, parameterized examples and a clear lifecycle structure, and it is well-organized as a single file. Its main weaknesses are mild redundancy in the examples and missing explicit validate-fix-revalidate checkpoints in the batch note-validation workflow.

Suggestions

Add an explicit validate-fix-revalidate loop to the 'Validating Notes' section so batch/drift-driven fixes have a clear checkpoint (e.g., run schema_validate, fix outliers, re-validate until clean).

De-duplicate the Meeting schema definition that appears in both the standalone YAML 'Complete Example' and the write_note metadata block; cross-reference one from the other to tighten the body.

Add a validation gate to the discover/create workflow (e.g., validate immediately after creating a schema) to raise workflow clarity toward the level-3 anchor.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete, non-padded code examples, but it repeats schema field definitions across the standalone YAML example and the write_note metadata example, and some guidelines restate earlier points; it could be tightened without losing clarity.	2 / 3
Actionability	Provides fully executable, copy-paste-ready calls (schema_infer, write_note, schema_validate, schema_diff, edit_note) with realistic parameters and complete YAML, matching the level-3 anchor.	3 / 3
Workflow Clarity	Numbered sequences and a workflow summary exist and the evolution section re-validates, but the validation/fixing of batch notes lacks an explicit validate-fix-revalidate checkpoint and the discover/create flow has no validation gate, so per the rubric's batch/destructive rule workflow clarity caps at 2 rather than 3.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single well-sectioned file with clear headings covering syntax, discovery, creation, validation, drift, and evolution; per the rubric's simple-skill note, well-organized sections score 3 when no external references are needed.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, complete, and well-triggered: it names concrete lifecycle actions, gives explicit when-to-use guidance with natural trigger terms, and carves out a distinct niche. It reads in third person and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'discover unschemaed notes, infer schemas, create and edit schema definitions, validate notes, and detect drift' — matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the schema lifecycle actions) and when ('Use when working with structured note types ... to maintain consistency across the knowledge graph').	3 / 3
Trigger Term Quality	Includes natural trigger language users would say ('structured note types', 'Task, Person, Meeting, etc.') plus an explicit 'Use when working with...' clause; good coverage rather than mere jargon.	3 / 3
Distinctiveness Conflict Risk	Scopes itself tightly to Basic Memory's Picoschema schema lifecycle, with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: basicmachines-co/basic-memory
Path: skills/memory-schema/SKILL.md
Commit: cb95e59

Reviewed: 11 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.