--- name: guava-stack description: Makes Notion the owner's shared memory and workspace in Claude and ChatGPT, in their desktop apps and in Claude Code and Codex, by running Notion's official setup guide for agents, adding the steps it leaves to each app, then Guava's parts (a guava-hub with the owner's context and rules, a map of where their work lives, in Notion or the apps they already use, their scheduled routines recorded in Notion's Skills library, founder-mode, and seven starter skills, the head-chef and line-cook router among them). Use when the owner says "set me up", "set this up https://workwithguava.com/guava-stack", "Follow the Start here steps in github.com/romeodiaz/guava-stack", "check my routines", "update guava-stack" or "uninstall guava-stack". --- # guava-stack v0.2.3 guava-stack is a small add-on to Notion's official setup guide for agents, [Set up Notion for your agent](https://developers.notion.com/prompts/setup.md). Notion's guide does the setup. This skill adds what the guide leaves to each app (how Claude Code and Codex connect to Notion, where they keep the custom instructions, and how the owner's other apps join), then Guava's parts on top. It supports four apps on two plans: the Claude desktop app and Claude Code on a Claude plan, and the ChatGPT desktop app and Codex on a ChatGPT plan. The desktop app's **Code** tab (Claude) or **Codex** tab (ChatGPT), set to **Local**, is Claude Code or Codex running on the owner's computer. For anything else, say it isn't supported yet. Read Notion databases with `notion-fetch` or through a saved view (`notion-query-data-sources` in view mode), not SQL: on Free and Plus plans Notion meters SQL per workspace, and views have no limit. Use SQL only when no view can answer. ## Set up 1. **Run Notion's guide.** Read it in full, then run its steps in order, following its rules for talking with the user, and use steps 2 and 3 below where it leaves the details to your app. Where these steps and Notion's guide cover the same thing, follow Notion's guide. This guava-stack is tested with Notion's version 0.0.6: if the guide shows a newer version, run 0.0.6 from https://developers.notion.com/prompts/setup/versions/0.0.6.md and tell the owner once that Notion has a newer one. If that link doesn't load, run the newer version and tell the owner guava-stack isn't tested with it yet. The steps below name Notion's steps by their 0.0.6 number and name; if a version numbers them differently, go by the name and what the step does. - **The setup card** (Notion's Choose how much to set up, right after step 1): guava-stack always runs the shared context layer, so don't show the card. Pick **Shared context layer** for the owner and tell them in one line, then do the rest of what Notion's guide says for that choice: save it as the **Notion agent setup choice** memory and treat it as the approval for Notion's private steps. Guava's parts still get their one plan and one yes. 2. **Connect Notion** (Notion's step 1, Set up the Notion MCP), in the app you're running in: - Claude desktop app: "Open https://claude.ai/customize/connectors?q=notion and click **Connect** next to Notion," then start a new chat if Notion's tools don't show up. - ChatGPT desktop app: "Open https://chatgpt.com/plugins?search=notion and click **+** next to Notion," then start a new chat if Notion doesn't show up. - Claude Code: `claude mcp list` shows `claude.ai Notion` when Claude Code is signed in with the same Claude account. Only if it doesn't, run `claude mcp add --transport http --scope user notion https://mcp.notion.com/mcp`. If Notion asks for sign-in, have the owner type `/mcp` and approve Notion's sign-in page. - Codex: only if `codex mcp list` doesn't show Notion, run `codex mcp add notion --url https://mcp.notion.com/mcp`. If Notion asks for sign-in, run `codex mcp login notion`, and the owner approves Notion's sign-in page. - In Claude Code and Codex, a connection added during a session may not reach it: if Notion's tools don't show up, have the owner start a new session and paste the Start here line again. Then finish with Notion's own check: tell the owner their name and workspace. 3. **Save the custom instructions** (Notion's step 2, Create the Agent Operating Guide and update custom instructions). Every app gets the same text, with the link to the owner's Agent Operating Guide: - Claude and ChatGPT desktop apps: the click paths in Notion's guide. - Claude Code: the end of `~/.claude/CLAUDE.md`, the file every Claude Code session loads. - Codex: the end of the global file every Codex session loads, in `~/.codex`, or in `$CODEX_HOME` when it's set: `AGENTS.override.md` if it's there and not empty, otherwise `AGENTS.md`. Guava adds two things at the end of Notion's text, inside the same block, so the owner pastes once. First this line: ``` Also use my guava-hub in Notion, which my Agent Operating Guide links: read its context and rules pages in the same step as the guide, follow the rules page as my working preferences, and in Claude Code or Codex route work with my guava-router Skill. ``` Then founder-mode's rules 1 to 4, the block under **Never bend these** in [founder-mode](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/founder-mode/SKILL.md), word for word. They're safety rules, so they go here, where they hold whatever any page says, even when Notion is down; the rest of founder-mode goes on the rules page. Before the block, tell the owner in one sentence what it does: "This tells your AI to use Notion as its shared memory, read your guava-hub once per session, and always ask before anything it can't undo." Offer the block as something to copy, as Notion's guide says. In Claude Code and Codex, show the owner the exact text and the file, and save it yourself after their yes, as Notion's guide offers. Add to what's there and keep the owner's other lines. Never put it in a project's `CLAUDE.md` or `AGENTS.md`: those live in code repositories, and Notion's guide keeps personal guidance out of them. Keep going in this session. When setup is finished, have the owner start a new session and ask "Where does my Agent Operating Guide live?": it passes if the answer gives the guide's link without searching. 4. **Run Notion's steps 3 to 5** (the daily loop and saving the owner's context), then add **Guava's parts** below, then run Notion's step 6, Complete the Agent Operating Guide, which records them in the guide's destinations. Then add the owner's other apps, and end with Notion's Last step, get the Notion app, since it closes setup. - For the daily check (Notion's step 3, Create a daily loop), the Claude desktop app runs it as a scheduled task and the Codex app as an automation. Both run only while the app is open and the computer is awake. Set it up in each desktop app the owner uses, with that app's own memory as its source. With only Claude Code or the Codex CLI, say the check can't run on its own there and offer the same steps as a daily checklist, as Notion's guide says. - When Notion's step 6 completes the guide, keep it short: every app reads it at the start of each session, a longer always-read page gets followed less closely, and any wrong line reaches every session. Keep each destination and preference to what to do and when. When one needs a procedure, put the steps in a skill and leave a line that says when to use it and names the skill, as the routines line's last sentence does for **Check my routines**. ## Guava's parts Ask once. Show one short plan with a line on what each part does and every database, column and view you'll add, since Notion's guide asks before a new schema, and do it all on one yes. The owner can drop any part by name. If they drop guava-router, take "and in Claude Code or Codex route work with my guava-router Skill" out of Guava's line everywhere step 3 saved it, showing them the change for each desktop app. founder-mode is always on. Only these get their own question: filing guava-hub in a shared teamspace, scheduling anything, third-party skills, whose audit results come first, and oracle-council and oracle-research, which cost money. Save into the owner's private pages by default, as Notion's guide says. - **guava-hub:** a page called guava-hub that holds the two pages below and Notion's Skills library database (move it in, since Notion's step 5, Save the user's existing context, saves skills there; if they don't have one yet, make it there with `notion-create-database` and `database_type` skills), with links to the Agent Operating Guide and Notion Memory at the top. Tasks, projects and other work stay where they live, as **Where your work lives** says. Offer to put it at the top of the owner's teamspace, next to their other databases, so the whole hub shows in the sidebar. Notion's guide asks before filing in a shared space, so that needs a yes; without one, keep it private. The Agent Operating Guide stays private either way, as Notion's guide says. - **From Guava's template:** an owner who'd rather click can duplicate Guava's template first, from https://guava-hub.notion.site/guava-hub-409a1a34268a810c8951f9a75a9e5c8a. Then use its guava-hub instead of making one: replace its "Not set up yet" lines with links to the Agent Operating Guide and Notion Memory, and fill in context and rules. Its rules page already has founder-mode's rules 5 to 16, and its Skills library already has its icon and the Routines columns and view, so Notion's step 5 saves skills there. If the owner already had a Skills library with skills in it, keep theirs, move it in, and offer to delete the template's empty one. A duplicate lands in the owner's private pages, and Notion's tools can't move a page to the top of a teamspace, so if the owner says yes to the teamspace, they drag guava-hub there. - **context:** the owner's work, whether it's a business, a team at a company, a lab or a side project, in short bullets under Work, Who it serves, What you deliver, People, Voice, Tools, Where your time goes and Priorities. Who the owner is stays on Notion Memory's About page, so Work opens with a link to it instead of repeating it. Draft it from their website, LinkedIn and anything they share, ask a few short questions for the rest, and keep the link each fact came from. Leave out what you're unsure of and ask instead. No passwords, keys or other secrets. - **rules:** the owner's working preferences: their own, and the rules skills they turn on, such as founder-mode's rules 5 to 16, each set word for word in its own section, listed at the top of the page. Rules that must always hold go in the custom instructions instead (step 3). - **Icons:** give each page its 8-bit icon from this repo, as an external image icon at `https://raw.githubusercontent.com/romeodiaz/guava-stack/main/assets/`: guava-hub `brain-hub.png`, context `logo.png` and rules `founder-mode.png`. The Agent Operating Guide gets the đŸ§­ emoji as its icon. Each starter skill's page gets its own too (step below): workflow-review `workflow-review.png`, design-cook-off `cook-off.png`, humanizer-writing `humanizer-writing.png`, ponytail-coding `ponytail-coding.png`, oracle-council `oracle-council.png`, guava-router `model-router.png` and oracle-research `oracle-research.png`. The Skills library gets `skills.png` too, but Notion's tools can't set a database's icon, so offer it as one optional click for the owner: the library's icon, then paste the image link. The template's library already has it. - **Where your work lives:** a map of where each kind of work lives, in Notion or another app, so every app files work where the owner already keeps it. Map it; don't move it. 1. Ask where each kind of work lives today: tasks and to-dos, projects, deals and clients, meeting notes, documents and files, plus anything else the context page's Tools section names, such as code or post drafts. Search the Notion workspace for databases that hold any of them, whatever they're called, and note the other apps the owner names, such as Linear, Jira, HubSpot, Google Drive or SharePoint. 2. Leave everything where it is. Never suggest moving work into Notion, and never move, import or delete rows, files, views or relations. 3. When an app the owner names has a connector in this app and it isn't connected yet, offer to connect it; the owner approves the sign-in. 4. Only for a kind of work with no home at all, offer one in Notion: Tasks and Projects as Notion's own tasks and projects databases (`notion-create-database` with `database_type`), related to each other; Meetings with a name, a date and a Project relation, for Notion's AI meeting notes; Docs with a name, a type and a Project relation. 5. When tasks live in Notion, tell the owner that **My Tasks**, on Home in the sidebar, lists the open tasks assigned to them from up to 10 Task databases, without moving any. A tasks database made in step 4 already counts. For any other tasks database, offer Notion's **Turn into Tasks** (the database's settings, then More settings), naming which of Status, Assignee and Due date it would add; it changes the schema and no Notion tool does it, so the owner clicks it. If the tasks still don't show, they add the database under My Tasks, New Task, then Configure. 6. Notion's step 6 records each one in the Agent Operating Guide's destinations, one line each, naming the app when it isn't Notion, such as "Bugs and engineering tasks: Linear, team ENG" or "Client files: Google Drive, Clients folder", so every app finds it there. - **Task log** (offer it once the owner has a home for tasks, in Notion or another app): the assistants log the bigger work the owner would track, so one search finds a job's whole trail. Add this line to the Agent Operating Guide's preferences: ``` Log bigger work I'm involved in and would track (a project, event or feature) as a task where my tasks live, as my Agent Operating Guide's destinations say, when it starts, with its goal and links, and put the task's ID in commits, PRs, hand-offs and memories. Skip questions, quick lookups and small changes I only approve, such as wording fixes or a renamed skill: their commit or PR is the record. ``` When their tasks live in Notion and the database has no ID column yet, offer to add one: a unique ID with a prefix the owner picks, such as `TASK`. Apps like Linear and Jira already give each task an ID. - **Routines:** the scheduled tasks in the owner's apps, recorded in the Skills library next to the skill each one runs, so every app sees what runs where and nothing runs twice. Each app's own scheduler keeps running them. 1. Add these columns to the Skills library, keeping any it already has: **Schedule** (text, such as "Fridays 9 AM PT"), **Runs on** (a select of Claude, ChatGPT, Claude Code and Codex, plus any other app the owner schedules in), **Scheduler ID** (text: the job's ID and where it lives), **Pre-approved** (text: what the owner said yes to in advance for it, in their words) and **Last run** (a date). Add a **Routines** view that shows only rows with a Schedule, with those columns. 2. Bring in the scheduled tasks this app already has, as **Check my routines** below says, including Notion's daily check from step 3. When a job's prompt isn't a skill yet, offer to save it as a Notion Skill, the way Notion's step 5 saves skills, so it has a row. 3. Add this line to the Agent Operating Guide's preferences: ``` When you set up, change or stop a scheduled task, update its skill's Schedule, Runs on, Scheduler ID and Pre-approved in my Skills library in the same step, and write into its prompt that each run sets Last run when it finishes. When I say "check my routines", follow Check my routines in the guava-stack skill from github.com/romeodiaz/guava-stack. ``` - **founder-mode:** always on, without asking: 16 working rules, so the assistants handle safe work on their own, check the real result and ask before anything costly or permanent. Rules 1 to 4 are already in the custom instructions from step 3. Add rules 5 to 16, on how to work, report and improve, to the rules page as founder-mode's **Turn on** says, then tell the owner in one line that they can change any rule there, or say "uninstall founder-mode". Follow [founder-mode](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/founder-mode/SKILL.md). - **Starter skills:** the plan includes workflow-review, design-cook-off and guava-router; humanizer-writing, ponytail-coding, oracle-council and oracle-research are offered as the questions above say. Save the ones the owner keeps as real Notion Skills in the Skills library, with every file they need, as Notion's step 5 (Save Skills) says: 1. [workflow-review](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/workflow-review/SKILL.md): "Say 'review my workflows'. I'll rank which of your workflows are worth automating, as a report that stays on your computer." 2. [design-cook-off](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/design-cook-off/SKILL.md): "Say 'cook-off' for a page people judge by its look. I'll build it twice with two design skills, and you pick one." It runs in Claude Code or Codex. 3. humanizer-writing, blader's [humanizer](https://github.com/blader/humanizer): "So anything I write for you doesn't sound like AI." 4. ponytail-coding, the `skills/ponytail` skill from Dietrich Gebert's [ponytail](https://github.com/DietrichGebert/ponytail): "When I write code for you, I write the least code that does the whole job." 5. [oracle-council](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/oracle-council/SKILL.md): "Say 'ask the council' on a hard call. Three top AIs from three companies answer it at once, and I merge their answers into one verdict." It runs in Claude Code or Codex, with its Gemini 4 Argon seat on OpenRouter, billed per use, or by hand in a chat app with no terminal. Follow its **Set up** once it's saved. 6. [guava-router](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/guava-router/SKILL.md): "In Claude Code or Codex, I hand thinking work to your head-chef and doing work to your line-cook." With Claude Code or Codex on the owner's computer, follow its **Set it up**. Save it as a Skill even though the guide holds the model lines: the lines name the two slots, and the skill is what tells each app when and how to hand work off. 7. [oracle-research](https://raw.githubusercontent.com/romeodiaz/guava-stack/main/skills/oracle-research/SKILL.md): "Say 'research this' or 'what are people saying about…'. I'll sweep the last 30 days on Reddit, Hacker News, YouTube and the web, and answer here with links." It runs in Claude Code or Codex on the same OpenRouter key as oracle-council, about $0.30 a run. Take third-party skills straight from their GitHub repos, as **Third-party skills** below says. Before the yes, say in plain words what their [skills.sh](https://skills.sh) audits found, failed and warning checks included (`https://skills.sh/blader/humanizer`, `https://skills.sh/dietrichgebert/ponytail/ponytail`). ## Third-party skills Install a third-party skill from its GitHub repo at the newest commit, then keep the owner on that commit until they say yes to a newer one. An update is new instructions the assistants will follow, so it gets the same audit and yes as the install instead of arriving on its own. - **Audits:** before each yes, read the skill's skills.sh page and say what it found, failed and warning checks included. When a failed check names specific entries, such as sites listed in taste-skill's `library/sites.json` that are on threat blocklists, offer to install with those entries taken out. - **Skills that are only instructions** (humanizer-writing, ponytail-coding) are saved as full Notion Skills, as **Starter skills** says. End each with one line naming its repo, the commit and the audit date. - **Skills that run programs** (impeccable and taste-skill, for design-cook-off) are installed on the computer for each tool, since a Notion copy can't run them and impeccable ships separate builds for Claude Code and Codex. Give each a pointer row in the Skills library: a Skill page named after the skill, without its files, recording the repo, the commit installed and any change made to it, the audit results and their date, and where each tool keeps it. Its steps tell the assistant to use the installed copy; where it's missing, to install the recorded commit after the audits and a yes; and before each use, to compare the repo's newest commit (`git ls-remote HEAD`) with the recorded one and, if they differ, say so in one line and keep using the installed copy. - **Updates** happen only on a yes, through **Update** below: show what changed since the recorded commit and the current audits, install, reapply any change the owner chose, and update the record. ## Check my routines Use this when the owner says **"check my routines"**, when an app joins, and as part of "update guava-stack". Each app runs its own scheduled tasks and the Skills library only records them, so the check runs in each app. Read the Routines view first. 1. **List this app's scheduled tasks:** the Claude desktop app's scheduled tasks, Claude Code's routines (`/schedule`, or RemoteTrigger's list), ChatGPT's scheduled tasks or the Codex app's automations, whichever you run in. If you can't list them, say so and ask the owner to read them off, naming where to look. 2. **Compare** each job with the rows whose Runs on is this app: a job with no row, a row with no job, a different time, a Scheduler ID that doesn't match, or a Last run older than the schedule allows (a weekly routine with no run in 8 days). One-time reminders that already ran aren't routines; leave them out. 3. **Show what differs** as a short list, most urgent first, and fix the rows on the owner's yes. Fill Pre-approved only from what the owner approved, such as the job's own prompt or their answer, never by guessing. Changing, stopping or starting a job itself needs its own yes, and so does adding the Last run line to a job's prompt: show the exact line first. ## Add the owner's other apps Each desktop app pairs with the tool on the same computer: Claude with Claude Code, ChatGPT with Codex. After setup in one, offer the other, and the owner pastes the same Start here line there. An owner with both plans does the same in the other plan's apps. A joining app doesn't show Notion's setup card either. When the owner has an Agent Operating Guide but no guava-hub yet, setup stopped partway: pick up at step 4. When they have both, joining is short: connect Notion (step 2), check it's the same workspace and guide, save the same custom instructions (step 3), check a new session, run **Check my routines** if the Skills library has the Routines columns, then stop. Offer Notion's other steps, such as the daily check or bringing in memories, only if the owner asks, so nothing runs twice. To reach Claude Code or Codex from the desktop app, the owner opens its **Code** or **Codex** tab, sets it to **Local**, picks their home folder and pastes the Start here line there. If the `claude` or `codex` command is missing on the computer, say so and point to the install steps at https://code.claude.com/docs or https://developers.openai.com/codex, rather than guessing. ## Update When the owner says "update guava-stack": read this skill again, run the version check from Notion's daily check now, and show any change to the custom instructions, old and then new. Then compare founder-mode's version on the rules page and each Guava skill in the Skills library with this repo's copy, and each third-party skill's recorded commit with its GitHub repo's newest commit and current audits, as **Third-party skills** says. Then read the Agent Operating Guide's preferences. For any of the owner's own lines that hold a procedure, offer to move the steps into a skill, showing the new skill and the line that replaces them, which says when to use it, as setup step 4 says. Leave Notion's own lines and Guava's task log and routines lines as they are. Then run **Check my routines**. Change nothing without a yes. ## Uninstall When the owner says "uninstall guava-stack": show the exact text to remove, then, on a yes, take the custom instructions out of `~/.claude/CLAUDE.md` and Codex's global file from step 3, leaving the owner's other lines, and Guava's lines from the desktop apps' custom instructions. Offer to remove the Notion connections steps 2 added to Claude Code and Codex, as their own items, since other work may use them, and the OpenRouter key oracle-council or oracle-research saved in `~/.config/guava-stack/openrouter-key`, if there is one (the key itself stays in the owner's OpenRouter account until they delete it at https://openrouter.ai/settings/keys). Everything in Notion stays, since it's the owner's: the Agent Operating Guide, the guava-hub, memories, skills, documents and the databases and columns setup added. Offer to take Guava's task log and routines lines out of the guide's preferences, as their own item, since they point to this repo. Notion's own text stays in the desktop apps' custom instructions, since it's Notion's setup; tell the owner where it is in case they want it gone too.