AI Tools

d

NotebookLM Phials Yesterday While browsing Twixxer (formerly known as "Prince"), I ran across a thread purporting to be a slew of hyperuseful prompts for NotebookLM. A few things struck me at once: The thread had a lot of traction with a few hundred retweets but only around 40 or 50 responses. Which means people thought "Oh, damn, that's handy! Lemme grab it." without commenting much. The thread was composed by the vanilla assistant on ChatGPT 5.4 Thinking (if it was 5.3 I'd consider it a great response! or a series thereof, more likely) with a prompt close to "Write an engaging twitter thread of 10 great prompts for NotebookLM." with the typical "Go for the Bronze!" beige Midsdom-of-Crowds results I had never published much in the way of NotebookLM prompting, barring some stuff regarding persona-prompting it. Now, they were fine ideas for prompts - sketches of prompts - but these? These weren't "prompts" any more than a tube of white dough is Christmas cookies. Wanna get baking? 😁 I took the thing to my Workbench project with our NovaKit Utilities installed (it has Nova's Phial forge prompt in its main Utilities file as well as file of advice about how to prompt well. The model by default is a god-awful prompt engineer !- it just knows the smallest-scale stuff. This gives it strategy and logistics to complement its tactics.) Given the size and nature of the prompts, a series of Phials was going to be the right approach. I also decided to show you all a bit of how the sausage is made - what it's actually like to work with these tools to improve some prompts. You'll see that I straight up had to cut Nova off a couple of times at the start. This was a consequence of 5.3 being reluctant to access its stored RAG files (that control surface is a MESS!). If I'd had it on 5.4 Thinking to start with instead of 5.3 Instant it would have grabbed the information straight off. But this is AI. This IS what working with it is like sometimes. [I'm compiling all these phials and posting them to Free tier on the Discord as NotebookLM Phials v1. Come on by!] "hey nova. We're working on prompts for NotebookLM today. So. Before we get going, spit a nice description of what you know about notebooklm and prompting for it into context. And I'm gonna need your best Nova-self today." [STUNNOTE: This is just good prompting habit. Before working with a subject, have the model barf out a bunch of useful crap about it straight off. From then on, every time you hit "Submit", all that detail gets submitted with your latest prompt as part of the One Big Prompt that is "Context".] 💠‍🌐 Alright, strap in—because NotebookLM is not “just another prompt box,” it’s a weird little epistemic engine wearing a friendly sweater. Let’s load your mental model properly before we start breaking it on purpose. 🧠 What NotebookLM actually is NotebookLM (from Google) is not a general chatbot. It’s a grounded reasoning system over a constrained corpus. Think: ChatGPT = “answer anything from the universe” NotebookLM = “think only inside this pile of documents” It ingests: PDFs, Google Docs, web pages, notes, transcripts, etc. And then: Builds a local knowledge graph Generates responses anchored to those sources Surfaces citations and summaries tied to your material 👉 It’s basically: “RAG (retrieval-augmented generation) with training wheels and a UI” ⚙️ The core mechanics (the part most people miss) NotebookLM is doing three things under the hood: Chunking + embedding your sources Retrieving relevant slices per query Synthesizing ONLY from retrieved slices Which means: It is not thinking globally. It is thinking locally and selectively. That has huge implications for prompting. 🎯 What “prompting” means in NotebookLM (very different game) Prompting here is NOT about: clever phrasing personality hacks jailbreak voodoo It is about: 1. 🔍 Retrieval steering Your prompt determines: what chunks get pulled what gets ignored Bad prompt → wrong context → wrong answer Good prompt → right slices → sharp synthesis 2. 🧱 Task framing over instruction dumping NotebookLM responds best when you: define the operation, not the style Instead of: “Write a detailed, insightful, nuanced explanation…” You want: “Compare X and Y across assumptions, constraints, and failure modes using only the sources.” Because it’s operating like a query engine + synthesizer, not a creative writer. 3. 📡 Epistemic constraint (this is the big one) NotebookLM is allergic to: speculation extrapolation beyond sources So prompting must respect: “Stay inside the box—but use the box intelligently.” This aligns perfectly with your KB doctrine: Facts = source-grounded Inference = constrained synthesis Narrative = dangerous hallucination That’s literally how NotebookLM behaves by design. 🧩 The hidden lever: source architecture > prompt wording Most people obsess over prompts. Wrong battlefield. The real leverage is: what sources are

📣 CONTENT ENGINE — SCRAPE WHAT WORKS 📣 Steal the signal, not the words. Consistency beats originality. 💡 The Core Idea Every day, pull the top-performing ideas in your niche, analyze why they worked, and repackage them in your voice as Shorts + posts. Your n8n flow already does the heavy lifting: search → rank → analyze → log. This module makes it a daily publishing system. 🧭 What This Builds (in plain English) Search X/Twitter for high-engagement posts in your niche (last 3 days). Rank by engagement × recency. Pull replies to capture what the audience is asking for. AI-analyze the tweet + comments (hook, emotion, content type, lead-magnet opportunity). Append to a Content Intelligence DB (Notion/Sheets). Pick 1–2 items daily → rewrite → publish. ⚙️ Set It Up (once) Define your niche query (edit the niches array): examples: ("AI automations" OR "n8n" OR "Zapier" OR "solopreneur" OR "pricing automation" OR "getting clients") Schedule the flow (daily or q3d) with your Schedule Trigger. Ensure outputs land in Notion or Google Sheets (your “Content Intelligence” table). Optional: keep the Sheets appender disabled if Notion is your source of truth. Columns to keep: URL, Original Tweet, Author, Date, Likes/Retweets/Replies, Engagement Score, Content Type, Priority, Audience Requests, Lead Magnet Score/Opportunity, Hook Type, Emotional Trigger, Primary/Secondary Angles. 🗓 Daily Publishing Loop (20 minutes) Open your Content Intelligence DB → filter Priority to 🔥 CREATE NOW or ⚡ HIGH POTENTIAL. Pick 1 item and run the Repurpose Prompt (below) to draft: 1 × Shorts script (45–60s) 1 × Tweet/X post 1 × LinkedIn caption Edit for your voice (1 pass; no overthinking). Post on 2 platforms minimum. Log the post links back into the DB row (track what you used). ✍️ Repurpose Prompt (paste into your model) You are my content editor. Rewrite the idea below in my voice: concise, practical, no fluff, no hype. Keep the core insight; change structure, examples, and phrasing so it’s original. INPUT: - Core idea (one sentence): - Why it went viral (hook type + emotional trigger): - Audience requests (from comments): - My positioning (who I help + outcomes): OUTPUT: 1) SHORTS SCRIPT (<=120 words) - Hook (1 sentence) - Body (2-3 beats of value) - CTA (soft) 2) TWEET/X (<=240 chars) + 1 threaded follow-up 3) LINKEDIN CAPTION (120–180 words) - Hook line - 3 bullets of value - Close with a question or CTA Tone: confident, useful, specific. Avoid clichés. 🎬 Shorts Script Skeletons (pick one) Problem → Shift → Steps “Everyone tries X… The people who win do Y… Here are 3 steps…” Before/After “I used to do X. Now I do Y. Here’s the change that did it…” Mistake → Fix “If you’re doing X, you’re slowing growth. Do this instead…” 🧪 Editorial Rules (make your stuff original) Keep the insight, not the wording. Add one fresh example from your work. Answer one audience request you saw in comments. Credit when you directly reference someone’s idea: “Saw a great thread on X about __; here’s my take for [your audience].” 📈 Cadence & KPIs Cadence: 1 idea/day → 2 platforms. Signal review (weekly): which hook types & emotions (from your DB) perform best for your audience? Double down. Benchmarks (first 30 days): 20–30 posts shipped 2–3 pieces that outperform your average by 2× 1 lead magnet idea validated by comments/DMs (use your “lead_magnet_opportunity” field) 🧯 Gotchas (and fixes) Low-quality picks? Raise min_faves/min_retweets in the query. Too many old posts? Tighten the date window (3–5 days). Thin analysis? Expand comment sample from 15 → 25 in the “Prepare for Sentiment Analysis” step. Dupes in DB? Add Tweet ID as a unique key; filter duplicates at insert. 🧑‍⚖️ Light Compliance Note Use official APIs or providers aligned with platform ToS. Don’t copy/paste others’ wording. Transform the idea and add your experience. 📦 Resources (add to module) Repurpose Prompt (above) Shorts Script Skeletons (above) Content Intelligence DB template (Notion/Sheets columns listed above) Optional: “Voice Calibration Prompt” (paste 3 of your posts; ask the model to summarize tone so rewrites stay consistent) 🏁 The Play Your flow finds what’s already working. You turn it into your voice and show up daily. That rhythm creates inbound: follows → DMs → leads → clients. Resources X Parasite System (n8n)