Memory Schema
Manage structured note types using Basic Memory's Picoschema system. Schemas define what fields a note type should have, making notes uniform, queryable, and validatable.
When to Use
New note type emerging — you notice several notes share the same structure (meetings, people, decisions)
Validation check — confirm existing notes conform to their schema
Schema drift — detect fields that notes use but the schema doesn't define (or vice versa)
Schema evolution — add/remove/change fields as requirements evolve
On demand — user asks to create, check, or manage schemas
Picoschema Syntax Reference
Schemas are defined in YAML frontmatter using Picoschema — a compact notation for describing note structure.
Basic Types
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+picoschema syntax reference provided with basic types, reducing friction for schema authoring
weaknesses
~no step-by-step procedures for core workflows (discover unschemaed notes, infer schemas, validate, detect drift) - description lists operations but not how to execute them
~no failure modes, constraints, or edge cases addressed (malformed yaml, conflicting field types, partial schema coverage, validation false positives)
~incomplete - 'Basic Types' section terminates abruptly without content or examples
