company-brainify

Sanitize a personal knowledge brain into a shareable team brain by stripping sensitive content.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill company-brainify-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company-brainify
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/company-brainify
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill company-brainify-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personal knowledge bases accumulate sensitive material — compensation details, performance assessments, retention conversations, and candid opinions — that must be removed before the brain can be shared with a team. Clean working files alone are insufficient because git history and structured takes/facts still carry the sensitive data. ## Core Features & Use Cases - Full-scope sanitization: Scans people, meetings, dailies, companies, projects, and analysis directories plus takes and facts, removing ratings, compensation, performance assessments, and political dynamics while preserving professional identity and work history. - Gated destructive operations: Fires data-loss-gate confirmation cards before bulk content stripping and before git history rewriting with force-push, requiring an explicit typed yes. - Verification and re-audit: Runs grep triage plus retrieval-based checks (gbrain query, takes search, recall) against the tree that ships, and supports report-only periodic re-audits of an existing shared brain. - Use Case: A founder wants to stand up a shared company brain from their personal brain. The skill copies the scanned directories to a staging tree, strips sensitive content, verifies with retrieval queries, and exports a fresh sanitized repo for the team. ## Quick Start Ask the agent to sanitize my personal brain into a team-safe shared brain, stripping compensation, ratings, and performance notes before anyone else gets access.

Frequently Asked Questions about company-brainify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sanitize a personal knowledge base before sharing it with my team?

Run a full-scope sanitization pass that strips compensation, ratings, performance assessments, and retention notes from pages, takes, and facts. The skill uses retrieval-based discovery plus grep triage, edits a staging copy rather than the personal brain, and verifies with retrieval queries before export.

What content gets removed when creating a shared company brain?

Always removed: internal scores and ratings, compensation and equity details, performance assessments, departure and retention notes, management strategy, political dynamics, and personal PII. Always kept: professional identity, current projects, career arc, professional beliefs, and factual work timelines.

Does cleaning the working files remove sensitive data from git history?

No. Old commits still contain pre-sanitization versions. The skill either exports a fresh repo with new history from the sanitized staging tree, or rewrites history with git filter-repo on the shared repo only, after a verified mirror-clone backup and an explicit confirmation gate.

Why is gbrain forget not enough to remove sensitive facts?

gbrain forget only expires a fact — the row stays on the page struck through and remains served via --include-expired. Sanitization requires deleting the fact row from the page's Facts fence, re-syncing, reconciling the facts index, and verifying removal with gbrain recall --grep.

Can I audit an existing shared brain without modifying it?

Yes. The skill supports a report-only re-audit mode that re-runs the discovery, triage, and verification phases without edits, surfacing new sensitive hits for human review. This suits periodic hygiene passes on shared brains that re-accumulate sensitive data.