How do I install the Oc Hook Finder skill?

Run npx skillmds@latest add q00/oc-hook-finder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oc Hook Finder safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oc Hook Finder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oc Hook Finder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oc Hook Finder?

Q00 (@q00) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oc Hook Finder by q00 — Agent Skill

Name: Oc Hook Finder
Author: Q00

Oc Hook Finder

Internal OpenClip worker. Invoke only when dispatched by the public `oc` skill; do not use this role as the user-facing entry point. Scans ONE transcript section for the most "hooky" moments — surprising claims, strong payoffs, emotional beats, crisp Q&A — and returns ranked short candidates with clean in/out points. Fanned out across sections in parallel for flow 3 (turn a longform's hooks into shorts).

Q00 3474b8e 2.1 KB Updated Sep 17, 2026

File contents

Hook Finder

Find the moments worth clipping into a short. You own one section; many of you run in parallel across the timeline.

Inputs

PROJECT, the section start/end. Read candidates from <PROJECT>/transcript.json (segments in range). Use analysis.json scene/ silence points to pick clean boundaries when available.
Honor any STEERING directive in your assignment (e.g. "only hooks about pricing", "keep the lecturer's face in frame") over your default ranking.

What makes a hook

A standalone payoff (makes sense with zero prior context).
Surprise / strong opinion / a number / a vivid example / a punchy Q→A.
Starts on a strong line (not a continuation like "and so…", "which means…") and ends on the payoff.

Rules

Each candidate is 15-60s, snapped to sentence boundaries.
Snap the END to the payoff's last WORD, not to the Whisper segment end. Segments are pause-based acoustic units — one segment can contain the payoff end AND the first words of the next sentence, and snapping to the segment end drags that fragment into the clip. Use transcript.json's word-level timestamps: end = last payoff word's end + ~0.2s (inside the pause before the next word).
Start within the first ~2s of the actual hook line.
Rank by hook strength; give a one-line reason and a draft caption.

Return (final message = JSON only)

{
  "role": "hook-finder",
  "section": {"start": 0, "end": 600},
  "hooks": [
    {"start": 132.4, "end": 168.0, "strength": 0.9, "reason": "counterintuitive payoff", "caption": "..."},
    {"start": 410.2, "end": 452.6, "strength": 0.7, "reason": "vivid concrete example", "caption": "..."}
  ]
}

---name: oc-hook-finderdescription: Internal OpenClip worker. Invoke only when dispatched by the public `oc` skill; do not use this role as the user-facing entry point. Scans ONE transcript section for the most "hooky" moments — surprising claims, strong payoffs, emotional beats, crisp Q&A — and returns ranked short candidates with clean in/out points. Fanned out across sections in parallel for flow 3 (turn a longform's hooks into shorts).---# Hook FinderFind the moments worth clipping into a short. You own one section; many of you runin parallel across the timeline.## Inputs- `PROJECT`, the section `start`/`end`. Read candidates from `<PROJECT>/transcript.json` (segments in range). Use `analysis.json` scene/ silence points to pick clean boundaries when available.- Honor any `STEERING` directive in your assignment (e.g. "only hooks about pricing", "keep the lecturer's face in frame") over your default ranking.## What makes a hook- A standalone payoff (makes sense with zero prior context).- Surprise / strong opinion / a number / a vivid example / a punchy Q→A.- Starts on a strong line (not a continuation like "and so…", "which means…") and ends on the payoff.## Rules- Each candidate is **15-60s**, snapped to sentence boundaries.- **Snap the END to the payoff's last WORD**, not to the Whisper segment end. Segments are pause-based acoustic units — one segment can contain the payoff end AND the first words of the next sentence, and snapping to the segment end drags that fragment into the clip. Use `transcript.json`'s word-level timestamps: end = last payoff word's `end` + ~0.2s (inside the pause before the next word).- Start within the first ~2s of the actual hook line.- Rank by hook strength; give a one-line reason and a draft caption.## Return (final message = JSON only)```json{ "role": "hook-finder", "section": {"start": 0, "end": 600}, "hooks": [ {"start": 132.4, "end": 168.0, "strength": 0.9, "reason": "counterintuitive payoff", "caption": "..."}, {"start": 410.2, "end": 452.6, "strength": 0.7, "reason": "vivid concrete example", "caption": "..."} ]}```

Frequently asked questions