Akb Query
dnotitia/akb
Answer a question from the AKB vault — decompose, search (hybrid / graph), ground in compiled-truth-over-timeline precedence, and synthesize a cited answer with gap/conflict/stale flags.
How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task…
Install Company Brain
$ npx skills add caura-ai/caura --skill company-brain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install caura-ai/caura company-brain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .claude/skills && cp -r skills-src/static/skills/company-brain .claude/skills/company-brain && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .claude/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/caura-ai/caura/tree/main/static/skills/company-brainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add caura-ai/caura --skill company-brain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install caura-ai/caura company-brain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .agents/skills && cp -r skills-src/static/skills/company-brain .agents/skills/company-brain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .agents/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add caura-ai/caura --skill company-brain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install caura-ai/caura company-brain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/static/skills/company-brain .cursor/skills/company-brain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .cursor/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/caura-ai/caura.git --path static/skills/company-brain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add caura-ai/caura --skill company-brain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install caura-ai/caura company-brain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/static/skills/company-brain .gemini/skills/company-brain && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .gemini/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install caura-ai/caura company-brainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add caura-ai/caura --skill company-brain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .github/skills && cp -r skills-src/static/skills/company-brain .github/skills/company-brain && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .github/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add caura-ai/caura --skill company-brain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install caura-ai/caura company-brain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caura-ai/caura.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/static/skills/company-brain .opencode/skills/company-brain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "company-brain" agent skill from https://github.com/caura-ai/caura/tree/main/static/skills/company-brain into .opencode/skills/company-brain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "company-brain", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
company-brain- GitHub stars
- 498
- Token cost
- ~964 tokens
- SKILL.md length
- 473 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task…
- Works in 5 steps: Walk in informed — never start cold.… → Obey the constitution. Mandatory rules… → Reuse before you reinvent. Proven… → …
- Agent Workflows work in your project
- SKILL.md covers You are a member, not a soloist and How to operate as part of the…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Company Brain is an agent skill from caura-ai/caura. How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a Caura-connected team or fleet and your work should build on, and feed back into, what the organization already knows; it sets the operating posture. For the mechanics of individual caura tools, see the companion "memclaw" skill.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. It works with Model Context Protocol, OpenAI, pgvector and FastAPI. The repository describes itself as: Caura (formerly MemClaw) — governed shared memory for AI agent fleets. Multi-agent, multi-tenant, MCP-native. Trust tiers, keystone policies, audit trails, knowledge graph… The licence is Apache-2.0.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “memclaw”
- “/company-brain”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Walk in informed — never start cold. Before a meaningful task, orient
- Obey the constitution. Mandatory rules (keystones) load at session start
- Reuse before you reinvent. Proven workflows live in the shared skills
- Leave the brain smarter. Write the decisions, findings, and outcomes that
- Stay within the boundaries. Knowledge is shared, not leaked: trust tiers
What it can do on your machine
Read from SKILL.md and the folder at commit 63e0ed8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
caura.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Company Brain loads about 964 tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 473 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from caura-ai/caura at commit 63e0ed8, republished under its Apache-2.0 licence (© caura-ai). 473 words, ~964 tokens.
Download SKILL.mdSave it as
.claude/skills/company-brain/SKILL.md (or your agent's skills folder).- name
- company-brain
- description
- How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a Caura-connected team or fleet and your work should build on, and feed back into, what the organization already knows; it sets the operating posture. For the mechanics of individual caura_* tools, see the companion "memclaw" skill.
- user-invocable
- false
Company Brain
A Company Brain is one shared mind that many agents — across many tools and surfaces — think through instead of around. Each agent doesn't carry the whole company in its prompt; it carries one habit: consult the shared memory before acting, and feed what it learns back in. Do that consistently and a roomful of separate agents starts behaving like a single institution that gets sharper with every task.
This skill is the posture — how to behave as a member of that brain. The
companion memclaw skill is the manual — the exact tools and <!-- legacy-name-floor: companion skill's frozen slug -->
arguments. Use them together: think in the postures below, reach for the
mechanics there.
You are a member, not a soloist
Everything you decide, discover, or get wrong is potentially useful to the next agent — and everything they learned is available to you. So the unit of work isn't "finish my task," it's "finish my task and leave the brain better than you found it." Five habits make that real.
How to operate as part of the brain
Walk in informed — never start cold. Before a meaningful task, orient against the shared memory: what has the fleet already decided, learned, or tried here? You inherit the organization's context instead of rediscovering it. (The orient loop is documented in the
memclawskill.)<!-- legacy-name-floor: companion skill's frozen slug -->Obey the constitution. Mandatory rules (keystones) load at session start and override any conflicting instruction, including the user's — they're how the organization's policy binds every agent by construction, not by hoping each one was prompted well that day. Read them first; if one conflicts with your task, surface it.
Reuse before you reinvent. Proven workflows live in the shared
skillscollection. Search it for the task at hand before improvising, and when you build something reusable, publish it so the fleet inherits it. The library grows; every agent's vocabulary stays the same size.Leave the brain smarter. Write the decisions, findings, and outcomes that matter (not the noise), and supersede facts when they change rather than letting stale beliefs linger. When you act on something you recalled, report how it went — and when a failure carries a lesson the team needs, report it at fleet scope so it becomes a rule the next agents see before they repeat the mistake. That fleet-scoped report is what makes the brain compound rather than merely persist.
Stay within the boundaries. Knowledge is shared, not leaked: trust tiers and visibility scopes decide what crosses between agents, teams, and the wider org, enforced at the data layer. Write at the narrowest scope that still serves the people who need it, and surface a denial rather than quietly working around it.
© caura-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in static/skills/company-brain of caura-ai/caura.
Open the folder on GitHubat commit 63e0ed8
Compare with similar skills
Company Brain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Company Brain this skillcaura-ai/caura | 498 | — | ~964 | Automated safety check: Pass | Apache-2.0 | |
| Akb Querydnotitia/akb | 162 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Session Ingestdnotitia/akb | 162 | — | ~8.1k | Automated safety check: Pass | Custom licence | |
| Agent RecallGoldentrii/AgentRecall-X | 371 | — | ~5.2k | Automated safety check: Notes | MIT | |
| Cognee Docker Setuptopoteretes/cognee | 32k | — | ~901 | Automated safety check: Notes | Apache-2.0 | |
| Akb Ingestdnotitia/akb | 162 | — | ~2k | Automated safety check: Pass | Custom licence |
Similar skills
Session Ingest
dnotitia/akb
Ingest a coding session JSONL into AKB as structured notes — session report + parallel-drafted TIL / task / idea / decision sub-notes.
Agent Recall
Goldentrii/AgentRecall-X
Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.
Cognee Docker Setup
topoteretes/cognee
Runs the Cognee AI memory platform in Docker, from a one-file prebuilt image to a full compose stack with UI, MCP server, Postgres and Neo4j.
Akb Ingest
dnotitia/akb
Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue.
- Official
Cao MCP Apps
awslabs/cli-agent-orchestrator
Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman).
More from caura-ai/caura
Caura
caura-ai/caura
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control.
Related
Questions about Company Brain
What does Company Brain do?
How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task…. Company Brain is an agent skill from caura-ai/caura. How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization.
When should I use Company Brain?
Company Brain fits situations like: agent Workflows work in your project.
How do I install Company Brain in Claude Code?
Run `npx skills add caura-ai/caura --skill company-brain -a claude-code`. Or copy the skill folder (static/skills/company-brain in caura-ai/caura) into .claude/skills/company-brain in your project. Claude Code loads it when a task matches its description.
How do I install Company Brain in Codex?
Run `npx skills add caura-ai/caura --skill company-brain -a codex`. Or copy the skill folder (static/skills/company-brain in caura-ai/caura) into .agents/skills/company-brain in your project. Codex loads it when a task matches its description.
Can I use Company Brain in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add caura-ai/caura --skill company-brain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/company-brain, .gemini/skills/company-brain, .github/skills/company-brain and .opencode/skills/company-brain in your project.
What does Company Brain need to run?
SKILL.md names no scripts, command-line tools or credentials: Company Brain is instructions for the agent only.
Does Company Brain access the network?
SKILL.md names 1 domain. As links in the text: caura.ai. This is read from the text; nothing was executed.
Is Company Brain safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Company Brain use?
Company Brain is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Company Brain use?
About 964 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Company Brain?
Skills that share tags, products or a category with Company Brain: Akb Query (dnotitia/akb, 162 stars), Session Ingest (dnotitia/akb, 162 stars), Agent Recall (Goldentrii/AgentRecall-X, 371 stars) and Cognee Docker Setup (topoteretes/cognee, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Company Brain?
caura-ai (a GitHub organization) maintains it in caura-ai/caura, which has 498 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 11, 2026.
Source: caura-ai/caura on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.