PrompTom
Усі скіли

Reverse-engineering competitors' viral videos

trendwatchPROtiktokgrowth

Breaks down other people's hits along seven axes and turns the analysis into hooks for your own product.

Що робить

  • Triggers on “what's working on TikTok right now”, “analyse this competitor”, “give me hooks for Reels”.
  • Researches first — app store, search, competitor profiles — and only then asks for what no tool can return: goals, KPIs, brand voice.
  • Each video is decomposed into seven parts: what stopped the scroll in the first 1.5 seconds, what the hook promised, the format, the message, the sound and how fresh it is, the CTA, and what the comments reveal.
  • Separates credit due to the format from credit due to the creator: 500k views on a 2M-follower account proves nothing, 50k on a 5k account proves a lot. Only the latter feeds ideation.
  • Accumulates a log of what was tried, what happened and what was learned — so over time it stops suggesting what already failed for you.

Навіщо він потрібен

Watching someone's viral video and copying it wholesale is the fastest way to waste a month: what gets copied is what's visible, and what works is what isn't. The skill takes a video apart and separates the three things people constantly conflate — the format, the creator's own audience, and paid amplification. And it remembers your past attempts, so it gets sharper with use.

Куди покласти

  1. 1Створіть у проєкті теку .claude/skills/trendwatch
  2. 2Покладіть у неї файл SKILL.md з текстом нижче
  3. 3Усе. Claude Code підключить скіл сам, коли задача підійде під опис

Щоб скіл працював в усіх проєктах, а не в одному, покладіть його в ~/.claude/skills замість теки проєкту.

Файл SKILL.md

# Trendwatch

A pipeline for organic TikTok/Instagram growth: discover what's working for competitors, decompose why it's working on 7 axes, generate adapted hook ideas for the user's product, and accumulate learnings over time so the skill gets sharper with use.

## Operating principles

1. **Auto-discover before asking — always.** Exhaust tools first: WebSearch (URLs, handles, news), WebFetch (App Store pages, landing pages, competitor profiles), Read/grep (codebase, analytics events, memory files). Ask the user ONLY for: *strategic decisions* (goals, KPIs, where to send traffic), *subjective preferences* (voice, what they value), *operational facts not in any system* (budget, who shoots content), or *validation* of hypotheses already drafted. Never ask for URLs, handles, copy, geo, or anything tools can return. The user's turn is for judgment, not lookup.

Файл скіла входить у PRO-добірку

Відкрити доступ
Reverse-engineering competitors' viral videos — PrompTom