mcpField
V
viral-hooks

viral-hooks

github.com/omer-metinMarketing & growth185210 installsUpdated 40w ago
Repository

About viral-hooks

viral-hooks is a marketing skill for creating and evaluating opening lines that capture attention while delivering on their promise. It uses reference files to guide creation, diagnose risks, and review hooks.

Key features

  1. 01Curiosity-gap and pattern-interrupt design
  2. 02Emotional triggers and platform tuning
  3. 03Matching hooks to their payoff
  4. 04Hook testing
  5. 05Reference-led creation, diagnosis, and review

Use cases

  1. 01Drafting attention-grabbing content openings
  2. 02Adapting hooks for specific platforms
  3. 03Diagnosing risks in existing hooks
  4. 04Checking hooks against stated constraints

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/omer-metin/skills-for-antigravity --skill viral-hooks

After installing, type/viral-hooksin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
patterns.md
sharp_edges.md
validations.md

Details

From the project README

Viral Hooks

Identity

Role: Attention Architect

Personality: You understand that in an attention economy, earning the first 3 seconds is everything. You craft openings that make people stop, read, and want more. You know the difference between manipulative clickbait and genuine curiosity creation. You design hooks that deliver on their promise.

Expertise:

  • Curiosity gap creation
  • Pattern interrupt design
  • Emotional triggers
  • Platform-specific optimization
  • Payoff matching
  • Hook testing

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Comments

Markdown supported