--- name: rim-build-second-brain description: > Build an OKF Second Brain for a local business: a structured, AI-ready memory of the business in the user's own folders, built by the user's own agent from the user's own knowledge. Use when the user says "build my second brain", "create my business memory", "set up OKF", "make my business AI-ready", or connects the Rank-in-Maps MCP and asks what to do. metadata: version: "0.2.0" --- # Build a Second Brain (OKF) You are helping a business owner create a **Second Brain**: a folder of structured markdown files that captures their business facts, evidence, insights, actions, and notes. Once built, any AI they use can load this folder and instantly understand their business. ## Principles 1. **Their folders, their data.** Build in the user's own filesystem or Drive (via your own connectors). Never require them to grant new permissions to Rank-in-Maps. 2. **Extract before you ask.** The user already has the information — in their files, website, email, prior conversations. Mine what you can access first; interview only for gaps. Never invent facts. 3. **Structured over prose.** Facts go in fields, not paragraphs. The test: could a different AI parse this file cold? 4. **Read-only toward the world.** This skill never edits Google Business Profile, posts content, or contacts anyone. It writes local files only. 5. **Twenty minutes to wow.** A useful brain today beats a complete brain next week. Mark gaps `TODO` and move on. ## If the Rank-in-Maps MCP is connected Use `rim_search_docs` / `rim_read_doc_page` to pull the OKF methodology and the latest templates before building. If it is not connected, this skill is self-sufficient — use the templates below. Tool visibility does not prove account entitlement. A client may list paid tools for every account even when running them would return an upgrade or authorization response. Never infer the user's plan from the tool list and never test entitlement by running a paid or write tool. If the user explicitly wants the hosted workspace path, call `rim_get_connected_business` and follow the response. When the account is eligible, hosted setup can continue through `rim_search_business_listings` → `rim_connect_business` → the discovery interview. Read `second-brain/hosted-tools.md` via `rim_read_doc_page` before that workflow. The local folder this skill builds remains the user's portable copy. ## Step sequence ### 1. Locate or create the root folder Ask where the brain should live (a folder you can write to). Create: ```text [Business Name] OKF/ 00_Profile/ README.md business_overview.md entities.md services.md 01_Evidence/ reviews/ 02_Insights/ audit_history.md competitor_analysis.md 03_Actions/ recommended_actions.md completed_actions.md 04_Notes/ manual-notes.md ``` If a `[Business Name] OKF/` folder already exists (e.g. created by Rank-in-Maps sync), extend it — do not create a parallel tree, and do not overwrite files bannered "Generated by Rank in Maps". ### 2. Gather the facts In order of preference: 1. Files/folders the user points you at (brochures, old audits, price lists, website exports). 2. Their website, if you have browsing/fetch capability. 3. A short interview — batch questions, don't drip-feed. Minimum viable facts: business name, address (or service area), phone, website, category/type, opening hours, top 3–5 services with rough pricing. ### 3. Write 00_Profile Use the templates in `templates/` (or below). Every file you create gets this header line: > Maintained by [agent name] for [owner]. Structured for AI reuse. > Last updated: YYYY-MM-DD. - `business_overview.md` — identity, positioning, story, who the ideal customer is. Short prose is allowed here, and only here. - `entities.md` — pure structured facts: NAP, categories, hours, attributes, links, social profiles. Use the frontmatter schema below. - `services.md` — one section per service: name, description (2 lines max), price/pricing model, keywords a customer would use. - `README.md` — one paragraph telling any future AI what this folder is and to read `entities.md` first. ### 4. Seed the other folders - `01_Evidence/reviews/reviews_YYYY_MM.md` — if the user can paste or export recent reviews, log them (date, author, rating, text, replied?). Otherwise create the current month's file with the column headers and a note on how to add entries. - `02_Insights/` — if any past audit or competitor knowledge surfaced in step 2, record it; otherwise leave headed placeholder files. - `03_Actions/recommended_actions.md` — from what you learned, write the 3–5 most obvious actions (e.g. "hours missing on website", "no reply to the 2★ March review"), each with a priority and a why. - `04_Notes/manual-notes.md` — create it, tell the user it's their free-writing space. ### 5. Verify and hand over 1. Re-read `entities.md` back to the user for confirmation — facts must be theirs, not yours. 2. Demonstrate the payoff: answer one question about their business using only the folder. 3. Teach the habit: whenever something changes (new service, price change, notable review), tell your agent to update the brain. Suggest a recurring weekly task: "update my Second Brain from this week's work." ## entities.md frontmatter schema ```yaml --- okf: entities schema_version: 1 business_name: business_type: # storefront | service_area primary_category: secondary_categories: [] address: # omit or mark "service area" for SABs service_area: # list of towns/postcodes if SAB phone: website: email: hours: # per day: open/close or closed mon: "" tue: "" wed: "" thu: "" fri: "" sat: "" sun: "" attributes: [] # e.g. wheelchair accessible, free parking profiles: # GBP, Facebook, Instagram, etc. — URLs only opening_date: updated: YYYY-MM-DD --- ``` Unknown values: leave the key present with `TODO` — never guess. ## What this skill never does - Edit or draft changes to Google Business Profile. - Run paid audits or call paid APIs. - Send the user's data anywhere without being asked. - Ask the user for tokens, API keys, or other credentials.