diff --git a/01-claude-ocp/presentation.pdf b/01-claude-ocp/presentation.pdf
deleted file mode 100644
index ba32007..0000000
Binary files a/01-claude-ocp/presentation.pdf and /dev/null differ
diff --git a/03-skills/presentation.md b/03-skills/presentation.md
index 8aab3ec..d08dd5f 100644
--- a/03-skills/presentation.md
+++ b/03-skills/presentation.md
@@ -8,7 +8,7 @@ Skills: Teaching AI How to Think
 <!-- font_size: 2 -->
 Lazy-loaded expertise for efficient, reliable agents
 <!-- no_footer -->
-<!-- speaker_note: Title slide. Core message: skills make agents both smarter AND cheaper to run. -->
+
 <!-- end_slide -->
 
 
@@ -61,7 +61,6 @@ You have two bad options:
 Neither is acceptable.
 ===
 
-<!-- speaker_note: Set up the tension. Everyone building agents hits this wall. -->
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -98,7 +97,6 @@ graph TD
 
 **SKILL.md is the brain. Everything else is optional.**
 
-<!-- speaker_note: The SKILL.md IS the SOP. Scripts and templates are scaffolding. -->
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -151,7 +149,7 @@ graph LR
 
 **10 skills × 2,000 tokens = 20,000 always loaded → ~500 base + 2,000 on demand**
 
-<!-- speaker_note: This is the efficiency win. 10x reduction in baseline context. Analogy: a pro doesn't carry every manual — they know which shelf to reach for. -->
+
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -209,7 +207,7 @@ The SKILL.md **is** the standard operating procedure.
 
 **Runbook vs. "figure it out"**
 
-<!-- speaker_note: This is the reliability win. Same request, wildly different outcomes. Like giving a junior engineer a runbook vs saying figure it out. -->
+
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -254,7 +252,6 @@ graph LR
 
 Tools without skills = workshop full of power tools, no training
 
-<!-- speaker_note: All three layers are needed. Tools are hands, prompts are personality, skills are expertise. -->
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -283,7 +280,7 @@ Real-World Examples
 
 * **Skill Creator** 🏗️ — A meta-skill: a skill for *building skills*. Encodes the structure, best practices, and packaging conventions.
 
-<!-- speaker_note: Range from trivial to deeply complex. The ST skill is a great example of tribal knowledge capture. -->
+
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -344,7 +341,7 @@ graph LR
     style F fill:#ffd93d,stroke:#333,color:#000
 ```
 
-<!-- speaker_note: This is the strategic argument. Skills aren't just operational convenience — they're knowledge management that actually works. -->
+
 <!-- no_footer -->
 <!-- end_slide -->
 
@@ -373,5 +370,5 @@ Capture knowledge. Scale it. Share it.
 <!-- font_size: 2 -->
 🎯
 <!-- no_footer -->
-<!-- speaker_note: Closing. The question isn't whether your agents need skills — it's what expertise you'd encode first. -->
+
 <!-- end_slide -->