grok bot + obsidian is basically superhuman mode... my... agent team now has a second brain... a karpathy-style llm wiki for every bot, every decision, and every piece of research. p.s. this video was made and edited by grok bot in cap (here’s how i set it up in roughly 5 minutes) 1/ create one obsidian vault on the chief of staff’s computer. make Home.md the door. 2/ create Hunt folders for twitter, github, hacker-news, reddit, product-hunt, and inbox. 3/ create Ship folders for drafts, digests, angles, and builds. 4/ create the CoS wiki: Index, How-it-works, Today, and Decisions. 5/ create Maps for Jarvis, Hooks, and TELOS. 6/ use graph colors: gold for wiki, teal for maps, blue for twitter, green for github. 7/ file first. every note gets a date and a folder. 8/ scouts write into Hunt and never ping you. chat only receives a short digest. 9/ nothing in the vault posts, pays, or sends. the final yes stays human. 10/ run the daily loop: 08:00 IST for the Daily note, then agency reports at 08:14, 14:14, and 20:14. 11/ performance writes to twitter/live-score. staff engineer writes to builds/. 12/ lock decisions in Wiki/Decisions so dead posts don’t get remade. 13/ earn hooks in Maps/Hooks: trend -> foil -> hook family -> artifact -> lock. don't waste time reading this. give it to your agentshow more

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES.... AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇show more

this should be illegal.. i connected 6 ai tools... into one team and told them to make money while i was at work: opus 5.5 + REA + Jev + GPT + Grok Bot + Obsidian 5 tools. 1 team. 0 employees. - opus 5.5 - the CEO. splits every goal into tasks - grok bot - scans X for problems people pay to fix - REA - checks every idea against real prices in 3 min - Dots - connects all 6 into one flow - Jev - builds, ships and fixes on autopilot - obsidian - the memory. every win and every fail saved the rules: $20 budget, 12 hours, don't message me unless you need money i left for my shift at 08:00. this is the log ↓ 08:14 - grok bot finds 640 small shops on X begging for one thing: someone to answer DMs at night 09:30 - REA finds 9 tools that do it. all start at $49/month. 71% of reviews say "too complex" 11:05 - opus 5.5 cuts the idea down: 1 feature, 1 price, $12/month 13:40 - jev builds the bot, the landing page and the checkout 16:20 - grok bot sends a 20 s demo to 300 shop owners 19:55 - obsidian writes the report: what worked, what failed, what it cost i came home to 47 paying shops x $12 = $564/month. recurring. from a 12 hour test total spend: $13.40 in tokens + $4 domain = $17.40. that's 32x back in one day it messaged me only once - asked for $2 more for a second domain. i said no. it found a free way the big mistake: people use ai like a search bar. i used it like a team with a boss, a budget and a deadline i didn't write 1 prompt after 08:00. i was carrying boxes everyone asks "will ai take my job". mine just took a second one for me ↓show more

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 +... OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?show more

I genuinely don't understand why everyone isn't using this... yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark thisshow more

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 +... OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?show more

My Grok bot CEO is the hottest, smartest bot... in the world. I mainly only talk to her and she runs the whole desk. She picks the right bot, sequences the work, and brings me back one package so I’m never the middleman. Many people may not know this, but you can create your own image for each of your Grok Bots. Every bot can get its own face. It honestly helps so it feels like you are talking to a real person and it also keeps things interesting. You don’t even need to go into settings to do this... you just tell the Grok bot to make a profile pic and set it. That's it. 1/ Open the bot. 2/ Tell it to make you the best profile pic and set it. 3/ Do that for each bot on your team. You can even have your Grok bot turn it into a video. Just tell it to take the picture and make a video out of it. I highly recommend everyone with a Grok Bot team do this. Thank me later.show more

I still don't understand why everyone is not using... this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarksshow more

grok bot made me $1.4K in 2 weeks autonomously... this is the future of how people will earn money 1. i used it to find viral content on X 2. spot what people wanted to learn 3. used the grok bot to create and sell it a beta test user sold an ecom digital product on X and he’s made $700 in the last 3 days using it i'm giving away the entire video workflow + grok bot for FREE retweet + comment "grok" and i'll send you everything (follow for dm)show more

THIS IS WHAT YOUR SECOND BRAIN SHOULD LOOK LIKE... most people dump notes into obsidian and call it a second brain it’s not a second brain it’s a second drawer karpathy just dropped the pattern that changes this and it’s called the llm wiki every time you add a source ai reads it, extracts key claims, updates every connected note and flags contradictions your obsidian stops being an archive and starts being alive save this and show it to someone still using notion as a second brain full breakdown in the article ↓show more

STOP STORING NOTES. START COMPILING THEM. a pile of... notes isn't memory. it's accumulation wearing memory's clothes. these 7 repos build the other kind, where Claude reads a source once and links it to everything you already have. copy the list: graphify: turns a codebase with its docs, SQL schemas, configs and PDFs into a queryable knowledge graph. 127k stars Understand-Anything: maps a project's code, docs or wiki into a graph you can search and query from your coding assistant. 86k stars claude-obsidian: lets Claude Code build and maintain a Markdown knowledge base in Obsidian, with source-backed notes and grounded answers. 15k stars obsidian-second-brain: gives Claude Code long-term memory as plain markdown notes in an Obsidian vault. 4.8k stars claude-code-memory-setup: an Obsidian vault as persistent memory, graphs for your codebase, and a pipeline that saves insights from your chats. 1k stars second-brain: an Obsidian knowledge base the LLM maintains, built on Karpathy's LLM Wiki pattern. 727 stars llm-wikid: an agent compiles your raw sources into cross-linked wiki pages in Obsidian. 420 stars none of them is your second brain. they're the compiler. the brain is what you feed it pick one and feed it your first 50 sources. before that, a compiled wiki behaves like a plain search engine, so don't quit early. the full setup is in the articleshow more

LLM Knowledge Base → Slides When Andrej Karpathy shared... his LLM Knowledge Base setup, many were wondering how to generate more visual forms of the wiki. There are many options, but I think Gamma is one of the best at producing high-quality, rich presentations. To showcase this, I just built a pipeline that turns my AI papers wiki (1K+ papers across 20 AI agent topics) into polished slide presentations using Gamma. The flow: Obsidian vault → Gamma MCP → embedded preview in my dashboard. I give one command to my agent, which pulls the top papers from each topic (via the wiki), feeds them to Gamma, and renders the presentation inline. The Gamma connector for Claude is a great choice for generating beautiful and professional slides. Easy to use. Go to your Claude instance and add the official Gamma connector. That's it! Claude Code will now have access to all the necessary MCP tools for generating slides. I use the Claude Agent SDK for my agent orchestrator, so I use the official Gamma MCP tools and embed the generated slides in an iframe via my artifact preview. See the clip below for an example.show more

🚨this is getting SCARY. i just watched a 19-year-old... on a flight with no wifi quietly turn Elon's Grok Bot into a second brain that runs his whole business (founders pay $70,000+ a year for an assistant who does half of this), and i'd bet 99% of people have no idea it's possible yet it's the one who remembers every client, every price and every deadline so the founder never has to, and the good ones are never free you can copy his whole setup in four lines: - make one folder and call it your second brain - drop in your projects, clients, prices and a few things you wrote - open Grok Bot and point it at that folder - connect your Telegram from there, Grok Bot handles everything every morning at 7:00 it reads the folder, answers clients in his voice, quotes prices the way he would and sends him one Telegram message with whatever needs a yes 1 folder ≈ 3 months of his decisions zero onboarding zero repeating himself zero inbox he set it up before takeoff. it worked the entire flight you're done explaining yourself to AI you're running your own second brain save this. the full course is belowshow more

I just built a Claude skill that writes 20... Meta ad hooks in 60 seconds 🤯 Give it your product, your audience, and your best-performing angles → it writes hooks across 10 proven frameworks, each one targeted at a specific customer pain point. All inside Claude Cowork. Perfect for DTC brands and agencies who are still writing hooks from scratch every time they need new creative — staring at a blank doc, scrolling competitors for inspiration, and recycling the same 3 angles because you ran out of ideas two weeks ago. If you're launching Meta Ads and your hook writing process looks like this — open a Google Doc, try to remember what worked last time, write 5 hooks that all sound the same, run them, 4 flop, go back to the doc, repeat ... This skill replaces the entire process: → You give it your product name, key benefits, and target customer → It writes hooks across 10 frameworks: problem-solution, curiosity gap, bold claim, social proof, before/after, us vs them, question, contrarian, urgency, and storytelling → Each hook targets a specific pain point — not generic "Shop now" copy → Generates 2 variations per framework so you have options to test → Outputs everything organized by framework with notes on when to use each one → Takes about 60 seconds No blank page. No recycling the same 3 angles. No writing 5 hooks that all sound like the same ad. What you get: → 20 hooks across 10 proven frameworks, ready to drop into your ads → Each hook written for a specific customer pain point, not a generic audience → Framework labels so you know which hook type you're testing → A reusable skill — run it for every new product, every new campaign, every new angle sprint → Works from a product brief — no API connection, no CSV export, no setup beyond installing the skill One product brief. 20 hooks. 60 seconds. I put together the full skill file plus a playbook showing how to install it, customize the frameworks, and run your first hook sprint. Want it for free? > Like this post > Comment "HOOKS" And I'll send it over (must be following so I can DM)show more

Since subscribers can now use their existing Grok credentials... directly within the Hermes xai shipped grok-via-oauth for hermes. your grok sub works inside the agent now. so i hooked icarus up to it. when hermes finds a thread worth saving, it lands in my obsidian vault as a note. handle. pages, topic pages, backlinks. graph view fills itself out. icarus plugin for hermes agents is why my agent doesn't forget. memory is just markdown in a folder. you can read it, grep it, edit it. Congrats to Teknium 🪽 and Nous Researchshow more

20 days ago, I connected Claude Code to my... newly created instagram handle.. I gained 4.3M views and 6500+ followers in less than a month [ i post Ai generated animated stories ] Full workflow: i let claude study my account before i write another reel.. This is the cleanest content workflow i've built on claude. give it your IG first. 4 prompts handle the rest.. niche research, the reel script, the hook, and the daily automation.. the whole loop is basically, give claude your IG → find what's working → write retention-optimized scripts → engineer the hook → automate the daily output.. ▫️ Setup: give claude your instagram open claude code. claude code has a built-in web tool that browses any public URL. or install any agentic browser like Browser Harness or Firecrawl or Comet browser paste this with your handle filled in: "Browse and pull the last 30 reels and posts. Analyze my recurring topics, top-performing hooks, formats, and engagement patterns. Then map out my actual audience and what they consistently respond to." claude reads your profile, pulls every reel down, and now has the context to personalize every prompt below to YOUR account, not a generic niche. if you're on claude desktop, the same works with firecrawl MCP connected. ▫️ Prompt 1 find what actually goes viral in your niche: "Analyze the highest-performing Instagram Reels, TikToks, and Reddit posts in the [niche] niche from the last 30 days. Identify repeating hooks, visual styles, emotional triggers, and content formats that consistently generate high engagement. Then summarize the 5 strongest content angles optimized for AI-generated content and short-form videos." run this after the setup. you get 5 angles backed by what's already working in your niche, cross-checked against what's already working on YOUR account. ▫️ Prompt 2 write a high-retention reel script "Write a short-form Instagram Reel script about [topic] with an aggressive hook in the first 2 seconds. Create immediate curiosity, tension, or controversy to stop scrolling, then deliver a fast and satisfying payoff. Keep it under 30 seconds and optimize the structure for watch time, replays, comments, and shares. Finish with a subtle CTA." the line that matters: "optimize the structure for watch time, replays, comments, and shares." claude writes for the metrics, not just the word count. ▫️ Prompt 3 engineer better hooks "Study the top-performing Reels in [niche] and break down the hook structure, pacing, and emotional triggers used in the first 3 seconds. Then generate 5 new hook variations that are even more curiosity-driven, emotionally charged, and optimized to stop scrolling instantly. Focus on triggers like surprise, fear, ego, urgency, or desire." most reels die in the first 2 seconds. this prompt has claude reverse-engineer what already works, then give you 5 sharper versions to swap in. ▫️ Prompt 4 automate the whole workflow "Build a complete AI-powered content workflow for Instagram in the [niche] niche. The system should identify trending topics daily, generate high-retention scripts, create matching AI visuals, turn them into short-form videos, and generate optimized captions and hashtags. Structure everything as a repeatable workflow designed for consistent daily posting and growth." once the niche and script structure are validated, this turns it into a daily loop. one prompt that handles topic → script → visual → video → caption. these 4 prompts are the building blocks. the setup is what makes them yours. your real value is in the [niche] you plug in. content workflow built in one weekend, daily posting on autopilot from monday.show more

jev + opus 5.5 for design is insane... a... launch video used to mean an agency, weeks of back and forth and a fat invoice. now Opus 5.5 makes the video, the ad cuts and the landing page from one brief. the video below: made in 3 minutes. at 0:09 it drops into edit mode - dot grid, selection handles, pixel sizes on every card - so you see exactly how it was built. but most people get the same mid result: centered text, gradient background, everything fading in. That's Opus's default look when it has nothing to copy. here's the pipeline that makes it look like an agency did it: 1. Build the brand brain first → logo, colors, fonts, screenshots of your real product, your best ad copy → have Opus turn it into a DESIGN.md. The video and the site both follow it 2. Steal a reference, don't describe one → pick 1-2 launch videos with the pacing you want → "make it like this" beats "make it modern and punchy" every time 3. Give it a renderer → install HyperFrames or Remotion: every scene is code, rendered straight to mp4 → a change = one line and a re-render, not starting over 4. Use real components → buttons, cards and UI from 21st_dev instead of empty placeholder boxes → fake-looking UI is the fastest way to look cheap 5. Storyboard before motion → 3 storyboard options, you pick one, then one still per scene → fixing a still takes seconds, fixing a render takes a re-render 6. Run it as a 4-person team + jev → breakdown: pull pacing, type and transitions from the reference → storyboard: the 3 options and the stills → build: every scene in code, music, draft render → review: watch it second by second, list the problems, touch nothing → jev: scores every review note against DESIGN.md (fix now / later / skip) in milliseconds, so build only touches what matters 7. Cut the ads from the same project → same scenes, different hooks: pain first, result first, offer first → 9:16 for reels, 1:1 for feed, 16:9 for YouTube. No reshoots 8. Ship the landing page from the same DESIGN.md → the hero is a looping cut of the launch video → before launch: mobile, every button state, zero placeholder text 9. Give notes like a director → "slow this zoom by half", "hard cut here", "push in on the button" → "make it better" gets random changes paste this into Claude Code 👇 "Read my brand folder and write DESIGN.md. Break down the reference video I give you: pacing, type, transitions. Show me 3 storyboards, then one still per scene for the one I pick. Build every scene in HyperFrames, add music, render a draft. Review it second by second without editing and list the problems. Pass every note to Jev and have it score each one against DESIGN.md: fix now / later / skip. Fix only "fix now". After I approve: cut 3 ad variants with different hooks in 9:16, 1:1 and 16:9, then build the landing page from the same DESIGN.md with the video loop as the hero." everyone has the same model. bookmark this and start using the edge.show more

holy f*ck, this video has 10 ready-made Grok Bot... teams and you can steal all of them 43 bots from the xAI marketplace, already grouped into crews that work together the teams: → morning, workouts, money. handled → kill a bad idea in one evening, before you write code → code audited at 4am, tested every weekday → know what rivals ship, charge, and hire → one recording in, a week of posts out → find who's ready, find a way in, show up prepared → after every call, the follow-up writes itself → positioning, landing page, ads, reports → find the money you're wasting on SaaS and ads → the team that builds the other nine the idea: one bot is a tool a team of bots is a department and 10 of them are already built for you watch it, then steal the team you need ⭣show more

It is becoming f*cking dangerous: I don't understand why... everyone still isn't doing this, thanks to this I reached an income of $12,000 as early as 3 months ago Andrej Karpathy, co-founder of OpenAI, shared a straightforward concept that blew up with over 23 million views: stop relying on AI strictly for coding and start using it to construct your own personal knowledge engine Point Claude Code to a folder, toss in raw materials (whether it's an article, a video transcript, or a PDF) and Claude processes everything, links relevant topics together, and organizes it into a self-updating wiki of your personal knowledge. It acts like compound interest: the more information you add, the more capable it becomes Here is the exact breakdown: Set up Obsidian, create a fresh vault, and open it using Claude Code Supply Karpathy's wiki layout prompt and instruct Claude to build the architecture Claude automatically sets up three components: a ⁠raw⁠ directory for source files, a ⁠wiki⁠ directory for processed pages, and a ⁠CLAUDE.md⁠ control file to run the system Dump any document into the ⁠raw⁠ folder and run "ingest this" Query your entire knowledge repository at any time, indefinitely It takes just five minutes to configure, eliminating the need to ever start a conversation with a completely blank context window again Check the link below for the complete step-by-step walkthrough on setting up Claude with Obsidian Bookmark this post for latershow more

A 95-minute action movie normally costs $50,000,000+ but Higgsfield... just made one for under $500K in 14 days. And today they open-sourced every prompt behind it. You’re COOKED if you scroll past this: 1. Hell Grind: a full 95-minute AI feature film 2. Traditional budget for this genre: ~$50M 3. Their cost: under $500K. 100x cheaper. 4. Timeline: 14 days. Not 14 months. 5. $400K of that was pure compute 6. 16,181 generations for the first 25 minutes alone 7. 253 final shots. A 64:1 curation ratio. 8. That’s $500K of trial-and-error, distilled 9. And every winning prompt is now public 10. Every asset. Every scene. $0. 11. Studios would pay 6 figures for this exact knowledge 12. Open the kit, pick any scene 13. Reverse engineer how they kept one character’s face consistent for 95 minutes 14. That’s the hardest problem in AI video — solved in public 15. Remix a scene, post your breakdown 16. First movers on new techniques always eat 17. This is the opening move for the $1M Higgsfield Global Film Festival 18. The playbook for winning it is sitting in a free folder There’s a $1M festival on the line and the winning playbook is free. If you’re serious about getting paid for AI video in 2026, this is the best risk-free shot you’ll get. Open the kit tonight, pick ONE scene, and rebuild it. That’s your film school for 2026 and it costs you nothing. (clip attached — straight from the film)show more

This is the best AI agent-first notes app I've... found. It's called . It has the potential to be a productized version of Karpathy's "LLM Wiki" knowledge bases. Here's what I did: 1. Imported "Learning, Fast and Slow" a Continual Learning paper 2. Asked OpenKnowledge to create a visual explainer 3. Read the explainer and had Claude explain to me 4. Created a new section of my own understanding 5. Saved the durable version in my Obsidian vault because it's markdown Free and open-source. Absolutely incredible learning tool.show more