Nockbrain — Development skill for Claude Code
Memory you approve for Claude Code: a small, signed, local store of reviewed facts, recalled when you ask about the past.
How to install Nockbrain
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open nocktechnologies/nockbrain and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Nockbrain does
Memory you approve for Claude Code: a small, signed, local store of reviewed facts, recalled when you ask about the past.
Alternatives in Development
- Evolving Agents — A director agent that learns how your team works: it plans by walking your CLAUDE.md and memory as linked stat 453 ★
- Funes — Durable, searchable memory of your past agent sessions 349 ★
- Memory Question — Ask Claude's memory system questions about past work, decisions, and context 332 ★
README
NockBrain
I built this because I was tired of explaining my own decisions to Claude Code again every few sessions, and I didn't trust a memory that writes itself. NockBrain keeps a small, signed store of facts you've reviewed, on your own machine. When a prompt asks about the past, it hands the matching facts back to Claude as reference. Nothing goes in until you've read it and applied it.
[](media/nockbrain-explainer.mp4)
The one-minute explainer, its captions and the script behind it are in [media/](media/).
Who it's for
NockBrain fits one person who works with Claude Code across many sessions and is tired of explaining the same decisions, rules and corrections again. It runs on macOS and Linux, and the stock macOS `python3` is enough. Claude Code gets automatic capture and recall; Codex CLI, Gemini CLI, Cursor and Claude Desktop can recall through the MCP server. If you want a memory that fills itself with no review step, this is the wrong tool.
How it works
You decide what goes in. Point NockBrain at notes you choose, or turn on an optional Claude Code hook that queues what was said in a session each time Claude finishes a reply. Either way the candidates land in a review queue with secrets redacted, and nothing is in memory yet. You read every candidate with its kind and the line it came from, then apply the batch or discard it. Applied facts are signed, and their signed content is never rewritten.
Recall is opt-in too. When a prompt asks ab
Related Skills
Black Box
A local ledger coding agents write their reasoning into and read back before they act. Codex and Claude Code s
Agent Session Status
Live OpenCode, Claude Code, and Codex session state for Ironbar and Waybar. Provider events are reduced to a s
Reverie
Memory for coding agents. Reverie keeps the engineering conclusions your agent reaches, reviewed by you, groun
Working Memory
This is your working memory. Auto-loaded every session via CLAUDE.local.md. ~1500 word limit. Only behavior-ch
Knowl
Persistent memory for Claude Code, Cursor and Codex. Facts are typed, sourced, and retired when they change. L
Claude Rework
Local memory for Claude. Indexes your past sessions so Claude can answer questions about them for ~2.5k tokens
Related Agents
Memory Orchestrator
Biomimetic memory orchestrator. Retrieve before complex work, store high-salience facts during execution, and
Omg Code Simplifier
Bounded write-heavy simplifier. Small diffs only; cannot self-approve.
Feynman
Audit investment-research facts, figures, dates, periods, and quotes against traceable primary sources. Use be