company-brain
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 (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki pages, update INDEX.md), query (answer from the corpus with trust weighting, save to outputs/), review (triage queue — verify / deprecate / supersede unreviewed and stale captures so wrong info never becomes context), lint (orphans / stale / contradictions / gaps), connect (suggest new wikilinks), search (quick lookup). Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, recurring-questions/, sales-objections/) instead of second-brain's flat type-prefixed raw/. Multi-author aware — every capture stamps author + timestamp + trust status. Optional auto-sync from Fathom/Gong/Granola call transcripts, Slack/email exports, CRM. Defaults t
coreyhaines31 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add coreyhaines31/makerskills --skill company-brain技能说明
name: company-brain description: 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 (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki pages, update INDEX.md), query (answer from the corpus with trust weighting, save to outputs/), review (triage queue — verify / deprecate / supersede unreviewed and stale captures so wrong info never becomes context), lint (orphans / stale / contradictions / gaps), connect (suggest new wikilinks), search (quick lookup). Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, recurring-questions/, sales-objections/) instead of second-brain's flat type-prefixed raw/. Multi-author aware — every capture stamps author + timestamp + trust status. Optional auto-sync from Fathom/Gong/Granola call transcripts, Slack/email exports, CRM. Defaults to a vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "add this person to the team brain," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "cull the team brain," "lint the company brain," "who's the internal expert on X." metadata: version: 0.3.0
/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.
Reserved dirs (never modified by company-brain): Projects/, Team/, Templates/, Drafts/.
Multi-author discipline
Every capture stamps:
source: <URL / call / email / manual entry>
author: <who added this — email or handle>
captured: YYYY-MM-DD
trust: unreviewed
Wiki pages track cumulative contributions in the ## Sources section (per source file, per author). No overwriting — always append + attribute.
Sensitivity tagging (optional but recommended):
sensitivity: internal # any team member can read
sensitivity: leadership # exec team only
sensitivity: confidential # named list only (list access in the file)
Default: internal. Query mode respects sensitivity — refuses to include confidential content unless the invoker is on the access list.
Trust levels
The other half of multi-author discipline: not everything captured deserves equal weight as context. Every structured-raw file carries a trust: field.
(The field is named trust, not status, because companies/ and decisions/ already use status: for lifecycle — prospect/customer, decided/reversed — and the two must not collide.)
| Trust | Meaning | Query treatment |
|---|---|---|
unreviewed | Captured but no human has confirmed it (default for every new capture) | Usable, but flagged — answers leaning on it note lower confidence |
verified | A human reviewed it and confirmed it's right | Full weight |
deprecated | Wrong or obsolete — kept for history only | Never used as context |
superseded | Replaced by something newer — add superseded_by: [[target]] | Never used as context; queries point to the replacement |
Deliberately an enum, not a numeric weight — teams keep a four-value field current; nobody maintains a 0–1 float.
Deprecation replaces deletion. The "never delete raw files" rule stays intact: when info turns out wrong or stale, mark it deprecated (or superseded with a pointer) instead of removing it. History is preserved; context is protected.
Trust is orthogonal to sensitivity — a file can be verified + confidential, or unreviewed + internal.
Existing vaults: files predating trust levels simply lack the trust: field — treat them as unreviewed. If the vault's CLAUDE.md schema predates trust levels, offer to add the trust spec to it on the first /cb review run (the vault's CLAUDE.md stays authoritative — extend it, don't override it).
Step 1 — Load vault config + schema
- Read
references/vault-config.mdfor the vault path (default: `${COMPANY_BRAIN