skills/92bilal26/notebooklm-slides/SKILL.md
Generate pedagogically-aligned slide decks from educational content using NotebookLM. Use when creating chapter slide presentations with proficiency-calibrated prompts. NOT for static slides or non-educational presentations.
npx skillsauth add aiskillstore/marketplace notebooklm-slidesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# 1. Start browser (via browser-use skill)
bash .claude/skills/browser-use/scripts/start-server.sh
# 2. Navigate to NotebookLM
# browser_navigate to notebooklm.google.com
# 3. Create notebook, upload sources, generate slides
# Use proficiency-calibrated prompts below
| Step | Action | Tool |
|------|--------|------|
| 1 | Navigate to notebooklm.google.com | browser_navigate |
| 2 | Create notebook: "Chapter X: Title" | browser_click |
| 3 | Upload ALL sources (lessons + README + quiz) | browser_click |
| 4 | Click "Slide Deck" in Studio panel | browser_click |
| 5 | Select "Presenter Slides" format | browser_click |
| 6 | Paste proficiency-calibrated prompt | browser_type |
| 7 | Click "Generate" (wait 5-30 min) | browser_click |
| 8 | Review with success criteria | Visual inspection |
| 9 | Download PDF | browser_click |
| 10 | Move to static/slides/chapter-{NN}-slides.pdf | Bash |
Create inspiring slide deck for absolute beginners (A2 proficiency).
AUDIENCE: Complete beginners with no programming experience.
FRAMEWORK TO EMPHASIZE:
• [Principle 1]: Simple, concrete explanation
• [Principle 2]: Accessible mental model
• [Principle 3]: Encouraging principle
THEMES (with specific data):
1. [Theme with concrete numbers/facts]
2. [Theme with specific example]
3. [Theme with real-world data]
TONE:
• Encouraging (not intimidating)
• Future-focused and opportunity-driven
• Simple language, no jargon
• Action-oriented
<slide_format_requirements>
Generate 12-15 slides. Each slide: 3-5 bullet points as sentences,
NOT paragraphs. Clear headings. Cover all themes.
</slide_format_requirements>
NARRATIVE: problem → transformation → opportunity → action
END WITH: Specific next steps (not "Keep learning!")
Create comprehensive slide deck for intermediate learners (B1 proficiency).
AUDIENCE: Learners with [prerequisites]. Ready for [next-level challenge].
FRAMEWORK TO EMPHASIZE:
• [Intermediate concept with practical context]
• [Problem-solving approach]
• [Real-world application pattern]
THEMES (with specific data):
1-5. [Themes with concrete examples]
TONE:
• Professional yet accessible
• Balance theory with practice
• Technical terms with context
• Critical thinking encouraged
<slide_format_requirements>
Generate 15-20 slides. Each slide: 4-6 bullet points.
Include practical examples and case studies.
</slide_format_requirements>
END WITH: Implementation strategies (step-by-step)
Create detailed slide deck for advanced practitioners (C1 proficiency).
AUDIENCE: Experienced with [advanced prerequisites].
FRAMEWORK TO EMPHASIZE:
• [Theoretical frameworks and trade-offs]
• [Industry patterns and anti-patterns]
• [Critical analysis and decision-making]
THEMES: [5-7 themes with industry data]
TONE:
• Professional and rigorous
• Nuance and complexity
• Industry-standard terminology
• Analytical and evaluative
<slide_format_requirements>
Generate 20-25 slides. Each slide: 5-7 bullet points.
Include architecture diagrams, decision matrices.
</slide_format_requirements>
END WITH: Production deployment strategies
| Gate | Check | Pass | Fail | |------|-------|------|------| | 1. Title | Reflects framework? | "AI Coding Revolution" | "Introduction to AI" | | 2. Language | Matches proficiency? | A2: simple, no jargon | A2 with technical terms | | 3. Themes | All 5-7 covered? | Each theme with data | Themes missing | | 4. Tone | Matches spec? | Encouraging (not academic) | Wrong emotional framing | | 5. Count | Within range? | A2: 12-15, B1: 15-20 | Outside range | | 6. Arc | Progression clear? | problem → action | Random sequence | | 7. Ending | Actionable? | Specific tasks | "Keep learning!" |
Score: 7/7 → Deploy | <7/7 → Iterate with refined prompt
Format: chapter-{NN}-slides.pdf (zero-padded)
# Example
mv ~/Downloads/"The-AI-Revolution.pdf" \
"apps/learn-app/static/slides/chapter-01-slides.pdf"
Add to chapter README frontmatter:
---
title: "Chapter 1: Title"
slides:
source: "slides/chapter-01-slides.pdf"
title: "Chapter 1: Title"
height: 700
---
Build-time plugin auto-injects PDFViewer before "What You'll Learn".
For 3+ chapters:
Daily limit: 3-5 chapters/day (NotebookLM enforced)
| Issue | Solution | |-------|----------| | Generation stuck >30 min | Check browser console, verify no daily limit message | | Text-heavy slides | Add explicit "3-5 bullets, NOT paragraphs" | | Generic title | Include example engaging title in prompt | | Missing themes | List all themes numbered with specific data | | Daily limit hit | Wait 24h (midnight PT reset), notebooks persist |
| Don't | Why | Do Instead | |-------|-----|------------| | Vague audience | NotebookLM can't calibrate | "A2 beginners with no programming" | | Skip framework | Generic output | Explicit 3-5 principles | | Single-word tone | Ambiguous | "Encouraging (not intimidating)" | | Leave format default | Text-heavy slides | Explicit bullet count | | Vague endings | No student action | Specific next steps |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.