How to Build a Personal Knowledge Base with Claude

What We're Building (and Why)

You consume a lot of content. YouTube videos, articles, podcasts, PDFs. But how much of it do you actually remember a week later? Probably not much.

That's the problem. You watch a brilliant 40-minute video full of frameworks and tips, and by next Tuesday it's gone. You bookmark articles and never open them again. You take notes that sit in a folder collecting dust.

The solution is a system where you paste a URL or drop a file, and Claude turns it into a structured knowledge note. Not a vague summary. A complete, organised reference you can actually use later.

Over time, this becomes your personal reference library. 10 notes. 50 notes. 100 notes. Every insight, every framework, every useful tip, all structured and searchable.

Here's the magic: Claude can read your knowledge base at the start of every session. It knows what you know. When you ask it to write something, it pulls from your actual learnings, not just its general training.

How It Works (The Flow)

The whole system is simple. Content goes in, structured knowledge comes out, and Claude gets smarter every time.

• 1You find something worth saving. A YouTube video, a blog post, a PDF, your own notes.
• 2You give Claude the URL or paste the content directly.
• 3Claude extracts everything: every tip, framework, prompt, example, and stat.
• 4It reorganises the content into clear sections. Not just a summary, a complete reference.
• 5It saves it as a markdown file in your knowledge/ folder.
• 6It updates an index file so you (and Claude) can see what's in the library.
• 7Next session, Claude reads the index and knows what knowledge you have available.

Set Up the Folder Structure

First, you need a place for your knowledge to live. This takes about 30 seconds.

In your workspace, you'll create a simple folder structure:

You don't need to create this manually. Just ask Claude to do it. Open Claude Code or start a new task in Cowork and type:

Claude will create the folders and files in seconds. You'll see them appear in your workspace.

Create the Knowledge Skill

This is the key step. You're creating a custom skill that tells Claude exactly how to process content into knowledge notes.

A skill is a reusable instruction set. Once you create it, you can trigger it anytime with a simple command instead of re-explaining what you want every time.

In Claude Code, paste this prompt:

Claude will create the skill file in your workspace. From now on, you just type /learn followed by a URL and it handles everything.

Process Your First Piece of Content

Time to test it. Pick a YouTube video or article you found valuable recently and feed it to Claude.

Try it with a YouTube video:

Or with an article:

What you get: A structured markdown file in your knowledge/ folder. It will have clear sections, bullet points, frameworks, and every detail from the original content. Not a summary. A complete reference.

• 1Open the file and check it. Is everything there? Did Claude capture the key frameworks? Are the examples preserved in full?
• 2Give feedback if needed. If something is missing, just tell Claude: "You missed the section about pricing. Go back and add it." Claude will update the file.
• 3Check the index. Open knowledge/index.md. Your new note should be listed there with a title and one-line description.

Process Multiple Items at Once (Batch Mode)

Processing one thing at a time works great. But the real power comes when you batch process a whole week's worth of content in one go.

Throughout the week, save things as you find them:

• 1Paste URLs into knowledge/inbox/links.txt, one per line. YouTube videos, blog posts, articles.
• 2Paste raw text into knowledge/inbox/notes.txt. Meeting notes, Instagram captions, quotes, ideas. Separate each item with --- NOTE BREAK --- on its own line.
• 3Drop PDF files directly into knowledge/inbox/. Reports, whitepapers, ebooks.

Then, when you're ready to process everything, ask Claude:

Claude will work through each item, create a separate knowledge note for each one, and update the index with all the new entries.

Make Claude Read Your Knowledge

Your knowledge base is useless if Claude doesn't know it exists. This step connects everything together.

You need to tell Claude to check your knowledge base at the start of every session. The way to do this depends on which tool you're using.

Now every session, Claude sees your full library. When you ask "write a post about AI automation", Claude pulls from your knowledge: "Based on the video you watched about workflow automation and the article on AI tools for small teams, here's an angle..."

Build the Index

The index is the master list of everything in your knowledge base. It's how Claude (and you) can quickly see what's available without opening every file.

A good index shows the title, a one-line description, the source, and the filename for each note. It should be grouped by category so you can scan it quickly.

Here's what an index looks like:

Ask Claude to build or rebuild the index anytime:

Your /learn skill should update the index automatically every time you add a new note. But if things ever get out of sync, just ask Claude to rebuild it from scratch.

What to Feed It

Anything worth remembering is worth adding to your knowledge base. Here's what works well.

What You've Built

Let's step back and look at what you now have.

You've built a personal AI knowledge base that:

• 1Turns any content into a structured, searchable reference. YouTube videos, articles, PDFs, notes. All organised and easy to find.
• 2Builds over time. 10 notes, 50 notes, 100+ notes. Every week it gets more valuable.
• 3Makes Claude smarter about your specific interests. Not generic AI knowledge. Your knowledge. Your frameworks. Your insights.
• 4Never forgets anything you've learned. That brilliant framework from a video three months ago? It's still there, structured and ready to use.
• 5Gives Claude real context. When creating content, writing documents, or answering questions, Claude draws from what you've actually learned, not just its general training.