Menu
Use when capturing, recalling, reviewing, or consolidating durable project memory across sessions, especially decisions, constraints, procedures, and episodes that must retain provenance and freshness.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when creating or editing a plugin for a multi-host GitHub Copilot / APM / Claude Code marketplace — required manifests, the plugin.json ⇆ apm.yml mirroring rule, portable env-var and install conventions, component layout, and the catalog entry.
Use when every unit of a corpus must be accounted for rather than merely searched — auditing a document set, log archive, or file tree with provable coverage and gaps split into truly absent versus undecidable.
Use when searching source code: text/regex (ripgrep), structural/AST patterns (ast-grep, semgrep), symbol definitions/references/callers (LSP, GNU Global, ctags), when/why code changed (git history), structural rewrites (comby), or size/complexity (tokei, scc).
Use when searching non-code corpora: query JSON/YAML/config (jq, yq, gron), tabular data files (duckdb, sqlite-utils), or content inside PDFs/Office/archives (rga, pandoc, pdftotext).
Use when deciding WHERE a piece of guidance should live — always-on memory (CLAUDE.md / AGENTS.md), a path-scoped rule, an on-demand skill, a subagent, an MCP server, or a deterministic hook — and how to keep the always-on budget small.
Use for semantic search over a markdown corpus when keywords aren't enough (you know the meaning, not the exact words), or hybrid semantic plus lexical search when both meaning and exact terms matter. Index once, then query.
| name | memory-workflows |
| description | Use when capturing, recalling, reviewing, or consolidating durable project memory across sessions, especially decisions, constraints, procedures, and episodes that must retain provenance and freshness. |
| license | MIT |
| compatibility | Python 3 is required for the bundled validator/provider adapter. MemPalace is optional and must be installed separately for provider-backed recall. |
| metadata | {"author":"Mark Beacom","version":"0.2.0"} |
| allowed-tools | Read Grep Glob Write Bash(python3:*) Bash(mempalace:*) Bash(git:*) |
Use durable memory for reviewed information that should outlive one task, not as a transcript dump or a replacement for current repository evidence.
| Need | Use |
|---|---|
| Current task state and next action | context-handoff |
| Meaning-based search across a document corpus | local-rag |
| Prior decisions, constraints, procedures, or bounded episodes | durable memory |
| Exact current implementation or history | lexical/code-intelligence/Git |
MemPalace is an optional external provider for verbatim storage and recall.
context-kit keeps the memory contract, review policy, and verification gates
provider-neutral.
review: proposed. Promote them to accepted only after
checking the evidence with the append-only record-state operation; never
edit an already captured artifact.scripts/memory-provider.py validate, then persist with
capture. Provider archival is optional.Do not silently harvest whole transcripts, secrets, unverified speculation, temporary debugging noise, or information whose retention has not been approved.
verify-before-trust to stale, consequential, or conflicting claims.Use the composition recall then pin: memory locates the likely decision or episode; repository/filesystem evidence establishes what is true now.
Run review before relying on old records. Consolidation is propose-only:
supersedes edge;Never destructively rewrite the only evidence for a remembered claim.
Claude hooks ship inert. When explicitly enabled, they queue lifecycle payloads under the project-isolated memory home for manual review:
export CONTEXT_KIT_MEMORY_PROJECT=owner/repository
export CONTEXT_KIT_MEMORY_AUTO_CAPTURE=true
Hooks never create reviewed memory records or mutate a provider palace. Review a
queued payload, create a memory-v1 artifact, run explicit capture, and then
run sync-provider --apply when provider recall should change. GitHub Copilot
and APM do not run Claude hooks.
references/memory-contract.md — record schema and evidence rules.references/provider-mempalace.md — provider setup, isolation, and CLI.references/provider-qualification.md — provider qualification criteria
and the current decision table for local records, MemPalace, and Memora.references/retrieval-and-review.md — recall, freshness, cues, and
consolidation.references/automation.md — opt-in hook behavior and host boundaries.templates/memory.md — canonical record template.../../scripts/memory-provider.py — deterministic validator and adapter.