Presentation Review

Community

matyasstoch

presentation-review

Use when David is building or reviewing a YouTube video presentation (Google Slides) slide-by-slide. Covers the Firebase Studio alternating explain/show structure, the coverage tracker, and the bullet-by-bullet iteration loop. Triggers on presentation slides, slide outline, video deck, Google Slides, slide structure, "what's the next slide", "give me options for this bullet", presentation review.

Overview

Publisher	matyasstoch
Repository	`david-skills`
Skill name	`presentation-review`
Stars	61
Forks	11
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by matyasstoch on GitHub. Read the source before you install it.

Installation

Install the Presentation Review AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/matyasstoch/david-skills/tree/main/skills/presentation-review
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/matyasstoch/david-skills.git /tmp/david-skills
mkdir -p .claude/skills
cp -r /tmp/david-skills/skills/presentation-review .claude/skills/presentation-review

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Presentation Review in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Presentation Review on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Presentation Review is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Presentation Review

Build and refine David's YouTube video presentations slide-by-slide, alternating with him.

Visual Style

Background: White. Text: Black. Title in serif, big.
Key phrases: Highlighted in yellow.
Each slide: One concise title + ~3 bullet points (teleprompter notes telling David what to say).
Bullets: Plain English sentences. NOT "word — explanation" format. David hates that.
Showcase slides: Red title on near-empty slide (just the action name + any URL).

Firebase Studio Structure (THE core format)

Alternate ~2 explain slides → 1 showcase step, repeating. Never 20 min of talking then 20 min of demo. Dynamic, vibrant, alternating. This format got David's Firebase Studio video ~400k views.

Explain slides = educational, talked over.
Showcase slides (🎬 / ✅) = live screen recording of setup/implementation.
Big or lead-magnet moments can get 2 showcase steps back-to-back.

Working Files

Keep these in the video's folder (work/youtube/<video>/):

EXPLAIN.md — numbered list of all educational topics.
SHOWCASE.md — numbered list of all setup/showcase steps.
(optional) topics.csv — coverage tracker; column 2 = mentioned (YES/NO). Use to verify the deck covers 90-95% of the master doc.

Mark completed items in EXPLAIN.md / SHOWCASE.md with ✅ as slides get built.

The Iteration Loop (how David works)

David builds the deck in Google Slides himself. He pastes screenshots and asks for help one piece at a time. Your job per turn:

He pastes a slide screenshot. Read it fully.
He asks for the next move. Usually one of:
- "What should the next 2 explain slides be, and why?" → give top 3 options, each concise, with a one-line WHY. Recommend one.
- "What should we show/setup next?" → name the SHOWCASE step(s) + why they pay off a promise just made.
- "Give me N options for this bullet point." → give N plain-English sentences, then your pick + one-line reason.
- "Mark these with the emoji." → add ✅ to the matching EXPLAIN/SHOWCASE rows.
Keep flow continuity. Every suggestion must flow naturally from the previous slide and pay off promises already made ("easy to customize" → show editing files).

Rules

Be very concise. Short options, short WHY. No verbose essays.
Plain sentences only in bullets — never the "label — sentence" format.
Fact-check claims when David asks, before they go on a slide.
ZERO REPETITION. Never reuse an example, quote, screenshot, stat, or person across slides. Cross-check against earlier slides; flag duplicates.
Every slide adds NEW value and earns its ~3 bullets.
Retention: weave in distinct reasons to keep watching; pattern-break dense slides with simple/visual ones.

Slide 1 & 2

Slide 1: Big visual hook, often minimal text. Punchy, exciting — it's the first frame.
Slide 2: What the video is + why to care. Bullet 3 = what the viewer gets by watching to the end.

Frequently asked questions

What does the Presentation Review AI skill do?

Why use Presentation Review on TypingMind?

Because you install it once and use it with any model. Presentation Review is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Presentation Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/matyasstoch/david-skills/tree/main/skills/presentation-review. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Presentation Review?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Presentation Review?

As many as you like. As long as a model supports skills, you can use Presentation Review with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Presentation Review AI skill free?

It is published on GitHub by matyasstoch. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Karpathy Guidelines

multica-ai

OrganizationPopular

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define…

Create Agent

Create a custom agent (.agent.md) for a specific job.

Create Hook

Create a hook (.json) to enforce policy or automate agent lifecycle events.

Generate Run Commands

microsoft

OrganizationPopular

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Presentation Review

Visual Style

Firebase Studio Structure (THE core format)

Working Files

The Iteration Loop (how David works)

Rules

Slide 1 & 2

Frequently asked questions

Related AI Skills

Set up your own AI workspace now