coreyhaines31/makerskills / skills/company-brain
company-brain
VerifiedYour 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."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.3 KB |
| references/auto-sync-sources.md | markdown | 4.7 KB |
| references/rollout.md | markdown | 1.9 KB |
| references/schema.md | markdown | 8.2 KB |
| references/vault-config.md | markdown | 4.0 KB |
references/schema.md
View on GitHub# Company Brain schema (fallback)
**Authoritative source: `<vault>/CLAUDE.md` or `<vault>/AGENTS.md`.** This file is a fallback used only when the vault has neither.
Use this as a starter kit when seeding a new team's vault.
---
## Folder structure
```
people/ → Contacts with context (CRM-lite)
companies/ → Org profiles (prospects, clients, partners)
meetings/ → Call/meeting transcripts + notes
sops/ → Standard operating procedures
decisions/ → Decision records (narrative form)
customer-language/ → Verbatim phrases from customers/prospects
recurring-questions/ → Questions asked 3+ times → pre-answered
sales-objections/ → Objection library + best responses
raw/ → Uncategorized fallback (minimize use)
wiki/ → AI-compiled knowledge base
INDEX.md → Master index
outputs/ → Saved Q&A results, briefs, deliverables
Projects/ → Team task management (DO NOT modify — project-manager owns it)
Team/ → Internal team-only files (DO NOT modify)
Templates/ → Note templates (DO NOT modify)
Drafts/ → In-progress private drafts (DO NOT modify)
```
## File naming conventions
### `people/`
- Filename: `<first-name-last-name>.md` (kebab-case, unambiguous per person)
- If two people share a name: `<name>-<company>.md` or `<name>-<role>.md`
### `companies/`
- Filename: `<company-slug>.md` (short, memorable)
### `meetings/`
- Filename: `YYYY-MM-DD-<company-or-topic>-<slug>.md`
- Examples: `2026-06-15-acme-discovery.md`, `2026-06-30-q3-planning.md`
### `sops/`
- Filename: `<team>-<process>.md`
- Examples: `sales-outbound-cadence.md`, `ops-client-onboarding.md`, `content-blog-review.md`
### `decisions/`
- Filename: `YYYY-MM-DD-<decision-slug>.md`
- Example: `2026-06-30-pricing-restructure.md`
### `customer-language/`
- Filename: `<theme-slug>.md` (grouped by theme, not per customer)
- Examples: `pricing-anchoring.md`, `willingness-to-pay.md`, `decision-triggers.md`
- Append new verbatims to existing themed files; only create new files for new themes
### `recurring-questions/`
- Filename: `<question-slug>.md`
- Example: `how-do-you-handle-migration.md`
- Include a counter at the top: `asked_count: 7`
### `sales-objections/`
- Filename: `<objection-slug>.md`
- Examples: `too-expensive.md`, `we-already-have-a-tool.md`, `no-budget-this-quarter.md`
## File front-matter (all structured dirs)
Every file starts with:
```markdown
source: <URL / call with X on YYYY-MM-DD / email from Y / manual entry>
author: <who captured this — email or handle>
captured: YYYY-MM-DD
trust: unreviewed # unreviewed / verified / deprecated / superseded
sensitivity: internal # or leadership / confidential
```
**`trust` is deliberately not named `status`** — `companies/` and `decisions/` already use `status:` for lifecycle (prospect/customer, decided/reversed). The two fields coexist and must not collide. Files with no `trust:` field (pre-trust-levels vaults) are treated as `unreviewed`.
Every `/cb review` disposition except skip stamps:
```markdown
reviewed: YYYY-MM-DD
reviewed_by: <handle>
```
Verified files: `trust: verified`. Deprecated/superseded files additionally carry:
```markdown
trust: deprecated # or superseded
superseded_by: [[replacement-page-or-file]] # superseded only
```
For `people/` files, extend with:
```markdown
role: <current role>
company: <current company>
last_touch: YYYY-MM-DD
tags: [customer, prospect, partner, investor, alumni, ...]
```
For `companies/` files, extend with:
```markdown
industry: <industry>
size: <headcount range>
status: [prospect, customer, churned, partner, competitor]
opportunity_size: <ARR / TCV range>
last_touch: YYYY-MM-DD
account_owner: <team member>
```
For `meetings/` files, extend with:
```markdown
attendees: [name1, name2, name3]
company: <company slug if external>
duration_min: <int>
recording_url: <if available>
```
For `sops/` files, extend with:
```markdown
owner: <team member responsible>
last_reviewed: YYYY-MM-DD
review_cadence: <quarterly | annually | ad-hoc>
```
For `decisions/` files, extend with:
```markdown
deciders: [name1, name2]
review_by: YYYY-MM-DD # scheduled re-evaluation
status: [decided, in-effect, reversed, superseded]
```
## wiki/ page format
Same as `second-brain`:
```markdown
# Topic Name
Brief summary (2–3 sentences).
## Key Concepts
- Concept with explanation
## Details
Main content organized by subtopic.
## Connections
- [[Related Topic]] — how it connects
## Sources
- `people/jane-doe.md` (added by @alex, 2026-06-30) — role + context
- `meetings/2026-06-15-acme-discovery.md` (added by @sam) — objection notes
- `companies/acme.md` (added by @alex, updated by @sam) — deal state
```
**Cite by source file + author + optional date.** Multi-author attribution is the discipline that makes the vault trustworthy at team scale.
## wiki/INDEX.md format
```markdown
# Wiki Index
## Sales
- [[Acme Corp Deal]] — Active Q3 opportunity, $180K TCV
- [[Pricing Objections]] — Standard responses to price pushback
## Customers
- [[Beta Customer Feedback Themes]] — Aggregated themes from Q2 feedback
## Ops
- [[Client Onboarding Flow]] — 6-step process
## Product
- [[Roadmap Q3]] — Prioritized initiatives
## Team & People
- [[Team Directory]] — Who does what
- [[Key Contacts at Partners]] — Named POCs at partner orgs
## Decisions
- [[Pricing Restructure June 2026]] — Rationale + expected outcome + review date
## Playbooks
- [[Sales Outbound Playbook]] — Cadence, templates, escalation
```
Extend categories as the team's brain matures.
## Sensitivity levels
| Level | Access |
|---|---|
| `internal` | Any team member (default) |
| `leadership` | Named leadership list only (list in `Team/leadership.md`) |
| `confidential` | Named list per file (list in file front-matter or `Team/confidential-access.md`) |
Wiki pages inherit the *highest* sensitivity of any source. If a wiki page cites 4 `internal` sources and 1 `confidential`, the wiki page is `confidential`.
## Trust levels (`trust:`)
| Trust | Meaning | Query treatment | Compile treatment |
|---|---|---|---|
| `unreviewed` | No human has confirmed it (default for new captures; also how files with no `trust:` field are treated) | Usable but flagged — answers note lower confidence | Included; pages mostly built on it get a warning callout |
| `verified` | Human-reviewed and confirmed | Full weight | Included |
| `deprecated` | Wrong or obsolete | Never used as context | Excluded; noted in Sources with `reviewed` date + `reviewed_by` |
| `superseded` | Replaced (`superseded_by: [[target]]`) | Never used; queries point to the replacement | Excluded; Sources link to replacement |
Trust is orthogonal to sensitivity. Trust changes happen through `/cb review` (the human triage pass, which respects sensitivity — reviewers only see files at or below their level) — capture always starts at `unreviewed`.
## Rules
- **One page per concept** — not per source. Multiple raw files about the same customer merge into one wiki page.
- **Use `[[wikilinks]]`** for all internal references
- **Keep pages focused** — split if >500 words
- **INDEX.md is the root** — keep current
- **Connections section is mandatory** — every page links to ≥1 other page
- **No orphan pages**
- **Preserve nuance** — don't flatten contradictions between authors' captures; note the disagreement
- **Multi-author attribution required** in Sources sections
- **Sensitivity respected** in query mode
- **Deprecate, don't delete** — wrong/stale info gets `trust: deprecated` (or `superseded` + pointer), never removed
- **Trust respected end-to-end** — deprecated/superseded content never used as context in query or compile
## Publishing (same as second-brain)
Use pandoc + shared stylesheet at `~/.local/share/makerskills/render.css`:
```bash
pandoc "outputs/<file>.md" \
--css ~/.local/share/makerskills/render.css \
--metadata title="<title>" \
--pdf-engine=xelatex \
-o "outputs/<file>.pdf"
```
Company brain outputs commonly leave the vault as: client-facing briefs, quarterly reviews, sales enablement PDFs, onboarding docs. Same rendering pattern as second-brain.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |