ai/cursor-content-team/skills/brain-memory-kb/SKILL.md
Unified ai-brain skill combining memory operations and KB query operations with promotion flow.
npx skillsauth add akshay-na/dotfiles brain-memory-kbInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Unified interface for integrated ~/ai-brain/ operations.
memory mode:
kb-query mode:
promote mode:
~/ai-brain/org/global/operator-profile/ — see _templates/operator-profile.md; PII vs secrets per brain-conventions.mdc.Promote when item is:
brain-memory-kb.When brain-conventions.mdc → Entrypoint + decision agents — KB duty applies: lookup first, then one bounded write per checkpoint; git pull --rebase on the brain clone before first write; commit/push per signing rules after. See kb-identity / project-identity for per-repo projects/<slug>/.
~/ai-brain git commits: subject from <short-hostname> + agent one Co-authored-by: trailer per brain-conventions.mdc items 6–7; hostname -s (or fallbacks). No DotMate commit-msg hook on brain clone.
~/ai-brain optional git repo)Layouts: (a) ~/ai-brain is a git clone; (b) no .git — local-only vault. Do not git init on machines meant to stay local-only. If the git root is ~/.cursor/ai-brain, use that path in -C instead of $HOME/ai-brain per brain-conventions.mdc.
Detect: git -C "$HOME/ai-brain" rev-parse --git-dir (or ~/.cursor/ai-brain) succeeds and work tree matches that root. Else skip sync.
If repo + changes under allowed paths (not skeleton): pull --rebase → path-scoped add → git commit --no-gpg-sign (message per brain-conventions.mdc) → push (no --force to default branch unless break-glass).
Clean after pull → skip commit/push.
development
Discovery + naming convention reference for typed dev/SME/QA/devops team members in any workspace folder. Primary consumer: `tech-lead` (org-tier).
devops
Automated task classification, agent selection, and state tracking. Use when routing tasks to agents, selecting pipelines, or managing task state.
testing
Use when designing scalable systems, evaluating consistency models, planning state management, making architectural decisions, or when trade-offs around coupling, failure isolation, and reversibility need explicit reasoning before implementation.
tools
CTO/tech-lead helper — split work into disjoint shard briefs with caps (instance_cap, partition_basis, determinism keys).