Capture and search thoughts against a self-hosted Open Brain over plain HTTPS, with no MCP transport involved. Use this skill in environments where Claude Code's MCP feature is disabled or the network blocks remote MCP endpoints, but the brain stack from the companion `local-brain-no-mcp` recipe is reachable on the local network. Triggers: prompts like "remember this", "save that for later", "what did I note about X", "search my brain for Y", "what thoughts touched on Z", or any explicit request to record or recall personal memory.
76
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
The canonical Open Brain stack assumes Claude Code can talk to a remote
Supabase MCP server. In environments that disable MCP entirely -- corporate
networks, air-gapped offices, restricted Claude Code builds -- that path is
not available. This skill replaces it with curl calls to a LAN-resident
Open Brain (see the local-brain-no-mcp recipe), keeping the same
capture-and-recall behavior without any MCP protocol involvement.
BRAIN_URL and BRAIN_ANON_KEY are
not set on the dev host -- this skill cannot function without them; ask
the user to follow local-brain-no-mcp's install instructions first.On each dev host that will use this skill, the user must export:
export BRAIN_URL="http://<brain-host>:8000" # Supabase Kong gateway
export BRAIN_ANON_KEY="eyJhbGciOi..." # written by setup.shIf either is missing, stop and tell the user. Do not guess values.
When the user says something like "remember X" or "save this thought":
curl -fsS -X POST "$BRAIN_URL/functions/v1/capture" \
-H "apikey: $BRAIN_ANON_KEY" \
-H "Authorization: Bearer $BRAIN_ANON_KEY" \
-H "Content-Type: application/json" \
-d '{"content":"<the thought>","metadata":{"source":"claude-code"}}'Optional metadata fields: source, tags (array of strings),
thread_id, anything else useful. The server fingerprints content and
de-duplicates -- re-capturing identical text returns the existing id.
When the user wants to recall:
curl -fsS -X POST "$BRAIN_URL/functions/v1/search" \
-H "apikey: $BRAIN_ANON_KEY" \
-H "Authorization: Bearer $BRAIN_ANON_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"<what to find>","match_count":10,"match_threshold":0.65}'match_threshold defaults to 0.7. Lower it to 0.5-0.65 for broader recall;
raise to 0.8+ for precision. Cap match_count at 100.
When the user asks "what have I been thinking about" or wants a list rather than a similarity search:
curl -fsS "$BRAIN_URL/functions/v1/list?limit=20" \
-H "apikey: $BRAIN_ANON_KEY" \
-H "Authorization: Bearer $BRAIN_ANON_KEY"docker compose ps on the brain host.ollama pull step.EMBED_DIM env was
changed after the volume was initialized. Tell the user to read the
"one-way door" section of local-brain-no-mcp's README.BRAIN_ANON_KEY is wrong or expired. Tell the user to
check supabase-docker/docker/.env on the brain host.BRAIN_ANON_KEY -- it's a long-lived JWT.6779106
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.