Prompt Details
Model
(claude-5-5-opus)
Token size
597
Example input
[TOPIC]: why a SQL query is slow
[AUDIENCE]: junior data engineers
[LENGTH]: 30
[TONE]: confident, direct
Example output
Topic: why a SQL query is slow | Target viewer: junior data engineers | Length: 30 | Tone: confident, direct
## 1. Five hooks
a) One missing index turned my 40-second query into 0.2 seconds.
b) Fix a slow SQL query in 30 seconds.
c) Stop writing SELECT star on big tables.
d) Same query: 40 seconds before, 0.2 seconds after.
e) Your query is slow for one boring reason.
★ (a) - a concrete before/after number earns the next 2 seconds better than any warning.
## 2. Script
| Time | Spoken line | On-screen text | Visual / B-roll |
|---|---|---|---|
| 0-2s | One missing index turned my 40-second query into 0.2 seconds. | 40s → 0.2s | Query timer counting up, freezes at 40.1s |
| 2-6s | Most slow queries are not complex. They read too much. | Reads too much | Table of 10M rows scrolling fast |
| 6-11s | Run EXPLAIN first. Look for the words "Seq Scan". | EXPLAIN | Terminal: EXPLAIN output, "Seq Scan" highlighted |
| 11-16s | Seq Scan means the database checks every single row. | Every row | Cursor sweeping row by row |
| 16-21s | Filtering on customer_id? Index that column. | Index the filter | `CREATE INDEX ON orders(customer_id);` typed |
| 21-26s | Run EXPLAIN again. Now it says Index Scan. | Index Scan | Same output, line flips to Index Scan |
| 26-30s | Forty seconds became 0.2. One missing index. | One index | Timer: 0.2s, cut back to opening frame |
## 3. Titles
1. 40s to 0.2s with one SQL index
2. Why your SQL query is slow
3. Read this before you blame the database
4. EXPLAIN in 30 seconds
5. 1 line that fixed my slow query
## 4. Thumbnail / cover
1. "40s → 0.2s" - split frame, red timer left, green timer right. Dominant color: red.
2. "SEQ SCAN = SLOW" - terminal close-up with the phrase circled. Dominant color: amber.
3. "ONE LINE" - the CREATE INDEX statement huge on black. Dominant color: green.
## 5. Caption and tags
The fastest SQL fix is usually one index, not a rewrite.
What is the slowest query you have ever had to fix?
#sql #dataengineering #programming #postgresql #databasetips #sqlperformance #explainplan #queryoptimization
## 6. Retention check
- 2-6s: the "why" line can feel like a lecture. Fix: cut to 9 words and show 10M rows moving.
- 11-16s: jargon drop-off for beginners. Fix: "checks every single row" plus a visual sweep explains Seq Scan without a definition.
- 21-26s: viewers who got the idea leave. Fix: the payoff number is held until 26s and the timer is on screen.
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-5-OPUS
Turn any topic into a ready-to-film YouTube Short, Reel or TikTok. You get 5 hooks in 5 proven patterns (best one picked for you), a second-by-second script table with on-screen text and B-roll, 5 titles, 3 thumbnail concepts, a caption with hashtags, and a retention check that shows where viewers swipe away and how it was fixed. Built for retention: a change every 3-5 seconds, payoff held to the end, loop ending. No fake stats. Works in Claude and ChatGPT.
...more
Added 4 weeks ago
