Index of every page on this site: llms.txt
All skills
coreyhaines31 avatar

/company-brain

@4cb94db
Run it yourself

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."

Use this Skill: https://skilld.dev/gh/coreyhaines31/makerskills/company-brain

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesrollout.md

≈483 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Rolling out a company brain

Adoption beats announcement. Launching to the whole company on day one creates a pile of unreviewed captures you spend months culling, and people stop trusting answers before the brain has earned any trust.

Phase 1 — Pilot (2–4 weeks)

  • One workflow, seeded per "Start narrow" in vault-config.md.
  • One or two people who live in that workflow daily and will actually run /cb review.
  • Capture everything relevant to the workflow; don't capture outside it yet.
  • Hold a weekly review pass. If it slips, fix that before anything else; it's the habit everything else depends on.

Phase 2 — Prove value

Move on only when all three are true:

Signal Bar
Queries answered The pilot group asks it real questions weekly and gets useful answers
Review cadence Weekly review has held for 3+ weeks; the unreviewed queue isn't growing
Trust Answers cite verified sources often enough that people stop double-checking

If a signal misses, narrow rather than widen: fewer dirs, fewer sources, a tighter workflow.

Phase 3 — Expand

  • Add one workflow (and its dirs) at a time, with an owner who runs review for it.
  • Add people in the order they'll contribute, not by org chart.
  • Turn on auto-sync (call transcripts, Slack, CRM) per workflow only after manual capture has proven which content is worth keeping. Auto-sync on day one multiplies the review queue before anyone knows what good looks like.
  • Set sensitivity levels before leadership or confidential content arrives, not after.

Anti-patterns

  • The big launch. All dirs, all people, all syncs at once. Review can't keep up, so trust never forms.
  • Capture without review. A growing unreviewed queue is the leading indicator of a brain nobody trusts.
  • Measuring pages, not answers. Page count is vanity. Questions answered without asking a person is the metric.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning8d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    The 'company-brain' skill is a knowledge management system that aggregates team data from external sources like Slack, email, and meeting transcripts. Its primary security risk is indirect prompt injection, as malicious instructions hidden within ingested data could influence the agent during query or review modes. It also uses shell commands for git synchronization and document rendering.

  • Socket8d

    No alerts

  • Snyk10d

    Risk: MEDIUM · 1 issue

Signed by skilld at 4cb94db. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
metadata
{
  "version": "0.4.0"
}

README badge

README badge for coreyhaines31/makerskills/company-brain