brain
/brain
Tune adaptive recall with brain profiles — inspect profiles and posteriors, manage lifecycle (activate/deactivate/archive/reset), emit feedback (brain.feedback / brain.auto_feedback) to shift recall weights, and wire actors to profiles via bind/unbind/resolve/bindings. Use whenever recall behavior feels off, a new tuning profile is needed, or you need to confirm which profile serves a given caller.
- Author
- ohdearquant ↗
- Repository
- khive ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Tune adaptive recall with brain profiles — inspect profiles and posteriors, manage lifecycle (activate/deactivate/archive/reset), emit feedback (brain.feedback / brain.auto_feedback) to shift recall weights, and wire actors to profiles via bind/unbind/resolve/bindings. Use whenever recall behavior feels off, a new tuning profile is needed, or you need to confirm which profile serves a given caller.
Original author description
Tune adaptive recall with brain profiles — inspect profiles and posteriors, manage lifecycle (activate/deactivate/archive/reset), emit feedback (brain.feedback / brain.auto_feedback) to shift recall weights, and wire actors to profiles via bind/unbind/resolve/bindings. Use whenever recall behavior feels off, a new tuning profile is needed, or you need to confirm which profile serves a given caller.
How it works
- The pattern
- Anti-patterns
SKILL.md preview
---
description: Tune adaptive recall with brain profiles — inspect profiles and posteriors, manage lifecycle (activate/deactivate/archive/reset), emit feedback (brain.feedback / brain.auto_feedback) to shift recall weights, and wire actors to profiles via bind/unbind/resolve/bindings. Use whenever recall behavior feels off, a new tuning profile is needed, or you need to confirm which profile serves a given caller.
---
# Tune adaptive recall with brain profiles
The brain pack is the adaptive layer that adjusts how `memory.recall` ranks results. It holds
Bayesian profiles whose posteriors shift with every feedback signal. The verbs are
`brain.create_profile`, `brain.profiles`, `brain.profile`, `brain.activate`, `brain.deactivate`,
`brain.archive`, `brain.reset`, `brain.feedback`, `brain.auto_feedback`, `brain.resolve`,
`brain.bind`, `brain.unbind`, and `brain.bindings`. Per-verb param detail is one `help=true` away:
`request(ops="brain.feedback(help=true)")`.
## The pattern
### 1. Orient: which profile is active and who does it serve?
Start every session with a single batch call to see the current state:
```
request(ops="[brain.profiles(lifecycle=\"active\"), brain.resolve(consumer_kind=\"recall\")]")
```
The built-in profile is `balanced-recall-v1`. Inspect current posterior values (relevance,
salience, temporal weights) with:
```
request(ops="brain.profile(profile_id=\"balanced-recall-v1\")")
```
### 2. Feed signal back after recall
After `memory.recall` returns results, emit a signal on each result you can evaluate. The
convenience verb handles the common case:
```
request(ops="brain.auto_feedback(query=\"<the recall query>\", results=[{\"id\":\"<uuid-1>\"}], target_id=\"<uuid-1>\", signal=\"implicit_positive\")")
```
Both `query` (the recall query that produced the results) and `results` are required. A supplied
signal also requires `target_id` to exactly match one result; rank position never creates a
judgment. Omit `signal` to abstain without emitting a feedback event. For direct per-item control, use
`brain.feedback`. Eight signals are available: `useful`,
`not_useful`, `wrong`, `explicit_positive`, `explicit_negative`, `implicit_positive`,
`implicit_negative`, `correction`. Batch across multiple results in one call:
```
request(ops="[brain.feedback(id=\"<uuid-1>\", signal=\"useful\"), brain.feedback(id=\"<uuid-2>\", signal=\"not_useful\")]")
```
### 3. Manage lifecycle when behavior drifts
Posteriors that have drifted can be reset without losing event history:
```
request(ops="brain.reset()")
```
To pause live updates while inspecting a profile, deactivate it first:
```
request(ops="brain.deactivate(profile_id=\"balanced-recall-v1\")")
```
Then reactivate when ready:
```
request(ops="brain.activate(profile_id=\"balanced-recall-v1\")")
```
To retire a profile permanently, deactivate it before archiving — the runtime rejects a direct
`active` to `archived` transition:
```
request(ops="brain.deactivate(profile_id=\"balanced-recall-v1\") | brain.archive(profile_id=$prev.profile_id)")
```
### 4. Wire a new profile to actors or namespaces
When you need a separate tuning profile for a specific actor or context, create it (starts
`Inactive`), activate it, then bind it:
```
request(ops="brain.create_profile(name=\"research-v1\", consumer_kind=\"recall\")")
request(ops="brain.activate(profile_id=\"research-v1\")")
request(ops="brain.bind(profile_id=\"research-v1\", actor=\"researcher\", consumer_kind=\"recall\")")
```
Confirm the binding resolves correctly before relying on it:
```
request(ops="brain.resolve(consumer_kind=\"recall\", actor=\"researcher\")")
```
Resolution priority: exact (actor+namespace+consumer_kind) then namespace wildcard, actor
wildcard, and finally global wildcard. `NotFound` means no binding covers that combination.
## Anti-patterns
- **Ambiguous prefix in `brain.feedback`.** `id` accepts a full UUID or a globally unique
hex prefix of at least eight characters; prefer the full UUID from recall when available.
- **Archiving the only active profile.** If `balanced-recall-v1` is the sole active binding for
`recall`, archiving it makes `brain.resolve(consumer_kind="recall")` return `NotFound` for all
callers until a replacement is bound and activated.
- **Calling `brain.unbind()` with no args.** At least one filter (`profile_id`, `actor`,
`namespace`, or `consumer_kind`) is required. A bare call is rejected.
- **Resetting mid-session.** `brain.reset` discards posteriors accumulated in the current session.
Reset between sessions or after deliberate behavioral experiments, not while actively recalling.
- **Binding before activating.** A binding to an `Inactive` profile is valid but the profile will
not receive live updates until `brain.activate` is called.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ohdearquant/khive | 84 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| coco-research/coco | 100 | MIT |
| jeremylongshore/bobs-big-brain-registrar | 100 | Apache-2.0 |
| onetest-ai/echo | 100 | AGPL-3.0 |
| johantor/brain | 100 | Apache-2.0 |
| guangshinhaha/shinstack | 100 | MIT |
| atlasatakahraman/knowledge-skeleton | 100 | GPL-3.0 |
| kayossouza/brain-template | 100 | MIT |
Database snapshot: 13.11.2026 · package version 1342c4b7140f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 98claude-brain-builder
Build (or rebuild, or verify) the user's claude-brain transcript database at ~/claude-brain — markdown transcripts, catalog, a single-file SQLite vector index, and an always-on local recall server — and install its three operating skills (brain-architect, brain-recall,… - 100brain-recall
Recall everything brain knows about one specific entity — current profile, full bitemporal timeline, graph neighbours, and unresolved disagreements. Use when the user names a person/company/thing and asks "tell me about them", "what's their history", or "what do we still… - 94captn-brain
Use for CaptN-BRAIN CLI token/context optimisation. Deterministic first. - 100brain-recall
Persistent recall over the user's saved Claude and Claude Code transcripts in ~/claude-brain, via an always-on vector (RAG) search server that answers in milliseconds. Use when the user asks "what did we decide about…", "how did we do…", "last time we…", "do you remember…",… - 87project-brain
Triggers (all require explicit user request — do NOT activate just because a brain/ folder exists): (1) The user wants to set up project-level memory ("set up project brain", "scaffold project context", "init project brain", "建项目脑"). (2) The user is in a directory containing… - 100team-brain-sync
Regenerate BRAIN.md and optionally generate .cursorrules and AGENTS.md from team brain entries. Use when user says 'sync', 'regenerate', 'update brain', or '/team-brain sync'.