--- name: kk-short-form description: Use this skill whenever drafting Instagram Reels or YouTube Shorts scripts for KK Mookhey (@settlingforless1). Trigger on phrases like "write a reel", "draft a short", "Instagram Reel script", "YouTube Shorts script", "turn this into a reel", "hook for a reel", "repurpose this as a short", or any vertical short-form video content for KK's Instagram or YouTube Shorts channels. Use this instead of generic content skills whenever the destination is Reels or Shorts, because short-form video has its own structural requirements (hook, suspense, payoff, loop) that longer-form content doesn't demand. --- # KK on Short-Form Video — Instagram Reels & YouTube Shorts This skill captures what works for KK on vertical short-form video. It fuses three sources: (1) 2026 best practices for Reels/Shorts retention and distribution; (2) KK's actual Instagram analytics showing what has and hasn't worked on @settlingforless1; (3) KK's voice, as defined in the `kk-voice` skill. **The prerequisite:** This skill assumes the `kk-voice` skill is also loaded. Voice markers, tone, and anti-patterns from that skill apply here too. This skill adds *structural* rules specific to short-form video on top of KK's voice. ## The one rule that matters most **Short-form video is a forwarding medium, not a broadcasting medium.** The question every script must answer is not "is this interesting?" but "**would the viewer send this to someone they love in the next 10 seconds?**" KK's top-performing reel (iOS security update, 101K views, 7,246 shares, 2.6% from followers) won because viewers forwarded it to their parents, spouse, kids. His bottom-performing reels (political reactions, abstract AI framings) failed because there was nothing to forward. Shares are the single highest-ROI metric on Instagram — they're the algorithm's strongest signal and they're how KK reaches the 88–97% non-follower audience that defines his current distribution. If a script doesn't give the viewer a clear reason to forward it, it doesn't ship. ## KK's Audience on Reels/Shorts KK is writing for two sequential people. Every script must clearly serve at least one of them, and ideally both. ### Meera (the stopper — 60% of content) - 34, non-technical. Marketing, HR, product, teacher, finance, ops — not in cybersecurity. - Owns an iPhone. Lives on WhatsApp. Has aging parents who click on things they shouldn't. Has kids on apps she doesn't understand. - Reuses passwords, knows she shouldn't, doesn't do anything about it. - Her cybersecurity mental model is built from news headlines and one scary thing that happened to someone she knows. - **She's not following KK. She's seeing his reel because someone forwarded it, or the algorithm pushed it to her.** **What makes Meera stop scrolling:** - A specific device she owns + a specific bad thing + a specific action she can take. In 3 seconds. - Named, concrete threats she can recognize in her life. Not "phishing" — "the fake FedEx text." - Content that makes her feel like she just got a privileged warning. **What Meera does after a good reel:** forwards it to her family WhatsApp group, saves it, scrolls KK's profile for more. This is the behavior that drives KK's distribution. ### Rohan (the convert — 30% of content) - 27, tech-adjacent. SOC analyst, junior developer, product manager at a SaaS company, cybersecurity student. - Landed on KK's profile because of a Meera reel. Now evaluating whether KK is legit or generic. - Wants substance — real pentests, real tools, real founder/practitioner perspective. - Converts at ~11 follows per 1K views on the right content (KK's Python/AI hack reel is the benchmark). **What makes Rohan follow:** - Proof KK actually does the work — Whitney, Transilience threat intel, MCP security, pentest walkthroughs - Technical specificity that respects his intelligence - The founder-practitioner combination — rare, real, aspirational ### Story reels (nurture — 10% of content) For existing followers. Paul Coiningham/Mercor-style human-interest pieces. Don't reach as far but keep the audience warm and show KK has range beyond the safety-PSA voice. ## The Content Ratio Every 10 reels should roughly split: - **6 Meera reels** — distribution engine. Shareable security PSAs that non-technical people forward. - **3 Rohan reels** — conversion engine. Technical depth content that turns Meera-driven visitors into followers. - **1 story reel** — audience nurture. Human-interest, founder reflection, industry observation. If the last 10 reels don't match this ratio, rebalance the next batch. **Cut entirely:** - Political/war reaction content (unless there's a direct, concrete cyber dimension) - "The biggest news in AI" / "The internet is going crazy" framings - Abstract cybersecurity concepts with no named, concrete hook - Anything that primarily serves existing followers — the algorithm won't distribute it ## The Four-Part Structure Every KK short-form script follows the same four-part architecture. This is non-negotiable — the research is unambiguous that structure matters more than topic on this medium. ### 1. HOOK — 0 to 3 seconds This is 80% of whether the reel works. Strong hook, everything else gets a chance. Weak hook, nothing else matters. **The hook must do three things simultaneously:** 1. Name a specific audience ("If you have an iPhone…", "If your parents use WhatsApp…") 2. Signal specific stakes (what goes wrong, how bad) 3. Open a loop the viewer needs to close (what exactly to do, or what exactly happened) **KK's working hook template (from his 101K iOS reel):** > "If you are an iPhone or iPad user, this information is extremely important." Name the audience. Signal stakes. Promise information. Three seconds. **Hook formulas that work for KK:** - **The named-device warning:** "If you own an [device], stop what you're doing." - **The family-protection open:** "Your [parents / mom / kids] are about to get hit with this." - **The specific-threat callout:** "This exact message just cost someone ₹12 lakh." - **The authority-reveal:** "I've been in cybersecurity 23 years. This is the scariest [thing] I've seen this year." - **The mistake-inversion:** "Most people think [X] is safe. It's not. Here's what just happened." - **The demo-first:** Show the attack happening on screen in the first frame. Talk second. - **The contradiction hook:** "Your IT team told you to do X. That's exactly wrong." **Hook formulas to AVOID (KK's data shows these fail):** - "The biggest news in…" — too generic, forfeits the 3-second window - "Bombshell news…" — clickbait-flavored, doesn't name stakes - "The internet is going crazy about…" — delegates the hook to someone else - "Let me tell you about…" — slow build, dead on arrival - "Guys, you won't believe…" — the "guys" problem, plus zero specificity **Pattern interrupt requirement:** Within the first 1.5 seconds, something on screen must interrupt the scroll pattern. Options include: - Bold text overlay that names the stakes ("YOUR iPHONE IS AT RISK") - A close-up of the thing being discussed (the fake SMS, the iOS version number) - KK's face mid-reaction, not mid-greeting - A visual of the attack in progress **The greeting ban:** KK never opens a reel with "Hi," "Hey guys," "Welcome back," "In today's video," or any variation. He opens with the stakes. ### 2. SETUP — 3 to 10 seconds Once the hook lands, the next 7 seconds establish what exactly the viewer needs to know. This is the "why should I care and what is this about" section. **What setup does:** - Names the specific threat/tool/situation - Gives the viewer just enough context to understand the payoff - Seeds the payoff without giving it away **Setup rules:** - Max 2 sentences of context. Anything more is preamble. - Specific nouns only. Names the CVE, the app, the attack, the version number. - Keep the loop open — don't resolve it yet. **Good setup example (for a scam-alert reel):** > "A fake FedEx SMS is going around. It says your package is held at customs and asks for ₹50. Click the link and your entire banking app is compromised within 30 seconds." Bad setup: "Phishing attacks are on the rise and users should be cautious about suspicious messages." (Too abstract. No one forwards this.) ### 3. PAYOFF — 10 to 45 seconds The content the hook promised. This is where KK actually delivers value. **Payoff rules by reel type:** **Meera reels (PSA format):** - Show the exact thing to do in concrete steps - Name the setting, the button, the version number, the exact text of the scam - Keep steps numbered on screen (1, 2, 3) so viewers can follow visually - End with "if you already clicked it, here's what to do next" — this adds a second layer of utility **Rohan reels (technical format):** - Show the actual tool, code, or finding on screen - Narrate what you're doing, not why it matters (he already knows why it matters) - Reveal something specific — a technique, a bug, a result - Receipts over claims **Payoff pacing requirement:** Every 8–10 seconds of payoff needs a *re-hook* — a small jolt that resets attention. Research shows viewers disengage every 60–90 seconds in long-form, but in short-form the window is tighter. Options: - A visual cut (new shot, new angle, new overlay) - A stat-slam ("That's ₹40,000 crore lost last year alone") - A reaction beat (KK's face, a pause) - A rhetorical question ("Guess what happened next?") - A text-overlay reveal **The text overlay requirement:** Every 3–5 seconds, a text overlay changes on screen. Instagram shows ~90% of Reels on mute first. If the reel doesn't make sense without audio, it dies in the 3-second window. Key claims, numbers, and actions must be on screen as text. ### 4. PAYOFF CLOSE + LOOP — final 5 to 10 seconds The close has two jobs: (1) deliver the final punch the hook promised, (2) either loop back to the opening or give the viewer a reason to send it. **The loop option (best for algorithmic performance):** End the reel in a way that makes the first 2 seconds feel earned when the video auto-replays. Example: the final line restates the hook with new meaning after the payoff. This drives re-watches, which the algorithm reads as strong retention. **The forward option (best for shareability):** End with a line that gives the viewer a reason to send it. Not "share this with your friends" — too generic, reads as creator-desperation. Instead: - "Send this to the one person in your life who will click every link." - "Your mom needs to see this before Sunday." - "If you manage a dev team, the next 30 seconds matter." Name the recipient. Make the forward decision easy. **The CTA that actually works for KK:** KK doesn't do "like and follow" CTAs. They read as creator-begging and Jennifer/Meera/Rohan all find them off-putting. Instead: - Meera reels: end with the forward-prompt (named recipient) - Rohan reels: end with specificity that makes following obvious — "More teardowns like this every week" or nothing at all - Story reels: end with a reflective line in KK's voice ("It does not bode well for the future, I fear.") **What KK never does:** - "Smash the like button" - "Don't forget to subscribe" - "Let me know in the comments" - "Follow for more" These are banned phrases. They flag a reel as generic creator content and Jennifer would unfollow on sight. ## Length Targets - **Meera reels:** 20–35 seconds. Urgent-feeling. Enough to convey the action, not a second more. - **Rohan reels:** 35–60 seconds. Technical content needs room to show work. - **Story reels:** 30–45 seconds. Long enough to land the emotional beat, short enough to not drift. **The 25-second rule:** If a reel can deliver full value in 25 seconds, it should. The research is clear that shorter reels with complete payoffs outperform longer ones — they drive more re-watches, which is a major algorithmic signal. **Pacing — reels run fast.** A reel must feel quicker than natural narration. A read that sounds right as a talking-head is too slow for a reel; viewers expect snappy delivery, tight cuts, and no dead air between beats. When generating a reel (especially with TTS voiceover and timed B-roll), target roughly **1.2× the natural pace** — either prompt the voice to deliver faster or apply a 1.2× speed pass to the finished cut (pitch-preserved). Trim inter-beat tails to the minimum that still lets a caption land. If a beat lingers, it drags; cut sooner. This applies to all reel types — slow pacing is one of the most common reasons a technically-good reel underperforms. ## Sound & Audio Rules - **Trending audio is optional, not required.** KK's top reel succeeded without trending audio because its shareability did the work. - **Voiceover must be clean.** Low-quality audio is a 3-second skip trigger. - **Silence is a weapon.** A 1-second pause before a big reveal resets viewer attention. Use it, especially before stat-slams and payoff lines. - **KK's voice carries authority.** Voiceover is usually the stronger choice over lip-sync. Save lip-sync for moments of direct-camera impact ("Listen to me. Do this right now."). - **Music under voiceover, not over it.** If a viewer can't hear the words clearly, the reel fails. ## Visual & Format Rules - **Vertical 9:16 only.** No exceptions. - **No TikTok watermarks, no CapCut logos.** Instagram's 2026 algorithm penalizes recycled content with a watermark. Always export clean from the source. - **Captions always on.** Burn-in captions (not Instagram's auto-captions) in a consistent font. Key claims in bold/color emphasis. - **Text overlay every 3–5 seconds.** See payoff section. - **First frame matters.** The thumbnail frame when someone stops scrolling needs to make sense on its own. KK's face mid-warning, a screen showing the threat, or a bold text claim. Never a cold open on KK smiling. - **B-roll is load-bearing.** A talking-head reel with no B-roll loses Rohan in 10 seconds. Screen recordings of the attack, the tool, the CVE page, the update screen — these are the difference between a reel that gets saved and one that gets skipped. ## The Jennifer Test for Reels (Cross-reference from `kk-voice` skill — Jennifer Chen is the LinkedIn ICP. She doesn't consume Reels professionally, but she may see them. Reels should never *embarrass* KK in front of Jennifer.) Jennifer test for reels: **would KK be comfortable if Jennifer scrolled to this on a flight?** If the reel reads as clickbait, panic-porn, or "influencer slop," it damages KK's LinkedIn positioning. Don't ship it. **Specifically, reels must not:** - Use false urgency ("WORLD IS ENDING") - Make technical claims that don't hold up ("hackers can access your phone through your fridge") - Overstate threats for virality - Feel like content-farm output The rule: Meera reels can be urgent and visceral, but they must be *true* and *specific*. A Meera reel that a CISO would fact-check and find wrong is worse than no reel at all. ## Pre-Publish Checklist Every reel must clear ALL of these before it ships: 1. **Hook in 3 seconds:** Does the first 3 seconds name the audience, stake, and promise? If it takes 4 seconds, rewrite. 2. **Shareability test:** Would Meera forward this to her mom? Or would Rohan save this to show his team? If neither, kill the reel. 3. **Specificity check:** Named device, named app, named attack, named version. No "many", "users", "people", "threats", "attacks" — swap every generic noun for a specific one. 4. **Mute test:** Play the reel on mute. Does it still communicate the core claim through text overlays? If not, add overlays. 5. **Loop or forward:** Does the final 5 seconds either loop back to the hook or give the viewer a specific reason to send it? 6. **No banned phrases:** No "hey guys," no "smash the like," no "the biggest news in," no "guys you won't believe," no "welcome back." 7. **Jennifer non-embarrassment:** Would KK be comfortable if a US Deputy CISO scrolled to this? If it reads as clickbait or overstated, rewrite. 8. **KK voice markers:** Does it sound like KK? Short sentences, direct tone, no corporate polish, no AI-slop language. Run through the `kk-voice` skill if uncertain. 9. **Text overlay cadence:** New text every 3–5 seconds. Key claim on screen when voiceover says it. 10. **Length fits type:** Meera reel under 35s, Rohan reel under 60s, story reel under 45s. If any of these fail, the reel doesn't ship until it's fixed. ## Scripting Template Use this template when writing any reel script: ``` TITLE: [descriptive working title] AUDIENCE: [Meera / Rohan / Story] LENGTH TARGET: [20-35s / 35-60s / 30-45s] [00:00–00:03] HOOK Voiceover: [one sentence, names audience + stakes] On-screen text: [bold overlay naming the stakes] Visual: [what's on screen — B-roll, face, screen recording] [00:03–00:10] SETUP Voiceover: [1-2 sentences of specific context] On-screen text: [specific noun — device, CVE, app name] Visual: [B-roll showing the thing] [00:10–00:XX] PAYOFF Voiceover: [the actual value — steps / technical reveal / story beat] On-screen text: [numbered steps / key stat / specific finding] Visual: [screen recording / demonstration / relevant B-roll] Re-hook every 8-10 seconds: [list the re-hooks — cut, stat, pause, question] [FINAL 5-10s] CLOSE Voiceover: [loop-back line OR forward-prompt with named recipient] On-screen text: [final punch] Visual: [return to opening visual if looping, or direct-camera if forwarding] CAPTION (for the post): [one punchy line in KK voice, optional rhetorical question, 3-5 hashtags max] HASHTAGS: Primary (always): #cybersecurity Situational: [pick 2-4 specific ones — #iphonetips #scamalert #aisecurity #infosec etc.] Avoid hashtag soup — 3-5 max. More doesn't help in 2026. ``` ## Examples of Hook-to-Payoff Transformations ### Example 1: Meera Reel (PSA format) **Source material:** A new Android banking trojan disguised as an APK file spreading via WhatsApp. **Bad version (generic, forgettable):** > "Hey guys, today I want to talk about a new Android banking trojan that's been spreading recently. This is a serious threat and you should be aware..." **KK version (specific, shareable):** > [00:00] VO: "If your parents use WhatsApp on an Android phone, show them this in the next 5 minutes." > TEXT: "WHATSAPP APK SCAM — ANDROID USERS" > VISUAL: Close-up of a WhatsApp message with an APK attachment. > > [00:03] VO: "This APK file is going around. Looks like a wedding invitation or a government form. Install it once, and your banking app is compromised in under a minute." > TEXT: "One tap → bank account drained" > VISUAL: Screen recording of the install prompt. > > [00:12] VO: "Here's what to check right now. Settings. Security. Install unknown apps. Turn it off. For every app." > TEXT: 3 numbered steps on screen. > VISUAL: Screen recording of the settings path. > > [00:25] VO: "If they already installed it, factory reset. Today. Not tomorrow." > TEXT: "ALREADY INSTALLED? FACTORY RESET NOW." > > [00:30] VO: "Send this to the one person in your family who clicks every link." > TEXT: "Forward this. Save a life savings." > VISUAL: Back to the opening WhatsApp frame — loops naturally. ### Example 2: Rohan Reel (Technical format) **Source material:** Testing three AI pentest tools against a vulnerable Apache Struts instance. **Bad version (abstract, no receipts):** > "AI-powered pentesting tools are changing the game. Today I tested a few of them and the results were interesting..." **KK version (specific, technical):** > [00:00] VO: "I ran the same exploit through Claude Code, HexStrike, and Strix. Only one of them got root." > TEXT: "3 AI PENTEST TOOLS vs APACHE STRUTS" > VISUAL: Split screen of three terminals. > > [00:04] VO: "Target: Apache Struts, the same stack that got Equifax. CVE-2017-5638. Known bug, documented exploit." > TEXT: "CVE-2017-5638 — Equifax bug" > VISUAL: Screen recording of the lab setup. > > [00:10] VO: "Claude Code: hesitated on the payload crafting. Needed three nudges." > TEXT: "Claude Code — 3 prompts to exploit" > VISUAL: Screen recording of the conversation. > > [00:20] VO: "HexStrike: found the vuln, failed the exploit. Gave up." > TEXT: "HexStrike — found, not exploited" > > [00:28] VO: "Strix: one command. Root shell. 90 seconds." > TEXT: "Strix — root in 90s" > VISUAL: The terminal showing root access. > > [00:38] VO: "This isn't an ad. It's a finding. If you're running legacy Struts anywhere in your environment, AI agents will get in before your SOC sees the first alert." > TEXT: "Full teardown in bio." > VISUAL: KK direct to camera. ### Example 3: Story Reel **Source material:** A reflection on the apprenticeship model dying in cybersecurity. **KK version:** > [00:00] VO: "In 2001, I hired my first employee. He didn't know anything. Neither did I." > TEXT: "2001." > VISUAL: An old photo or ambient office B-roll. > > [00:06] VO: "We learned on the job. We broke things. We fixed them. That's how the whole industry was built." > TEXT: [builds as the line goes] > > [00:14] VO: "Today, if you can't deliver on day one, you don't get hired. The apprenticeship model is dead." > TEXT: "The apprenticeship model is dead." > > [00:22] VO: "And I don't know how the next generation of defenders is supposed to learn. I really don't." > VISUAL: KK direct to camera, no movement. > > [00:28] VO: "It does not bode well for the future, I fear." > TEXT: none — the line lands on its own. Notice: no "follow for more," no CTA. The story lands and ends. This is how KK writes. ## Anti-Patterns (What NOT to Do) - **Creator-voice CTAs.** No "hit that follow button." Ever. - **"The algorithm" content.** Don't reference the algorithm in the script. Viewers don't care. - **Political reaction.** Skip unless there's a concrete cyber dimension (the Iran/Handala/Stryker reel worked because it was genuinely about a cyber campaign). - **Abstract AI framings.** "The biggest news in AI" — no. "Claude Mythos" — no. Name what the threat actually is. - **Recycled content with watermarks.** Originality Score penalty. Always re-export clean. - **Reading from a Dark Reading article.** If the reel is just KK narrating a news article, it fails. Always add a practitioner POV, a specific action, or a real finding. - **The warm-up.** No intros. No "today we're going to talk about." The first frame is the hook. - **Overstretching.** A 55-second Meera reel that could've been 25 seconds loses 60% of its audience in the middle. - **Hedging.** "It's possible that maybe under some circumstances…" — KK doesn't talk like this anywhere else. Don't start on Reels. ## Reference Material - `kk-voice` skill — full voice and tone guide. Load alongside this skill. - `/mnt/user-data/outputs/reddit_ama_qa.md` — KK's authentic voice patterns from AMA. - KK's top-performing reel for reference: "iOS security update" (101K views, 7,246 shares, Feb 2026 — the benchmark Meera reel). - KK's top follower-converter: "Python/AI hack" (46.5K views, 507 follows — the benchmark Rohan reel).