feat: add memory-management skill#7
Draft
thomas-chen-glean wants to merge 1 commit into
Draft
Conversation
Add the memory-management skill for reading, writing, and reasoning about Glean memory entries across sources and categories. The skill provides playbooks for session continuity, style adaptation, and broad context retrieval using memory_schema and read_memory tools. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
memory-managementskill from askscio/skills, adapted for the cursor-plugins frontmatter conventionmemory_schemaandread_memoryMCP toolsCompatibility with incoming MCP memory changes
Reviewed against three in-flight PRs on the MCP memory server. No skill changes were needed:
memory_sourceon writes; add VSCode/Shared sourcesmemory_schemaas the runtime contract") means agents discover write requirements from the schema, not hardcoded assumptionscontentfieldTest plan
npm run validatepassesmemory_schemaandread_memorywork as described in the skill playbooks🤖 Generated with Claude Code