| name | teamkb |
| description | Runs an end-of-session capture sweep for the governed knowledge brain: reviews what
happened, classifies insights, checks for conflicts, and proposes governed memories
via the teamkb MCP tools. Admin capture workflow that complements the one-shot
/brain-save. Use when wrapping up a session with team-relevant discoveries, or
when importing existing docs into the brain. Trigger with "/teamkb", "capture this
session", or "sweep for team knowledge".
|
| allowed-tools | Read, Glob, Grep, Agent |
| version | 1.0.0 |
| author | Intent Solutions <jeremy@intentsolutions.io> |
| license | Apache-2.0 |
| compatibility | Designed for Claude Code; requires the intent-brain plugin with admin role (TEAMKB_ROLE=admin) for the write tools |
| tags | ["brain","capture","governance","knowledge","admin"] |
| argument-hint | [capture | import | status | review] |
TeamKB — governed team-knowledge capture sweep
Capture team memory at the end of a session: review what happened, classify the
insights worth keeping, check them against existing memories for conflicts, and queue
them for governance review. This is the multi-step, subagent-driven capture workflow
that sits alongside the one-shot /brain-save.
Overview
The brain captures knowledge, validates it through deterministic governance policies,
and shares it across the team via qmd. This skill drives the capture side: it uses
the teamkb MCP tools to propose candidates (never writing governed state directly —
the curator promotes after policy checks) and delegates the judgment-heavy steps to
specialized subagents.
Prerequisites
- The
intent-brain plugin is installed with admin role (TEAMKB_ROLE=admin), so
the write MCP tools (teamkb_propose, teamkb_status) are registered. A member
install is read-only and cannot capture.
- For conflict checking, the brain has an existing corpus to compare against.
Authentication
In team mode, the write tools reach the brain API over the tailnet with the admin's
per-user bearer token (TEAMKB_API_TOKEN), sent as an Authorization: Bearer header.
A non-admin token is rejected server-side with 403. Never hardcode the token; supply
it via env or a headersHelper. In local mode no token is needed.
Available MCP tools
- teamkb_propose — capture a single insight as a candidate
{ title, content, category?, filePaths? }. Writes to the spool; the governance pipeline decides promotion.
- teamkb_import — bulk-import files as candidates
{ glob, basePath? }.
- teamkb_status — counts by lifecycle state, category, and recent rejection feedback.
- teamkb_transition — change a memory's lifecycle state
{ memoryId, to, reason, actor }.
Instructions
Step 1: Review the session
Use Read, Glob, and Grep to gather what changed and what was decided — the diff,
the files touched, and any decisions stated in the conversation. Delegate the sweep to
the @teamkb-scout subagent (via Agent) when the session is large.
Step 2: Classify each candidate insight
