Skip to content

PostPlusAI/hook-skills

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

4 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Hook Skills

5 open-source skills for stronger short-form video hooks.

Hook Skills is a focused skill pack for designing, decoding, routing, and QA-ing short-form video hooks.

It is built for TikTok, Reels, Shorts, UGC ads, AI video workflows, and any creative system where the first 1-3 seconds decide whether the viewer keeps watching.

This repo packages the hook layer only:

  • choose the right opening route
  • turn vague ideas into a stable hook brief
  • decode benchmark references into reusable opening logic
  • design stronger visual openings
  • QA prompts before spending generation credits

Why This Exists

Most short-form videos do not fail because the body is bad.

They fail because the opening does not create a concrete viewer question before the content feels like an ad.

We built these skills to make hook work less fuzzy and more operational:

  • mechanism before wording
  • product reveal timing before product hype
  • visible conflict before visual polish
  • reusable diagnosis before random inspiration

What Is Inside

Routing

  • pattern-router
    Choose the right opening route before prompt writing starts.

  • hook-design
    Turn a rough idea into a reusable Hook Brief.

  • reference-decode
    Distill benchmark clips and frames into reusable opening structure.

Creative

  • visual-hook
    Strengthen frame one, first slide, or first 1-3 seconds.

QA

  • prompt-preflight-qa
    Catch weak openings, early product reveal, and prompt drift before generation.

How We Distilled It

This repo is informed by analysis across 1,000+ short-form hooks, benchmark openings, and hook-adjacent prompt examples.

The working method:

  1. Collect winning and failed opening examples across short-form formats.
  2. Group them by stop-scroll job, not by niche or surface wording.
  3. Compare viewer question, product timing, visible proof, and self-recognition.
  4. Extract reusable opening mechanisms and failure patterns.
  5. Package those judgments into installable skills instead of a swipe file.

Read the full write-up in docs/methodology.md.

Quick Start

Tool Install
Claude Code /plugin marketplace add PostPlusAI/hook-skills
OpenClaw clawhub install PostPlusAI/hook-skills or bundle
Gemini CLI gemini extensions install https://github.com/PostPlusAI/hook-skills
Qwen Code qwen extensions install https://github.com/PostPlusAI/hook-skills
Amp amp skill add PostPlusAI/hook-skills
Kimi Code CLI kimi plugin install https://github.com/PostPlusAI/hook-skills.git
CodeBuddy /plugin marketplace add PostPlusAI/hook-skills then /plugin install postplus-hook-skills
Cursor / Codex / Windsurf / Cline / Copilot / 35+ agents npx skills add PostPlusAI/hook-skills

Install one skill:

npx skills add PostPlusAI/hook-skills -s hook-design

The repository includes the marketplace and extension manifests needed for these install surfaces.

Try These Requests

Turn this rough opening into a stronger hook brief
The product appears too early. Fix the hook logic first
Decode this benchmark into a reusable opening structure
Review this prompt before we spend credits on generation

Pipeline

                        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                        β”‚     Raw input         β”‚
                        β”‚  (brief / references  β”‚
                        β”‚   / prompt draft)     β”‚
                        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                   β”‚
                                   β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚      pattern-router       β”‚
                   β”‚                           β”‚
                   β”‚  Routes the opening job:  β”‚
                   β”‚  segment type, viewer     β”‚
                   β”‚  question, product rule   β”‚
                   β”‚                           β”‚
                   β”‚  Output: Route Summary    β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                              β–Ό
                   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                   β”‚       hook-design         β”‚
                   β”‚                           β”‚
                   β”‚  Locks mechanism +        β”‚
                   β”‚  product timing. Reads    β”‚
                   β”‚  hook-principles.md +     β”‚
                   β”‚  hook-examples.md for     β”‚
                   β”‚  reference.               β”‚
                   β”‚                           β”‚
                   β”‚  Output: Hook Brief       β”‚
                   β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β”‚                                β”‚
              β–Ό                                β–Ό
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”       β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
 β”‚   reference-decode   β”‚       β”‚     visual-hook      β”‚
 β”‚                      β”‚       β”‚                      β”‚
 β”‚  When benchmarks or  β”‚       β”‚  When frame-one or   β”‚
 β”‚  references exist:   β”‚       β”‚  first 3 s need      β”‚
 β”‚  extract essence,    β”‚       β”‚  visual strength:    β”‚
 β”‚  viewer question,    β”‚       β”‚  map hook mechanism  β”‚
 β”‚  grammar, drift      β”‚       β”‚  to visual family    β”‚
 β”‚  boundaries          β”‚       β”‚                      β”‚
 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜       β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
            β”‚                              β”‚
            β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                           β”‚
                           β–Ό
                  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                  β”‚   prompt-preflight-qa    β”‚
                  β”‚                          β”‚
                  β”‚  Pre-generation check:   β”‚
                  β”‚  opening strength,       β”‚
                  β”‚  product timing, drift   β”‚
                  β”‚  risk, missing fields    β”‚
                  β”‚                          β”‚
                  β”‚  Output: Verdict + Fixes β”‚
                  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                             β”‚
                             β–Ό
                  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                  β”‚  Ready for image /       β”‚
                  β”‚  video generation        β”‚
                  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Reference files (in routing/hook-design/):

hook-principles.md    6 mechanism definitions, product reveal rules,
                      common failure patterns

hook-examples.md      200+ example sentences organized by mechanism,
                      3 complete Hook Brief diagnosis examples,
                      appendices (FAQ, tips, niche references)

The goal is not to generate more hook ideas. The goal is to make the opening logic explicit enough that downstream prompt writing does not have to guess.

Repo Structure

hook-skills/
β”œβ”€β”€ routing/
β”‚   β”œβ”€β”€ pattern-router/
β”‚   β”œβ”€β”€ hook-design/
β”‚   └── reference-decode/
β”œβ”€β”€ creative/
β”‚   └── visual-hook/
β”œβ”€β”€ qa/
β”‚   └── prompt-preflight-qa/
β”œβ”€β”€ .claude-plugin/
β”œβ”€β”€ .codebuddy-plugin/
└── docs/
    └── methodology.md

Positioning

This is the open-source hook layer.

It is intentionally narrow, practical, and easy to install.

More production skills, research workflows, and creative systems: postplus.io

Contributing

See CONTRIBUTING.md.

Versioning

See VERSIONS.md.

About

more marketing skills, try postplus.io

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors