inbrainfun/inbrain/cold-start
Claude Code and agent skill by inbrainfun/inbrain
- community
Checking that the SKILL.md file is still in the repository.
Day-one data bootstrapping for a new brain. Sequences the highest-leverage data sources to go from empty brain to useful brain in one session. Uses ClawVisor for safe credential handling — the agent never holds raw API keys. Covers Gmail import, calendar sync, contacts seeding, X/Twitter archive, conversation imports, and file archives. Use when a user has just finished inbrain setup and asks "now what?"
Install
npx vskill@latest install inbrainfun/inbrain/cold-startSKILL.md
The same SKILL.md was published earlier as inbrainfun/inbrain/cold-start.
Cold Start — Day-One Brain Bootstrapping
You have a working brain. Search works. Now what?
An empty brain is a static database. A brain with your email history, calendar, contacts, conversations, and social media is a live context membrane that makes every future interaction smarter. This skill sequences the highest-leverage data sources to get you from zero to useful in one session.
Contract
- Every import phase is gated on user consent (ask-user pattern) before proceeding.
- Google/social API access goes through ClawVisor. The agent never holds raw OAuth
tokens or API keys. This is a safety requirement, not a preference. ClawVisor vaults credentials, enforces task-scoped authorization, logs every API call, and requires human approval for destructive operations. If the user doesn't want ClawVisor, the only safe alternative is offline file exports (Google Takeout, Twitter archive download).
- Each phase is independently valuable — the user can stop after any phase and still
have a useful brain.
- Progress is tracked in
~/.inbrain/cold-start-state.jsonso interrupted sessions
can resume.
- Entity detection and cross-linking run on every import, not as a separate pass.
Prerequisites
- Inbrain installed and initialized (
inbrain doctor --jsonall green) - Brain repo cloned and synced
- Agent has terminal access and can run
inbrainCLI commands
The Priority Stack
Data sources ranked by information density × ease of import:
| Priority | Source | Why | Time | Pages Created | |
|---|---|---|---|---|---|
| 1 | Existing markdown/Obsidian | Highest density — it's already structured | 5 min | 100s-1000s | |
| 2 | Google Contacts | Seeds the people/ directory — names, emails, companies | 10 min | 50-500 | |
| 3 | Google Calendar (90 days) | Meeting history with attendee context | 15 min | 30-90 | |
| 4 | Gmail (recent threads) | Relationship context, active threads, org chart signals | 20 min | 50-200 | |
| 5 | Conversations (ChatGPT/Claude exports) | Your thinking, questions, mental models | 15 min | 10-100 | |
| 6 | X/Twitter archive | Your public positions, takes, engagement patterns | 20 min | 30-365 | |
| 7 | File archives (Dropbox/Drive/local) | Historical documents, old writing, photos | 30+ min | varies | |
| 8 | Meeting transcripts (Circleback/etc.) | Deep relationship context from recorded calls | 20 min | 10-50 |
Phase 0: ClawVisor Setup (Required for API Access)
Safety boundary: An AI agent with raw OAuth tokens to your Gmail, Calendar,and Contacts is an uncontrolled attack surface. One prompt injection, onemalicious tool call, and your entire Google account is exposed. ClawVisoreliminates this risk class entirely.
ClawVisor is a credential gateway that sits between the agent and your APIs. The agent never sees your credentials — ClawVisor injects them at request time, enforces policies, and logs everything.
What ClawVisor gives you:
- Credential vaulting — agent sees shadow tokens, never real secrets
- Task-scoped authorization — each workflow declares exactly what it needs
- Audit trail — every API call logged with metadata (who, what, when)
- Human approval gates — destructive operations (send email, modify calendar)
require your explicit approval
- Multi-service — Gmail, Calendar, Contacts, Drive, GitHub, iMessage from one gateway
- Revocation — disable the agent's access in one click, no token rotation needed
Setup (15 min):
- Sign up at app.clawvisor.com
- Create an agent in the dashboard, copy the agent token
- Set environment variables:
``bash inbrain config set clawvisor_url "https://app.clawvisor.com" inbrain config set clawvisor_agent_token "<token>" ``
- Activate Google services (Gmail, Calendar, Contacts) in the dashboard
- Create a standing task with expansive scope:
> "Full brain bootstrapping: read emails, calendar events, and contacts to > populate knowledge base. List, read, and search across all connected accounts."
- Save the standing task ID:
``bash inbrain config set clawvisor_task_id "<task_id>" ``
Critical scoping rule: Be expansive in task purposes. "Email triage" gets rejected by intent verification. "Full executive assistant email management including inbox triage, searching by any criteria, reading emails, tracking threads" works. The intent model uses the purpose to judge each request.
If the user declines ClawVisor
Do NOT fall back to direct OAuth. Instead, skip Phases 2-4 (Contacts, Calendar, Gmail) and proceed with offline-only imports:
- Phase 1 (markdown/Obsidian) — works without any API access
- Phase 5 (conversation exports) — works from downloaded JSON files
- Phase 6 (X/Twitter) — works from downloaded archive
- Phase 7 (file archives) — works from local files
- Phase 8 (meeting transcripts) — works from exported transcripts
Tell the user:
"No problem. We'll skip the Google imports for now and work with file-basedsources. You can set up ClawVisor anytime to unlock Contacts, Calendar, andGmail imports safely."
Do NOT offer direct OAuth as an alternative. An agent holding raw Google tokens is a security liability. The skill should not teach agents to store credentials they shouldn't have.
Phase 1: Existing Markdown / Obsidian Import
The highest-leverage first import. If the user already has a notes system, this is hundreds or thousands of structured pages ready to go.
Discovery
Import
Post-import
- Run link extraction:
inbrain extract links --source db - Run timeline extraction:
inbrain extract timeline --source db - Start embeddings:
inbrain embed --stale(runs in background)
Track progress:```bashecho '{"phase_1_complete": true, "pages_imported": N}' > ~/.inbrain/cold-start-state.json```
Phase 2: Google Contacts → People Pages
Seeds the people/ directory. Every person in your contacts becomes a brain page with name, email, phone, company, and notes. This is the foundation that all other imports build on — when Gmail references "john@acme.com", the brain already knows who John is.
Via ClawVisor
Via direct Google People API
Processing rules
For each contact:
- Filter out noise — skip contacts with no name, no email, or that are clearly
automated (noreply@, no-reply@, support@, notifications@)
- Check brain first —
inbrain search "name"to avoid duplicates - Create people/ page with:
- Name, email(s), phone(s), company, title
- Source attribution:
[Source: Google Contacts, YYYY-MM-DD] - Any notes from the contact as initial context
- Link to company — if the contact has an organization, create/update the
company page and link the person to it
Quality gate
After importing 5 contacts, pause and show the user a sample page. Ask:
"Here's what a contact page looks like. Want me to continue with the rest, oradjust the format first?"
Phase 3: Google Calendar (Last 90 Days)
Meeting history with attendee context. Calendar events reveal who the user meets with, how often, and in what context. Combined with contacts, this builds a rich relationship map.
Fetch events
Brain structure
Follow the three-tier calendar architecture:
Entity enrichment
For each event with attendees:
- Look up each attendee in the brain (they should exist from Phase 2)
- Add a timeline entry to their page: met at [event title] on [date]
- If an attendee has no brain page and appears in 3+ events, create one
- Link attendees who appear in the same meeting
Phase 4: Gmail (Recent Threads)
Relationship context and active threads. Email reveals organizational relationships, ongoing conversations, and communication patterns.
Strategy: Smart sampling, not bulk import
Don't import every email. Import the signal:
- Sent mail (last 30 days) — who the user actively communicates with
- Starred/important emails — user-curated signal
- Threads with 3+ replies — active conversations worth tracking
- Emails from people already in the brain — enrichment, not cold import
Processing
For each email thread:
- Entity detection — extract people, companies mentioned
- Update people pages — add communication context to timeline
- Create meeting pages — if the email is a meeting summary or follow-up
- Skip noise — newsletters, automated notifications, marketing
Filtering rules
Auto-skip (never import):
- noreply@, no-reply@, notifications@, support@, mailer-daemon@
- Unsubscribe-heavy senders (marketing)
- GitHub/Jira/Linear notification emails
- Calendar invites (already captured in Phase 3)
Always import:
- Direct emails from people in the brain
- Starred/flagged emails
- Emails the user sent (their words are highest-value signal)
Phase 5: Conversation Exports (ChatGPT / Claude / Perplexity)
Your thinking, captured. AI conversation exports reveal what the user was researching, building, and thinking about. This is original thinking preserved in dialog form.
Supported formats
- ChatGPT: Settings → Data Controls → Export →
conversations.json - Claude: Download from claude.ai conversation history
- Perplexity: Export from settings
Processing
For each conversation:
- Assess significance (1-5 scale):
- 1 = Pure utility (how-tos, quick lookups) → skip or minimal page
- 2 = Minor context → 1-paragraph note
- 3 = Notable (reveals interests, building something) → full page
- 4 = Important (deep personal processing, strategic thinking) → rich page
- 5 = Defining (identity work, breakthrough insights) → full treatment
- Extract entities — people, companies, concepts discussed
- Capture original thinking — the user's exact phrasing is the signal.
Never paraphrase.
- File by primary subject — not in a "conversations/" dump. A conversation
about a person goes to people/, about a concept goes to concepts/, etc.
Quality rule
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 96 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/cold-start/SKILL.md
Popularity
- Repository stars
- 143
- Repository forks
- 126
- 7-day trend score
- 25
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/inbrainfun/inbrain/cold-start)