Menu

Individual skill

graymatter-memory

Search, retrieve, save, revise, and forget secure durable GrayMatter memory. Use when a task may depend on prior decisions, preferences, todos, artifacts, or long-lived context, or when the user asks to remember, update, or forget information.

plugins/ValkyrLabs/GrayMatter/skills/graymatter-memory/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GrayMatter Memory

Use GrayMatter as the durable memory system for information that remains useful beyond the current conversation.

## Workflow

1. Call `memory_search` before asking the user to repeat prior context that may already be known.
2. Use `memory_get` only to hydrate a specific authorized result when its full content is needed.
3. Keep temporary reasoning, transient chat state, and one-off working notes in the conversation rather than durable memory.
4. Call `memory_save` only for useful durable decisions, preferences, todos, artifacts, configuration, or reusable context.
5. Avoid storing passwords, access tokens, private keys, payment data, or highly sensitive personal information unless the product explicitly supports and the user clearly requests that use.
6. Use concise titles, normalized tags, and a stable source or scope. Store the durable fact in `content`; do not embed owner, tenant, ACL, user, or organization identifiers.
7. Call `memory_update` when an existing durable fact changes. Do not create a contradictory duplicate when the existing memory can be revised.
8. Before `memory_forget`, identify the exact memory and obtain explicit user confirmation. Pass `confirm: true` only after that confirmation.