AI Strategy / Foundation

You NEED to try these open-source AI projects RIGHT NOW

Matthew Berman reviews four under-the-radar open-source projects: Last 30 Days, a human-vote-powered trend search skill; Open Notebook, a local NotebookLM clone with podcast generation; Agent Skills, seven slash-commands mapping the engineering workflow; and Headroom, a context compressor claiming up to ~92% token savings for coding agents.

Matthew Berman16 minTranscript found

Quick learning frame

Read this before watching.

AI strategy is choosing where agents create durable leverage, then managing scope, adoption, risk, and measurable outcomes.

New playlist item from Matthew Berman; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Skill you build: The ability to discover, install, and evaluate open-source agent skills and tools β€” installing them by handing a GitHub URL to your coding agent and verifying their value on your own workflow.

Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.

Concept diagram

Where this video fits.

01Use Case
02Workflow
03Agent Role
04Metric
05Risk
06Adoption

Deep lesson

Turn this video into working knowledge.

2,943 cleaned transcript words reviewed across 842 timed caption segments.

Thesis

You NEED to try these open-source AI projects RIGHT NOW teaches a practical ai strategy move: Matthew Berman reviews four under-the-radar open-source projects: Last 30 Days, a human-vote-powered trend search skill; Open Notebook, a local NotebookLM clone with podcast generation; Agent Skills, seven slash-commands mapping the engineering workflow; and Headroom, a context compressor claiming up to ~92% token savings for coding agents.

The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.

0:00

Search by human votes

β€œI found four free GitHub projects that you probably haven't heard of that are so valuable. The first is a new type of search engine that is completely free, takes zero configuration, and actually works really well. We...”

Last 30 Days (40K+ GitHub stars, by Lyft co-founder Matt Van Horn) is a skill that searches Reddit, Hacker News, Polymarket, GitHub, X, YouTube, and TikTok in parallel, scores results by real human engagement β€” upvotes, likes, money-backed odds β€” and has an AI judge synthesize one brief, with an --emit=html option for shareable summaries. Install the skill in your coding agent, run /last30days on a topic you follow, and compare the human-vote-ranked brief against a normal Google search of the same term.

5:40

Local NotebookLM

β€œfantastic. So, check this out. 11 Agents by 11 Labs is a complete platform to design, deploy, and optimize real-time voice and chat agents that can not only speak, but also understand what you're trying to accomplish and...”

Open Notebook (~30K stars) ingests articles or thousand-page PDFs, answers questions with specific references, generates multi-host customizable podcasts (a 23-minute one from a single essay), and offers transformations like key insights and reflection questions β€” powered either by hosted models (GPT 5.5 for chat, text-embedding-3-large) or fully locally via Ollama or LM Studio. Install Open Notebook by pasting the repo URL into your agent, load one long document you actually need to read, and generate both a Q&A session and a podcast from it.

10:02

Compress your context

β€œme. And it's going to give you a step-by-step interview trying to extract exactly what you're looking to build. And it will then structure that in a really nice markdown file that you can then use for the...”

Headroom compresses everything your agent reads β€” tool outputs, logs, RAG chunks, and history β€” before it hits the LLM, reporting 92% savings on code search and incident debugging and 47% on codebase exploration with near-perfect accuracy on GSM8K, TruthfulQA, SQuAD v2, and BFCL; it wraps Claude Code via 'headroom wrap claude', shows savings with 'headroom perf', and 'headroom learn' mines failed sessions to write corrections into claude.md. Wrap your coding agent with Headroom (using the no-serena flag and disabling telemetry), work normally for a day, then run headroom perf to measure your actual token savings.

01

Use Case

Start with this video's job: Matthew Berman reviews four under-the-radar open-source projects: Last 30 Days, a human-vote-powered trend search skill; Open Notebook, a local NotebookLM clone with podcast generation; Agent Skills, seven slash-commands mapping the engineering workflow; and Headroom, a context compressor claiming up to ~92% token savings for coding agents. Treat "Use Case" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: β€œI found four free GitHub projects that you probably haven't heard of that are so valuable. The first is a new type of search engine that is completely free, takes zero configuration, and actually works really well. We...”

02

Workflow

Use "Workflow" to locate the part of the ai strategy workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 5:40, where the video says: β€œfantastic. So, check this out. 11 Agents by 11 Labs is a complete platform to design, deploy, and optimize real-time voice and chat agents that can not only speak, but also understand what you're trying to accomplish and...”

03

Agent Role

Turn "Agent Role" into the reusable artifact for this lesson: A one-page business case for one agent workflow. This is where watching becomes something you can inspect and reuse.

04

Metric

Use "Metric" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.

05

Risk

Use "Risk" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.

06

Adoption

Use "Adoption" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.

Example

Source-backed work packet

Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a one-page business case for one agent workflow..

Example

Claim vs. demo brief

Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.

Example

Teach-back module

Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.

Do not learn it wrong
  • Treating the title as the lesson without checking what the transcript actually says.
  • Letting the prompt drift into generic advice that could apply to any video in the playlist.
  • Copying the tool setup without identifying the operating principle that transfers to your own stack.
  • Skipping the artifact, which means the learning never becomes operational or inspectable.

Transcript-derived moments

Use timestamps to study the actual video.

Quality check

Do not count this as learned until these are true.

01

State the transcript-backed claim in your own words: Matthew Berman reviews four under-the-radar open-source projects: Last 30 Days, a human-vote-powered trend search skill; Open Notebook, a local NotebookLM clone with podcast generation; Agent Skills, seven slash-commands mapping the engineering workflow; and Headroom, a context compressor claiming up to ~92% token savings for coding agents.

02

Explain the practical stakes without hype: New playlist item from Matthew Berman; queued for transcript-backed review, topic mapping, and a practical learning artifact.

03

Map the idea onto the Use Case -> Workflow -> Agent Role -> Metric -> Risk -> Adoption sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: A one-page business case for one agent workflow.

Put it into practice

Give this grounded prompt to Codex or Claude after watching.

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: You NEED to try these open-source AI projects RIGHT NOW
- URL: https://www.youtube.com/watch?v=zjFE-dBzP_E
- Topic: AI Strategy
- My current learning frame: Install all four projects by handing their GitHub URLs to your coding agent, then run one real task through each β€” a trend search, a document podcast, an /interview-me spec session, and a Headroom-wrapped coding session β€” and keep the ones that measurably help.
- Why this matters: New playlist item from Matthew Berman; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "I found four free GitHub projects that you probably haven't heard of that are so valuable. The first is a new type of search engine that is completely free, takes zero configuration, and actually works really well. We..."
- 2:24 / Evidence 2: "engineering was born on June 7th, 2026. And the internet has spent the week fighting about it. Peter Steinberger posted, "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agent." and so..."
- 5:40 / Evidence 3: "fantastic. So, check this out. 11 Agents by 11 Labs is a complete platform to design, deploy, and optimize real-time voice and chat agents that can not only speak, but also understand what you're trying to accomplish and..."
- 7:38 / Evidence 4: "bunch of different settings with the podcast generation. You can have multi-host, you can have different tones, you can describe exactly what you want it to sound like. You can change the script. It's all hyper customizable because..."
- 10:02 / Evidence 5: "me. And it's going to give you a step-by-step interview trying to extract exactly what you're looking to build. And it will then structure that in a really nice markdown file that you can then use for the..."
- 11:34 / Evidence 6: "Headroom, and it effectively compresses the context that you are giving to your large language model, and it does so extremely well. Headroom compresses everything your AI agent reads. Tool outputs, logs, rag chunks, files, and conversation history..."
- 14:24 / Evidence 7: "features it has is this thing called headroom learn, which mines failed sessions and writes corrections to claw.md and agents.md. So simply type headroom learn, hit enter, and it's going to start analyzing your logs, looking for failed..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page business case for one agent workflow.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Use Case -> Workflow -> Agent Role -> Metric -> Risk -> Adoption
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "You NEED to try these open-source AI projects RIGHT NOW", not a generic AI Strategy essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.

Misconceptions

What to stop believing.

Every new AI tool deserves a trial.

Every tool has integration cost. Start from workflow pain, not novelty.

If an agent can do it once, it is automated.

Automation means repeatable, monitored, recoverable, and reviewable.

Practice studio

Learning only counts when you make something.

01

Transcript evidence map

Separate what the video actually says from what you already believe about the topic.

3 source-backed takeaways with timestamps, confidence, and a transfer note.
02

One useful artifact

Apply the video to a real workflow and produce a one-page business case for one agent workflow..

A reusable artifact with a done signal and one verification step.
03

Teach-back card

Explain the lesson to someone who has not watched the video yet.

A 90-second explanation, one diagram, one example, and one misconception to avoid.

Recall check

Answer first, then reveal β€” without rewatching.

How does Last 30 Days rank and synthesize information differently from Google search?

What can Open Notebook do with an uploaded document, and how can it run fully locally?

What does Headroom compress, and what evidence supports its claim that quality is preserved?

Source shelf

Use the video as a doorway, then verify with primary sources.

ReadingY Combinator Librarywww.ycombinator.com/libraryReadingOpenAI Businessopenai.com/business/