Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

If you're a student, build this before your next exam. Every lecture note goes into one folder. Opus 5.5 sorts it, links it and finds what connects across classes. Then you ask it: "What will probably be on the exam?" "Explain the 3 topics I understand least." "Quiz me... show more

CyrilXBT

197,032 subscribers

13,772 views • 6 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

2 Comments

Vipul Kumar Kewat6 days ago

This turns passive note-taking into active studying.

Genius💡💹🧲 🤖6 days ago

Dumping every lecture note into one folder and letting AI sort it is smart ngl

Related Videos

i asked opus 5.5 to read every note i wrote this year and tell me what i keep avoiding it took [real time] it said: "[paste its actual answer]" it was right. that's not a notes app anymore. full course on how to build it below

i asked opus 5.5 to read every note i wrote this year and tell me what i keep avoiding it took [real time] it said: "[paste its actual answer]" it was right. that's not a notes app anymore. full course on how to build it below

CyrilXBT

14,327 views • 6 days ago

POV: your notes finally talk back "You wrote about this exact problem in March." "These 3 notes contradict each other." "You promised Sam a follow up 9 days ago." "This idea has 14 links and you never posted it." That's Opus 5.5 running a second brain. How to build it in under an hour 👇

POV: your notes finally talk back "You wrote about this exact problem in March." "These 3 notes contradict each other." "You promised Sam a follow up 9 days ago." "This idea has 14 links and you never posted it." That's Opus 5.5 running a second brain. How to build it in under an hour 👇

CyrilXBT

33,544 views • 7 days ago

BEFORE: 2,000 notes. Zero I could find. Inbox full of guilt. AFTER: Inbox empty every morning. Every note linked. Weekly review written for me. Same notes. Different brain. The difference is Opus 5.5 and one CLAUDE. md file. How to set it up from scratch 👇

BEFORE: 2,000 notes. Zero I could find. Inbox full of guilt. AFTER: Inbox empty every morning. Every note linked. Weekly review written for me. Same notes. Different brain. The difference is Opus 5.5 and one CLAUDE. md file. How to set it up from scratch 👇

CyrilXBT

31,206 views • 7 days ago

Hot take: Organizing your notes is a waste of your time. Folders. Tags. Templates. Color codes. You spent 40 hours building a system you stopped using in week 3. Your only job is CAPTURE. Opus 5.5 does the sorting, linking and resurfacing. You capture. It organizes. You decide. How to set it up from scratch 👇

Hot take: Organizing your notes is a waste of your time. Folders. Tags. Templates. Color codes. You spent 40 hours building a system you stopped using in week 3. Your only job is CAPTURE. Opus 5.5 does the sorting, linking and resurfacing. You capture. It organizes. You decide. How to set it up from scratch 👇

CyrilXBT

13,536 views • 6 days ago

Most people use Claude to get answers. That is why they forget everything a week later. Real learning is not answers. It is a system: - map the skill - find the 20% - study in sessions - get tested - expose weak spots - compress into one page - explain it back simply Claude should not be your shortcut. It should be your teacher, examiner, curator, and feedback loop. Ask it to quiz you until the gaps show. Ask it to re-teach only what you missed. Ask it to turn messy notes into a path. The best learners are not collecting more resources. They are building tighter loops. Bookmark this before you ask Claude to “explain this” again.

Most people use Claude to get answers. That is why they forget everything a week later. Real learning is not answers. It is a system: - map the skill - find the 20% - study in sessions - get tested - expose weak spots - compress into one page - explain it back simply Claude should not be your shortcut. It should be your teacher, examiner, curator, and feedback loop. Ask it to quiz you until the gaps show. Ask it to re-teach only what you missed. Ask it to turn messy notes into a path. The best learners are not collecting more resources. They are building tighter loops. Bookmark this before you ask Claude to “explain this” again.

Fluixo

26,165 views • 3 months ago

6 commands replaced my entire productivity stack. /process → empties my inbox /connect → finds links I missed /review → tells me what I forgot /ask → answers from MY notes /draft → turns notes into posts /decide → turns notes into decisions One Obsidian vault. One Opus 5.5. Full course with every prompt below. Save this.

6 commands replaced my entire productivity stack. /process → empties my inbox /connect → finds links I missed /review → tells me what I forgot /ask → answers from MY notes /draft → turns notes into posts /decide → turns notes into decisions One Obsidian vault. One Opus 5.5. Full course with every prompt below. Save this.

CyrilXBT

37,695 views • 7 days ago

SOMEONE FROM THE ANTHROPIC TEAM LEAKED THEIR OBSIDIAN SETUP. 8 MILLION PEOPLE SAW HOW HE ACTUALLY USES CLAUDE the funniest part? all of this information was sitting in claude's documentation from day one. nobody read it one guy did, packed it into a 9-step guide and posted it. and it broke the internet. 4,100 likes, 800 retweets, then china picked it up and 8 million views want to know what's in it? one file. called CLAUDE.md. it holds everything about you: how you think, what you're working on, where you get stuck, even how you want the ai to talk to you. claude reads it first every single session one file changed everything. because now ai doesn't open with "how can i help?" it already knows. it remembers your projects, sees your goals, catches moments where you're contradicting yourself people spent years searching for the perfect prompt. the right temperature. the magic formula. and the answer turned out to be not how you ask ai. but what ai knows about you before you even open your mouth then the guy went deeper. taught claude to work on a schedule. every morning at 7am the ai walks through all notes on its own, finds new stuff, links it, cleans what's stale. no command. no reminder and all of this runs on obsidian. free app. text files on your drive. no cloud, no lock-in. switch models tomorrow and the folder keeps working the most liked comment under the original post: "this is the difference between using ai and building a system. most people won't realize it until they waste hundreds of hours repeating themselves" hundreds of hours. you've already spent some of them full guide in the video. i break down finds like this every day - follow so you don't miss the next one

SOMEONE FROM THE ANTHROPIC TEAM LEAKED THEIR OBSIDIAN SETUP. 8 MILLION PEOPLE SAW HOW HE ACTUALLY USES CLAUDE the funniest part? all of this information was sitting in claude's documentation from day one. nobody read it one guy did, packed it into a 9-step guide and posted it. and it broke the internet. 4,100 likes, 800 retweets, then china picked it up and 8 million views want to know what's in it? one file. called CLAUDE.md. it holds everything about you: how you think, what you're working on, where you get stuck, even how you want the ai to talk to you. claude reads it first every single session one file changed everything. because now ai doesn't open with "how can i help?" it already knows. it remembers your projects, sees your goals, catches moments where you're contradicting yourself people spent years searching for the perfect prompt. the right temperature. the magic formula. and the answer turned out to be not how you ask ai. but what ai knows about you before you even open your mouth then the guy went deeper. taught claude to work on a schedule. every morning at 7am the ai walks through all notes on its own, finds new stuff, links it, cleans what's stale. no command. no reminder and all of this runs on obsidian. free app. text files on your drive. no cloud, no lock-in. switch models tomorrow and the folder keeps working the most liked comment under the original post: "this is the difference between using ai and building a system. most people won't realize it until they waste hundreds of hours repeating themselves" hundreds of hours. you've already spent some of them full guide in the video. i break down finds like this every day - follow so you don't miss the next one

kai

174,650 views • 2 months ago

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: 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. Claude reads it, links it, 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: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: 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. Claude reads it, links it, 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: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

332,714 views • 3 months ago

Tiago Forte wrote a whole book on building a second brain. The hardest part was never the method. It was finding the time to sort, link and review your notes every week. Opus 5.5 does that part now. Every morning. Every Sunday. Automatically. The method was right. It just needed a brain to run it. Full course below 👇

Tiago Forte wrote a whole book on building a second brain. The hardest part was never the method. It was finding the time to sort, link and review your notes every week. Opus 5.5 does that part now. Every morning. Every Sunday. Automatically. The method was right. It just needed a brain to run it. Full course below 👇

CyrilXBT

19,678 views • 6 days ago

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,643 views • 4 months ago

"how do you remember everything you read?" I don't. Claude does. every article, PDF, and transcript goes into one Obsidian folder. Claude reads it, breaks it into atomic notes, links it to the rest. I just ask. that's Karpathy's second-brain method. three folders, one file. full guide below.

"how do you remember everything you read?" I don't. Claude does. every article, PDF, and transcript goes into one Obsidian folder. Claude reads it, breaks it into atomic notes, links it to the rest. I just ask. that's Karpathy's second-brain method. three folders, one file. full guide below.

Kirill

88,119 views • 2 months ago

A Berkeley professor just leaked Anthropic’s CCA exam that opens the door to $750,000 jobs. In 20 minutes he covers every single topic on the exam and explains how to actually solve it. This exam shows exactly what you need to know about AI right now and what’s not worth your time. Watch the presentation first, then read the guide below on how to build a system that improves itself.

A Berkeley professor just leaked Anthropic’s CCA exam that opens the door to $750,000 jobs. In 20 minutes he covers every single topic on the exam and explains how to actually solve it. This exam shows exactly what you need to know about AI right now and what’s not worth your time. Watch the presentation first, then read the guide below on how to build a system that improves itself.

Anatoli Kopadze

196,948 views • 2 months ago

I have a visualiser book for all my classes. 1) It sets the standard for presentation/organisation 2) I put notes in it about where we are up to/what next 3) It helps me model text annotation or exam questions. 4) It helps absent students catch up. This is my Yr 10 GCSE book

I have a visualiser book for all my classes. 1) It sets the standard for presentation/organisation 2) I put notes in it about where we are up to/what next 3) It helps me model text annotation or exam questions. 4) It helps absent students catch up. This is my Yr 10 GCSE book

Nikki McGee

90,383 views • 2 years ago

I built a Claude skill that turns Claude Code into your personal coding tutor. The core insight: Claude Opus 4.5 is already the best tutor in the world. Anthropic cooked with this model! It has incredible emotional intelligence and deep coding knowledge. What this skill does is just provide a harness—a way for Claude to agentically build the right context about YOU so it can personalize the tutoring experience in exactly the right way. Here's what makes it work: Learner profile from day one. The first time you use it, Claude interviews you. It asks about your programming background, your goal (where do you want this to take you?), and who you are as a person. This gets saved and informs every single tutorial it ever writes for you. From the very first interaction, everything is 100% personalized. Tutorials that use YOUR code. When you ask to learn something, Claude doesn't give you generic examples from some blog post. It finds examples in the actual codebase you're working in. This makes concepts stick in a way abstract examples never do. Quiz mode with spaced repetition. You can run "/quiz-me" and Claude will test you on concepts you've learned. It tracks your understanding score for each tutorial. Then it uses spaced repetition to prioritize the next quiz—concepts you're shaky on come back in 2 days, concepts you've mastered fade to 55+ day intervals. It literally builds retention into the learning process. One central knowledge base across all your projects. Whether you're joining a new company and want to understand their codebase, learning from an open source project, or leveling up on your own vibe-coded project—all your tutorials live in one place (~/coding-tutor-tutorials/). So your personal coding-tutor accompanies you across all your coding adventures. The whole thing is a feedback loop: learn → quiz → retain → learn more → quiz → retain. Your tutorials evolve, your knowledge compounds, and Claude gets better at teaching YOU specifically over time. To install it in Claude Code: • Run /plugin to open the plugin manager • Add marketplace nityeshaga/claude-code-essentials • Enable coding-tutor plugin Here's the Github: And here's 20-mins of me walking you through how to use this plugin and how it works 👇🏽 Let me know if you use it to teach yourself something cool!

Nityesh

64,666 views • 9 months ago

Boris Cherny, creator of Claude Code: "Opus 5.5 does in a day what used to take your team a month. Most people will keep using it wrong." In 12 minutes he explains why Opus 5.5 needs less prompting than any model before, and why your old detailed prompts now work against you. Watch it, then read the article below on how to prompt Opus 5.5 👇

Boris Cherny, creator of Claude Code: "Opus 5.5 does in a day what used to take your team a month. Most people will keep using it wrong." In 12 minutes he explains why Opus 5.5 needs less prompting than any model before, and why your old detailed prompts now work against you. Watch it, then read the article below on how to prompt Opus 5.5 👇

Rahul

151,024 views • 15 days ago

you should spend an afternoon building a second brain with jev... here's how i'd set it up: > create one inbox for saved posts, articles, meeting notes and ideas... give your agent access to it > give jev your active projects and interests so it can sort incoming material into categories that mean something to you > have your agent find similar notes, then use jev to flag duplicates and spot which ones add something new > save everything with its original link and date so you can always check where it came from > whenever you start a task, have your agent search the archive and let jev score which notes are relevant > feed those into your writing agent before it starts working... your customer conversations, examples and previous decisions are already there writing a proposal? bring back what the customer said on the call and the case study that answers their objection. working on a post? pull up the idea you saved three weeks ago alongside your own notes on the topic. start with one project and the material you've already collected for it. ask your coding agent to build that workflow, then check what it brings back on your next real task.

you should spend an afternoon building a second brain with jev... here's how i'd set it up: > create one inbox for saved posts, articles, meeting notes and ideas... give your agent access to it > give jev your active projects and interests so it can sort incoming material into categories that mean something to you > have your agent find similar notes, then use jev to flag duplicates and spot which ones add something new > save everything with its original link and date so you can always check where it came from > whenever you start a task, have your agent search the archive and let jev score which notes are relevant > feed those into your writing agent before it starts working... your customer conversations, examples and previous decisions are already there writing a proposal? bring back what the customer said on the call and the case study that answers their objection. working on a post? pull up the idea you saved three weeks ago alongside your own notes on the topic. start with one project and the material you've already collected for it. ask your coding agent to build that workflow, then check what it brings back on your next real task.

J.B.

13,511 views • 21 days ago

I just built a skill called 'Explain This'. It explains anything to you, tailored to how you learn. It's inspired by Geoffrey Litt's talk at AI Engineer: 'Understanding is the New Bottleneck'. AI can generate infinite code and content, and the scarce thing now is a human who actually understands. How often have you realized you read something but retained none of it? I built '/explain-this' to solve that. How it works: 🧠 It interviews you first. Ten minutes on what you know deeply, how explanations land for you, and what you're aiming to become. That generates your LEARNER.md profile. 📄 Then point your agent at any paper, PDF, or blog post and say "explain this." ✍️ It writes an explainer doc straight into your notes. Obsidian, OpenKnowledge, wherever you think, anchored to what you already know, skipping what you don't need to learn again. ✅ Every explanation ends with a quiz, and it grades your answers. Mastery learning means you don't move on until you prove to yourself you understood. 🔁 Your misses become spaced-repetition cards. Say "quiz me" next week and it re-teaches what didn't stick. Over time it learns your actual weak spots from evidence. Works in Claude Code or any agent that supports skills. Free and open source. Link to GitHub below. 👇

Dan McAteer

27,296 views • 2 months ago

Claude Opus 5.5 with this prompt is a f*cking cheat code paste it in and Opus 5.5 designs the whole system for you: > the agents and what each one owns > the prompt each agent runs on > the workflow, handoffs and stop conditions between them Claude Code tip: run it in plan mode first, cut every agent without a clear output, then let it build grab it before it becomes everyone's default playbook:

Claude Opus 5.5 with this prompt is a f*cking cheat code paste it in and Opus 5.5 designs the whole system for you: > the agents and what each one owns > the prompt each agent runs on > the workflow, handoffs and stop conditions between them Claude Code tip: run it in plan mode first, cut every agent without a clear output, then let it build grab it before it becomes everyone's default playbook:

Mr. Buzzoni

33,817 views • 4 days ago

AN ANTHROPIC ENGINEER LEAKED THIS OBSIDIAN CONVENTION you start with 12 notes and one convention. 6 months later you have 2379 and every one is linked to every one it belongs next to. you never touched the graph. claude did the convention is a domain prefix at the top of every markdown file. six characters. claude reads it, knows where the note belongs, and connects it to the older ones without you ever asking you drop in a new pdf at midnight. claude reads it, writes 8 linked notes, contradicts your old note from march, dates both versions, and pins the one you actually need on top by morning your vault stops being a folder. it becomes a night sky article in the first reply i test things like this on myself and share the results. follow kai if you want to see what's next

AN ANTHROPIC ENGINEER LEAKED THIS OBSIDIAN CONVENTION you start with 12 notes and one convention. 6 months later you have 2379 and every one is linked to every one it belongs next to. you never touched the graph. claude did the convention is a domain prefix at the top of every markdown file. six characters. claude reads it, knows where the note belongs, and connects it to the older ones without you ever asking you drop in a new pdf at midnight. claude reads it, writes 8 linked notes, contradicts your old note from march, dates both versions, and pins the one you actually need on top by morning your vault stops being a folder. it becomes a night sky article in the first reply i test things like this on myself and share the results. follow kai if you want to see what's next

kai

11,994 views • 2 months ago