Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

Company Brain (Team Knowledge Base)

A shared, AI-ready team knowledge base of people, companies, meetings, SOPs and decisions that Claude can query on your team's behalf.

Docs & OfficeIntermediate★ 839⑂ 69AI score 8/10Last updated: Sep 4, 2026

What it does

  • Routes every capture into purpose-built folders: people/, companies/, meetings/, sops/, decisions/, customer-language/, recurring-questions/, sales-objections/.
  • Compiles raw notes into interlinked wiki pages, updates INDEX.md, and writes Sources sections with per-author attribution.
  • Seven modes: capture, compile, query, review, lint, connect, search.
  • Stamps author, captured, trust (unreviewed/verified/deprecated/superseded) and sensitivity (internal/leadership/confidential) on every file, so multi-author vaults keep both confidence weighting and access control.
  • Never deletes: wrong or stale info is deprecated or superseded, preserving history while excluding it from answers.

Who it's for

  • Startups and small teams whose sales, CS and ops knowledge is scattered across people and tools.
  • Teams already living in Obsidian or Git-backed markdown who want an alternative to Notion AI / Glean.
  • Team leads who want meeting notes, SOPs and decision records in a form an AI can actually use.

Examples

  1. /cb capture — paste a Fathom call transcript; it lands in meetings/2026-06-15-acme-discovery.md with author, date and trust metadata.
  2. /cb query what does the team know about Acme's pricing objection? — answers from company, meeting and objection files, and warns "low confidence" when most sources are unreviewed.
  3. /cb review — walks the unreviewed queue item by item to verify/deprecate/supersede, then offers to recompile affected wiki pages.
  4. /cb lint — flags accounts untouched for 6+ months, questions asked 5+ times with no SOP, and a contributor doing over 80% of captures.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/coreyhaines31/makerskills/HEAD/skills/company-brain/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/company-brain folder from the GitHub repo coreyhaines31/makerskills into my ~/.claude/skills/company-brain/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/coreyhaines31/makerskills.git && mkdir -p ~/.claude/skills && cp -r makerskills/skills/company-brain ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and clone the repo: git clone https://github.com/coreyhaines31/makerskills.git
  2. Copy the skill into your Claude skills folder: mkdir -p ~/.claude/skills && cp -r makerskills/skills/company-brain ~/.claude/skills/
  3. Create the team vault: mkdir -p ~/Documents/CompanyBrain. To use another location, set the COMPANY_BRAIN_VAULT environment variable.
  4. Restart Claude Code and type /company-brain or /cb to confirm the skill is loaded.
  5. Try a first capture: run /cb capture, paste a meeting note or contact bio, and check the reported file path.
  6. Once a few files exist, run /cb compile to build the wiki, then schedule /cb review weekly.
  7. (Optional) For team sharing, turn the vault into a git repo pushed to GitHub, and always git pull --rebase --autostash before working in it.