supabase
Handles the full Supabase workflow from schema changes to deployment, with built-in security guardrails that catch common traps like RLS...
cold-open-creator
Create 25-35 second cold opens that hook listeners by dropping them into a specific moment that encapsulates the episode's themes. Uses narrative snippets method (story arcs with beats) combined with Colin & Samir's rearrangement technique.
Full skill instructions
Create 25-35 second cold opens that drop listeners into a story arc - someone who wanted something, encountered obstacles, and figured something out. The cold open cuts at the tension peak, before the resolution.
Core Philosophy: The cold open is not a summary or a trailer. It's a story interrupted at the moment of maximum tension. They should finish the cold open asking "How did we get here?" and "What happens next?"
The best cold opens follow recognizable story beats. Instead of searching for "good moments," search for complete story arcs, then cut them at the right point.
Every compelling story follows this pattern:
| Beat | What Happens | Cold Open Role |
|---|---|---|
| 1. Setup | Protagonist in their world, pursuing something | INCLUDE - establishes context |
| 2. Disaster | Something disrupts the status quo | INCLUDE - creates tension |
| 3. Failed Approach | They try the obvious solution, it backfires | INCLUDE - shows stakes |
| 4. New Insight | A realization that changes everything | TEASE or CUT HERE |
| 5. Resolution | They apply the insight, it works | CUT BEFORE THIS |
| 6. Reflection | The universal takeaway | CUT BEFORE THIS |
The Rule: Include beats 1-3 (maybe hint at 4). Cut BEFORE beats 5-6. The cold open ends with the question unresolved.
Scan for these signal phrases:
Disaster signals:
Failed approach signals:
Insight signals (CUT HERE OR JUST BEFORE):
Full arc (as it might appear in transcript):
For cold open: Include beats 1-4. Hint at beat 5. CUT before beat 7.
Cold open version:
"The dinner went exceptionally well. I was convinced I had the job sown up."
[beat]
"I'm sorry Howard, I have bad news... It's too risky, too much change."
[beat]
"Most people, when turned down for a job, just go away."
[beat]
"But this was a turning point in my life. It had to happen. So I called him back the next day and said—"
[CUT]
The listener NEEDS to know what Schultz said. That's the hook.
Use this skill when you need to:
Use when the episode contains personal stories with clear arcs - someone who wanted something, faced obstacles, figured something out. Works best for:
Use when the episode is more philosophical/conversational without clear narrative arcs. Works best for:
Decision rule: Scan the transcript for story arcs first. If you find one with beats 1-4 clearly present, use Approach A. If the content is more abstract/conceptual, use Approach B.
You have ONLY TWO tools:
You CANNOT:
The Art: Like a documentary editor selecting and sequencing pre-shot footage to tell a different story than the chronological one that actually happened.
Find the exact right moment—something small that encapsulates the big themes. Something specific that also gestures toward the general.
Questions to ask:
Get them on the page in ACTION, not passively described.
In a podcast context, this means:
Make us understand what's at stake for the character or listener.
Examples of stakes:
Find moments of friction, surprise, or expectation-violation.
Look for:
End by gesturing toward what's to come without giving it away.
The tease should:
First pass: Scan the transcript for complete story arcs - someone who wanted something, encountered obstacles, figured something out.
Signal phrases for story arcs:
| Beat | Signal Phrases |
|---|---|
| Setup | "Back then I was..." / "I had been trying to..." / "For years I thought..." |
| Disaster | "Then everything fell apart..." / "I was diagnosed with..." / "The call came and they said no..." |
| Failed Approach | "I tried X but..." / "We did everything we were supposed to..." / "Most people just accept it..." |
| Insight | "Then I realized..." / "That's when it clicked..." / "So what we do instead is..." |
If you find a story arc with beats 1-4: Use the Narrative Snippets approach. Extract the arc, identify where to cut (after beat 3 or partway through beat 4).
If no clear story arcs: Fall back to Scene Selection approach below.
For episodes without clear narrative arcs, scan for standalone moments:
Inflection Points (moments of shift):
Vulnerability Moments (personal stakes):
Contradiction Moments (what we think vs. reality):
Surprising Insights (research or data):
Choose ONE scene that:
Now that you know your scene, find all the verbatim clips within and around it.
Pull clips that show:
Document each clip with:
Now rearrange these clips to tell a more dramatic story than the original sequence.
The Descript Arc Structure:
Key principle: You are NOT arranging chronologically. You are arranging for maximum emotional/intellectual impact.
Example false chronology:
The Stranger Test
The Itch Test
The Stakes Test
The Tease Test
The Emotion Test
Pass at least 4 out of 5 = good cold open.
Every cold open MUST end with an unresolved moment. This cliffhanger must be 100% verbatim from the transcript.
Types of cliffhangers:
Create a file: [Episode_Name]_Cold_Open.md
# Cold Open - [Episode Title]
## The Scene
[1-2 sentences describing which moment encapsulates the episode]
## Clips (In Order)
**Clip 1** | **[Speaker]** | [Timestamp] | ~[X] seconds
"[EXACT VERBATIM QUOTE]"
**Clip 2** | **[Speaker]** | [Timestamp] | ~[X] seconds
"[EXACT VERBATIM QUOTE]"
[Continue for all clips...]
## Structure
**Arc:** [Describe the narrative arc: Setup → Character → Conflict → Stakes → Tease]
**Spine:** [What's the core tension? Contradiction? Shift?]
**Total Length:** [X seconds]
## The Cliffhanger
**Type:** [Unfinished statement / Unfinished question / Shocking statement / Promise of revelation]
**Line:** "[EXACT VERBATIM QUOTE - must end cold open]"
## Why This Works
[2-3 sentences: What makes this scene powerful? What questions does it create? Why will someone keep listening?]
---
## Testing Results
- [ ] Stranger Test: PASS / FAIL
- [ ] Itch Test: PASS / FAIL
- [ ] Stakes Test: PASS / FAIL
- [ ] Tease Test: PASS / FAIL
- [ ] Emotion Test: PASS / FAIL
**Final Score: X/5**
Mistake: Picking a "important" moment that doesn't actually encapsulate the episode or create curiosity Fix: Ask "Would a stranger care about this?" Pick moments with built-in drama, conflict, or surprise
Mistake: Arranging clips in the order they appeared in the episode Fix: Deliberately rearrange to tell a different, more dramatic story. Start with the end result, jump to the problem, tease the solution
Mistake: Explaining who the guest is or why they're talking Fix: Drop listeners in the middle. Let them figure out the context through what's being said
Mistake: Including too many clips or clips that resolve the tension Fix: Cut ruthlessly. The cold open is not the full story—it's a teaser
Mistake: Ending with the answer or solution revealed Fix: End with a question, a shift, a surprise—something that makes listeners want more
Mistake: Cutting mid-word or creating unnatural pauses that make the audio feel edited Fix: Cut at natural sentence breaks or at places where the speaker naturally paused
youtube-clip-extractor — Identifies and extracts best moments for short-form clips (TikTok, Instagram Reels)youtube-title-creator — Creates titles that pair with cold opensA cold open is not:
A cold open IS:
If listeners finish your cold open thinking "I need to hear the rest of this episode to understand what's happening," you've succeeded.
Handles the full Supabase workflow from schema changes to deployment, with built-in security guardrails that catch common traps like RLS...
Comprehensive guides and best practices for Neon Serverless Postgres, covering setup, connection methods, authentication, and platform APIs.
Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.
A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.
Official skill for integrating Firebase AI Logic (Gemini API) into web applications. Covers setup, multimodal inference, structured output, and security.
Complete Better Auth server and client setup with database adapters, session management, plugins, and security configuration.
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Complete Cloudflare platform integration with decision trees for compute, storage, AI, networking, security, and infrastructure-as-code.
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
Send, read, and manage Gmail messages, drafts, labels, and account settings.
Comprehensive website auditing across 230+ rules in 21 categories including SEO, performance, security, and accessibility.
Shared authentication, CLI syntax, and output formatting patterns for gws Google Workspace commands.
Discover your celebrity doppelgänger with StarByFace!
GeoSpy: Pricing, Features, FAQs, and Alternatives for AI Teams
Detect AI-generated voices to protect against audio fraud.
Ensure Your Content's Originality with AI Plagiarism Checker
Upscale images by 400% without quality loss
Protect your social media from copyright disputes
Accurately Detect AI-Generated Content with TheChecker.AI
Chrome extension that detects and flags AI-generated content