# Graymatter Context

> Compile bounded, task-specific GrayMatter context and inspect authorized procedures or retrieval receipts. Use when a task needs grounded prior context, a reusable method, or an explanation of why particular memory was selected.

- Skill: `thedixitjain/graymatter-context` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add thedixitjain/graymatter-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/graymatter-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: thedixitjain (https://skillmd.com/u/thedixitjain)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/thedixitjain/graymatter-context

---



# GrayMatter Context

Compile the smallest useful authorized context for the current task instead of loading broad memory exhaust.

## Workflow

1. State the current task clearly and call `context_compile` with a realistic token budget.
2. Prefer the compiled ContextPage summary, selected items, hydration pointers, policy result, and receipt reference over raw memory dumps.
3. Respect retrieval policy. If the compiled result indicates low confidence, stale context, partial coverage, conflict, retry, clarification, or denial, follow that action before answering confidently.
4. Call `procedure_search` when a repeatable methodology may already exist. Use an authorized high-confidence procedure when it fits the task; do not invent tenant filters.
5. Call `retrieval_receipt_get` when the user asks why context was selected, which sources contributed, or how confidence, freshness, coverage, and policy were evaluated.
6. Cite the receipt ID in the response when provenance or selection rationale materially matters.

## Context discipline

- Keep temporary conversational context in the conversation. Save only durable information through the GrayMatter memory skill.
- Do not request or pass tenant, organization, owner, user, role, permission, or ACL identifiers.
- Do not hydrate every pointer by default. Retrieve more detail only when the current task requires it.
- Treat authorization failures as final for that identifier and do not probe for cross-tenant alternatives.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/ValkyrLabs/GrayMatter/skills/graymatter-context/SKILL.md`