The argument in one line.
Generic AI gives generic advice, but an agent built on a curated knowledge base — one book, one framework, one trusted expert — gives grounded specialist counsel that improves every time you feed it more.
Read if. Skip if.
- A solo founder or small team leader who wants AI that actually understands your chosen frameworks, not just the average of the internet.
- Anyone who has tried using ChatGPT or Claude for strategic advice and found it too hedged, too broad, or missing the specific mental models you trust.
- A Notion user already on a business plan who wants to turn their reading and research into a reusable AI collaborator.
- Someone building or refining an AI agent system who wants a clear three-layer architecture: instructions, skills, knowledge base.
- You want a fully automated no-input system — this requires manual curation and iterative ingestion.
- You are not a Notion user and have no interest in becoming one; the workflow is tightly coupled to Notion AI.
The full version, fast.
The reason AI advice feels generic is that it draws from everything, not from sources you trust. The fix is a three-layer agent architecture: instructions that define role and boundaries, skills that define reusable processes, and a knowledge base that holds the curated frameworks you actually want the agent to reason from. The video builds this live in Notion using Claude Opus, sourcing a marketing specialist from Seth Godin's This Is Marketing, and demonstrates that the agent correctly refuses to answer when the knowledge base is empty and gives grounded, source-cited advice once it is seeded.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Hook + premise
What if you could clone any expert into an AI adviser? Opening promise and channel context.

02 · The three-layer architecture
AgentOS hub tour: global instructions dispatch to specialists made of agent instructions, skills, and a knowledge base. The knowledge base is the heart.

03 · AgentOS overview + download
Demo of the full AgentOS hub, distinction between personal agent (consultancy) and custom agents (automation + credits). Download link pitched.

04 · Build start: Meta Agent plans the specialist
Using the Meta Agent on Claude Opus 4.7 to plan the marketing strategy specialist. The agent reads its own KB before answering. Four clarifying questions answered.

05 · Knowledge base schema + button automation
Defining the KB schema live. Notion button automation creates a pre-structured KB page in one click.

06 · Writing agent instructions + token efficiency review
Meta Agent writes the marketing specialist instructions including knowledge base entry gate. Instructions reviewed and slimmed 55% for token efficiency.

07 · Skills: Book Ingestion Helper + Positioning Audit
Two specialist skills built and reviewed. Book Ingestion Helper generalised to work across any knowledge base. Instructions linked into global routing.

08 · Live test on empty knowledge base
First live test proves the system: agent correctly flags low confidence and no KB entries, refuses to answer without grounding, recommends ingestion.

09 · Book ingestion demo (This Is Marketing)
Seth Godin PDF pasted chapter by chapter. Agent extracts, atomizes, and normalizes into structured KB entries. Chapter list used as ingestion guide first.

10 · Live test with seeded knowledge base
Positioning question for AgentOS answered by the now-seeded marketing specialist using Godin frameworks. Result read aloud with Speechify. Result deemed genuine and specific.

11 · Compounding loop: self-improving KB agent
Harmonious Seeker custom agent configured to run weekly, review KB for gaps, suggest new entries from reputable sources. Credit cost acknowledged; personal-agent skill alternative recommended.

12 · Showcase + CTA
Existing YouTube content strategist agent shown as proof of long-term value. AgentOS download CTA. Channel milestone: 20k subscribers.
Lines worth screenshotting.
- An AI agent without a knowledge base is still just an AI — the knowledge base is what makes it a specialist.
- Skills define what the agent does step by step; the knowledge base defines what it knows. Confusing them produces mediocre agents.
- Agent instructions should be reviewed for token efficiency after every major build — a 55% reduction is not unusual and always improves reliability.
- An empty knowledge base that correctly returns low confidence and recommends ingestion is a success, not a failure.
- Pasting book content chapter by chapter into a chat window outperforms uploading a PDF for any document over 15 pages.
- Notion's personal agent is credit-light and suited for consultancy-style collaboration; custom agents are for scheduled automation but cost credits.
- A compounding knowledge loop — weekly audit, gap detection, new entries from reputable sources — is the upgrade path from a static agent to a self-improving one.
- The knowledge base is LLM-agnostic: the same Notion KB works across Claude, Gemini, and DeepSeek depending on which model you select.
- Writing the job description for an AI specialist is the same cognitive task as writing a job description for a human hire — role, mission, boundaries, handoff rules.
- Curating sources is the work that makes the agent valuable; the AI does the atomizing and normalizing, not the selection.
- An anti-drift protocol in agent instructions — explicit rules about when NOT to answer — is as important as what the agent is told to do.
- Asking the agent to review its own instructions for token efficiency is itself a reusable skill worth adding to the system.
What makes an AI agent actually useful
The gap between generic AI and genuinely useful AI is not model quality — it is whether the agent is anchored to a curated body of knowledge that was chosen deliberately.
- Generic AI draws on everything it was trained on; a knowledge-grounded agent draws only on sources you have curated and trust, which is why its answers feel different.
- The three layers of a working specialist agent are instructions (who it is and what it will not do), skills (reusable step-by-step processes), and a knowledge base (the principles it reasons from) — conflating any two of these produces a weaker system.
- Atomizing a source means one concept per entry with explicit fields for when to apply it and how confident you are — the structure is what makes it retrievable, not the volume of content.
- An agent that correctly refuses to answer when its knowledge base is empty is behaving as designed; low-confidence responses that recommend ingestion are a feature, not a failure.
- Token efficiency in agent instructions matters more than thoroughness — a 55% reduction in instruction length with no loss of quality is achievable through a single review pass, and shorter instructions produce more reliable behavior.
- A weekly automated audit that scans a knowledge base for gaps and proposes new entries from reputable sources turns a static reference into a compounding asset that grows without requiring manual research every cycle.
- Pasting source text chapter by chapter into a chat window is more reliable than uploading a PDF for any document over 15 pages, because models process pasted text with higher fidelity than extracted PDF content.
Terms worth knowing.
- AgentOS
- A multi-modal personal agent instruction system for Notion that uses global instructions to dispatch to specialist sub-agents; built by the creator and available at bettercreating.com/agentos.
- Knowledge base (agent context)
- A structured database of curated frameworks, principles, and case studies that an AI agent searches before answering, grounding its responses in chosen sources rather than general training data.
- Skill (agent context)
- A reusable, step-by-step process an agent can invoke for a specific task, such as ingesting a book chapter or running a positioning audit.
- Meta Agent
- A prompt engineering specialist sub-agent that the creator uses to help build and refine other agents; it consults its own knowledge base of agentic design patterns while doing so.
- Atomize
- The process of breaking a source text into discrete, single-concept knowledge base entries — one insight per entry — so the agent can retrieve and apply each individually.
- Anti-drift protocol
- Rules written into agent instructions that explicitly limit scope and prevent the agent from drifting into adjacent tasks or giving ungrounded answers.
- Confidence level
- A property on each knowledge base entry (High / Medium / Low) the agent uses to prioritize proven, validated ideas over untested ones when formulating advice.
- Compounding knowledge loop
- An automated cycle where an agent periodically reviews its own knowledge base for gaps and suggests new entries from reputable sources, causing the knowledge base to improve without manual effort each cycle.
Things they pointed at.
Lines you could clip.
“Without the knowledge base, I found that the end AI tends to just be still a bit generic, but with — like, a very clear process that it's following.”
“This is a specialist, not a chatbot giving you the same generic advice it gives everyone else.”
“Make it, trigger it once a month. Review the knowledge base, flag anything outdated, suggest three new entries based on the gaps — and it will get sharper every cycle.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
What if the AI adviser you have been missing was already sitting on your bookshelf? The creator opens with a stack of business books and a single question: can you take any expert's entire framework and clone it into an on-demand specialist — one that reasons only from sources you trust, not from the average of the internet?
Named ideas worth stealing.
Three-Layer Agent Architecture
- Agent Instructions
- Skills
- Knowledge Base
Every specialist agent needs: instructions defining role/boundaries, skills as reusable SOPs, and a knowledge base of curated principles the agent searches before answering.
Knowledge Base Schema
- Topic
- Category
- Key Insight
- When to Apply
- Confidence (High/Medium/Low)
- Source (Book + Chapter/Page)
- Related Entries
The structured fields that make a knowledge base searchable and useful to an agent — not a document dump but a normalized database of atomized insights.
Extract - Atomize - Normalize
- Extract: pull every distinct concept per chapter
- Atomize: one concept per KB entry; split if multiple triggers
- Normalize: fill all schema fields; quality gate before saving
The three-step book ingestion process that turns raw chapter text into structured, agent-ready knowledge base entries.
Compounding Knowledge Loop
- Ingest source material
- Agent uses KB to answer questions
- Weekly audit: scan for gaps and redundancy
- Research and propose new entries from reputable sources
- Review and add approved entries
- KB grows each cycle
A scheduled self-improvement cycle where the agent audits its own knowledge base and suggests additions, turning a static library into one that compounds over time.
How they asked for the click.
“Go and check out AgentOS, newly updated as of this week with these new database systems. Link in the description.”
Soft, conversational pitch after the demo value has been fully delivered. Also plugs a business OS template coming soon via email list.
- notion.com ↗
- WATCH NEXT: Create self-improving knowledge bases in Claude here ↗
- youtu.be ↗
- Get my FREE guide “Your First Steps to Building an Agentic Business” 👉 ↗
- + CoWork OS for Claude: Get your system setup better & faster ↗
- + All my Notion templates & agentic business resources ↗
- + WisprFlow ↗
- + Get Notion For Free ↗
- + Speechify ↗
- + Claude ↗
- 📸 Instagram ↗
- 🐦 Twitter ↗
- 🎵 TikTok ↗
- 📨 🌍 Get Resources & Sign Up to my newsletter here ↗
- ☑️ Get my iOS, iPad & Notion Icon Packs ↗
- Stop Adding AI Tools. Build an Agentic Business ↗




































































