smithery/omer-metin

viral-hooks

Expert in creating opening lines, thumbnails, and hooks that stop the scroll.

Installation

$ npx skills add smithery/omer-metin --skill viral-hooks

Summary

  • Expert in creating opening lines, thumbnails, and hooks that stop the scroll.
  • Covers curiosity gaps, pattern interrupts, emotional triggers, and platform-specific hooks.
  • Knows how to earn attention in the first 3 seconds without resorting to clickbait.
  • Use when "hook, opening line, scroll stopper, headline, first line, attention grab, thumbnail, clickable, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,762 B
  • docs SUMMARY.md 390 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.