Add designing-agent-memory-schemas skill (query-and-schema-design) - #17
Open
Vector897 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a new skill,
designing-agent-memory-schemas, to the query-and-schema-design domain. It guides developers through designing CockroachDB schemas for AI agent memory: an episodic/semantic memory table with aVECTORcolumn, a prefix-filtered vector index for per-agent cosine ANN, a two-stage retrieval query shape, history-preserving reconciliation via asupersedesself-reference, set-based forgetting-curve decay, crash-safe checkpoint and audit companion tables, and optional row-level TTL.Every SQL statement in the skill was executed and verified live against a CockroachDB Cloud Basic cluster (v26.x) while building an agent memory layer for the CockroachDB × AWS hackathon.
Related Issue
Closes #16
Type of Change
Skill Compliance Checklist
name,description)compatibilityfield, matching existing skills)python scripts/validate-spec.py skills/Note on validation:
validate-spec.pyemits one gerund-form warning for this name; the check's prefix whitelist doesn't include "designing", so already-merged skills likedesigning-application-transactionstrigger the same warning. Happy to rename if maintainers prefer.Documentation Updates
None required.