How do I install the Context Matters skill?

Run npx skillmds@latest add srobinson/context-matters in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Context Matters safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Context Matters?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Context Matters free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Context Matters?

srobinson (@srobinson) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Context Matters by srobinson — Agent Skill

Name: Context Matters
Author: srobinson

Context Matters

Storage policy for the cm context store. Use when deciding whether to persist a fact, decision, or lesson via cx_store/cx_deposit. The cm MCP server documents the tools themselves; this skill governs what belongs in the store and what does not.

srobinson a65b743 2.7 KB Updated Sep 17, 2026

File contents

Context Matters — Storage Policy

The plugin:helioy-tools:cm MCP server exposes the cx_* tools and their parameters. This skill is the editorial policy: what earns a slot in the store.

Store

Ideas, decisions, directions — "we wired up rust-dist in project X this way because Y." The reasoning behind a choice, not just the choice.
Progression and results — what was tried, what worked, what failed, and the conclusion that fell out of it.
Backlog and TODOs — "this feature needs more thought before we build it." Open threads that another session would otherwise re-litigate.
Cross-context knowledge — anything a future session in a different repo or project would benefit from knowing.
User feedback and corrections — store immediately as kind: feedback. Highest recall priority.

Do NOT store

Git history — it is already in the git log. Commits, SHAs, blame.
Line numbers — transient; the file changes and the number rots.
File paths inside a repo — rarely useful. An agent can locate a file by name with a single search. Only store a path when it is a durable external reference (config location, install root, etc.).
Code snippets that mirror the source — read the source, do not cache it.
Routine session activity — "I read three files and ran the tests." No future decision turns on it.
Filler that sounds like evidence — commit name-drops, history lessons, padding. Every token must change a decision the reader will make. If it does not, cut it.

Scope

global > project > repo > session. Ancestor walk: narrower scopes inherit broader ones. Pick the narrowest scope where the entry is actually reusable. Cross-project insight goes to global. A project-wide convention goes to global/project:<id>. A codebase quirk goes to global/project:<id>/repo:<id>. Session scope is ephemeral and rarely worth using.

Operating rules

Call cx_recall after receiving a task — query 1-3 keywords, not a sentence.
Store as you discover, not at session end. Memory written later is memory rewritten.
When the user corrects you, store the correction as kind: feedback before continuing.
Use cx_update or supersedes when an entry is wrong. Do not let stale entries accumulate alongside corrections.
Do not mention the context store to the user unless asked.

CLI fallback

cm stats — store statistics. cm serve — start MCP on stdio.

---name: context-mattersdescription: Storage policy for the cm context store. Use when deciding whether to persist a fact, decision, or lesson via cx_store/cx_deposit. The cm MCP server documents the tools themselves; this skill governs what belongs in the store and what does not.---# Context Matters — Storage PolicyThe `plugin:helioy-tools:cm` MCP server exposes the `cx_*` tools and their parameters.This skill is the editorial policy: what earns a slot in the store.## Store- **Ideas, decisions, directions** — "we wired up rust-dist in project X this way because Y." The reasoning behind a choice, not just the choice.- **Progression and results** — what was tried, what worked, what failed, and the conclusion that fell out of it.- **Backlog and TODOs** — "this feature needs more thought before we build it." Open threads that another session would otherwise re-litigate.- **Cross-context knowledge** — anything a future session in a different repo or project would benefit from knowing.- **User feedback and corrections** — store immediately as `kind: feedback`. Highest recall priority.## Do NOT store- **Git history** — it is already in the git log. Commits, SHAs, blame.- **Line numbers** — transient; the file changes and the number rots.- **File paths inside a repo** — rarely useful. An agent can locate a file by name with a single search. Only store a path when it is a durable external reference (config location, install root, etc.).- **Code snippets that mirror the source** — read the source, do not cache it.- **Routine session activity** — "I read three files and ran the tests." No future decision turns on it.- **Filler that sounds like evidence** — commit name-drops, history lessons, padding. Every token must change a decision the reader will make. If it does not, cut it.## Scope`global > project > repo > session`. Ancestor walk: narrower scopesinherit broader ones. Pick the narrowest scope where the entry isactually reusable. Cross-project insight goes to `global`. Aproject-wide convention goes to `global/project:<id>`. A codebasequirk goes to `global/project:<id>/repo:<id>`. Session scope isephemeral and rarely worth using.## Operating rules1. Call `cx_recall` after receiving a task — query 1-3 keywords, not a sentence.2. Store as you discover, not at session end. Memory written later is memory rewritten.3. When the user corrects you, store the correction as `kind: feedback` before continuing.4. Use `cx_update` or `supersedes` when an entry is wrong. Do not let stale entries accumulate alongside corrections.5. Do not mention the context store to the user unless asked.## CLI fallback`cm stats` — store statistics. `cm serve` — start MCP on stdio.

Frequently asked questions