Loading video...

Video Failed to Load

Go Home

GPT-6 Astra inside Obsidian was used to build a knowledge base inspired by Karpathy's LLM Wiki that stores winning ad structures, sales spines, character sheets and timed video sequences for a reusable long-form ad agent.

48,718 views • 10 days ago •via X (Twitter)

17 Comments

WalletX.gg - Profitable Wallets Scraper's profile picture
WalletX.gg - Profitable Wallets Scraper10 days ago

karpathy drops a wiki mario builds an ad agency in obsidian by dinner

Wizard of Alt's profile picture
Wizard of Alt10 days ago

that's a lot of nodes for what's ultimately a copywriting cheat sheet with a nicer interface

Align's profile picture
Align10 days ago

Pretty graph aside, the useful part is turning one-off ad prompts into a library you can actually pull from next week instead of starting from zero again.

Macro Bombastic's profile picture
Macro Bombastic10 days ago

honestly feels like overkill for ad copy, but i get the appeal

AI Mastery Guide's profile picture
AI Mastery Guide10 days ago

that graph view looks so satisfying

TheDeFiMentor's profile picture
TheDeFiMentor10 days ago

That’s insane

Vipul Kumar Kewat's profile picture
Vipul Kumar Kewat10 days ago

This is how you build actual moats with AI, moving past ephemeral prompt sessions to persistent, interconnected knowledge graphs turns ad generation into a deterministic assembly line.

Brainrot Labs's profile picture
Brainrot Labs10 days ago

Now that’s next-level productivity!

hops's profile picture
hops10 days ago

Reusable agent memory changes the workload from one-off prompting to continuous retrieval and execution. That is where @fluence_project fits: a verifiable backend for running agent tasks without anchoring the stack to one cloud

Johnny Yukari's profile picture
Johnny Yukari10 days ago

Every winning spine stops converting eventually and the agent will keep citing stale notes like gospel. I'd want a kill switch for old structures. How does it flag a note that went cold?

Audiee.AI's profile picture
Audiee.AI10 days ago

The interesting leap is turning context into a reusable production asset—not just a one-off generation. Versioning those structures and measuring which sequences actually work feels like the hard, valuable layer.

_alphashark_'s profile picture
_alphashark_10 days ago

worth checking whether Astra's outputs stay retrievable as separate notes or just live in chat history. if the wiki isn't backed by actual linked files in the vault, your sales spines won't survive an Obsidian reindex or plugin update.

Daily AI Digest's profile picture
Daily AI Digest10 days ago

the agent can reuse proven structures while preserving timing, characters, and sales logic, turning ad creation into a repeatable system rather than one-off prompting.

Adel Bucetta's profile picture
Adel Bucetta10 days ago

that's the real unlock: collapsing the time between idea and shipped product isn't just about ai or copying ui, it's about collapsing the knowledge gap between disciplines.

YonLe's profile picture
YonLe10 days ago

External structure beats baking it into weights when the offer or tone shifts mid-campaign.

Mr.SahaRok's profile picture
Mr.SahaRok10 days ago

This is where AI gets really interesting. The real advantage isn’t the model — it’s the knowledge base you build around it. Once your best ideas, structures and workflows become reusable context, every new project starts with your previous wins. That compounds fast. 🧠🤖 Follow for more practical AI systems.

Ryan White's profile picture
Ryan White10 days ago

I’m more interested in whether the agent queries the notes directly. If the winning ad spines only show up as pretty graphs, we’re just decorating the workflow.

Related Videos

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 views • 3 months ago