Company Brain
Your team's shared, AI-ready knowledge base, people, companies, meetings, SOPs, and...
Install
npx skills add coreyhaines31/makerskills --skill company-brain -g -a claude-code -y- Repository
- coreyhaines31/makerskills880
- Category
- AI and agents
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Your team's shared, AI-ready knowledge base, people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain, personal notes go there, not here. Modes, capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.
/company-brain, Team-shared AI-ready knowledge base
Company Brain (n.): Your team's shared, AI-ready knowledge base, people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf.
Team-scope sibling to second-brain (personal-scope). Same core compile → wiki → outputs pattern; different raw schema optimized for multi-author, sales-heavy, ops-heavy team use.
Also the operational backbone for the Company Brain Setup productized service (was previously called "Second Brain as a Service"; renamed to match the skill).
Mental model
Three layers, same as second-brain, but the raw/ layer is structured, not flat:
raw/ → wiki/ → outputs/
(structured (compiled (generated
by category) interlinked) artifacts)
Structured raw/ dirs (each is its own top-level folder in the vault):
| Dir | What lives here |
|---|---|
people/ | Contacts with context, CRM-lite. One markdown file per person. |
companies/ | Org profiles, last touchpoint, opportunity size, status. One file per company. |
meetings/ | Call/meeting transcripts + notes. Naming: YYYY-MM-DD-<company-or-topic>-<slug>.md. Auto-sync source. |
sops/ | Standard operating procedures. Named: <team>-<process>.md (e.g., sales-outbound-cadence.md). |
decisions/ | Decision records (narrative form; decide skill's structured form is different). |
customer-language/ | Verbatim phrases from prospects/customers/users. Fuels copy, headlines, objections. |
recurring-questions/ | Questions asked 3+ times across calls. Each becomes a pre-answered SOP/FAQ/script. |
sales-objections/ | Library of objections + best responses. Assembled into sales scripts. |
raw/ | Legacy / uncategorized captures (fallback bucket, minimize use). |
wiki/, outputs/, and INDEX.md work the same as second-brain.
