trending-content-scout
Scan social platforms for top-performing content by engagement before you create anything. Use this skill when the user wants to see what content is winning in a niche, find viral content patterns, research what's working on YouTube/TikTok/X/Reddit, benchmark engagement, discover content gaps, or says "what content is working for [topic]", "show me top performing content about [keyword]", "what's trending in [niche]", "find viral content about [product]", "content research for [keyword]", "what gets views in [niche]", "engagement analysis for [topic]", "scout the competition", "what videos are getting the most views about [keyword]", "social listening for [topic]", "trending content in [niche]", "top content analysis", "what hooks work for [keyword]", "content intelligence", "find winning formats".
What this skill does
# Trending Content Scout
Scan YouTube, TikTok, X, and Reddit for top-performing content by real engagement data.
Find winning formats, hooks, and content gaps — **before** you create anything. Stop
guessing what works. See what's already winning, then build on proven patterns.
This skill is the **data foundation** for the entire content pipeline. Run it first,
then feed its output into `content-angle-ranker`, `viral-post-writer`, `tiktok-script-writer`,
or any S2/S3 content skill.
## Stage
This skill belongs to Stage S1: Research
## When to Use
- Before creating any content for a keyword or niche
- When entering a new niche and need to understand what content works
- When comparing engagement across platforms for a topic
- When looking for content gaps competitors haven't filled
- When benchmarking your existing content against what's performing
- As the first step in any content creation workflow (before S2 skills)
## Input Schema
```yaml
keyword: string # (required) Search keyword — "AI video tools", "email marketing tips"
platforms: string[] # (optional, default: ["youtube", "tiktok"])
# Options: "youtube" | "tiktok" | "x" | "reddit"
sort_by: string # (optional, default: "engagement_score")
# Options: "views" | "likes" | "engagement_score" | "recency"
time_range: string # (optional, default: "30d") "7d" | "30d" | "90d" | "all"
limit: number # (optional, default: 20) Max content pieces to analyze
product: object # (optional) Specific product to focus on
name: string # "HeyGen"
url: string # "https://heygen.com"
```
No `api_config` needed in input — skills auto-detect configuration from conversation
context, project settings, or CLAUDE.md. See `shared/references/social-data-providers.md`
for setup instructions.
## Workflow
### Step 1: Determine Data Source
Check if the user has API configuration available:
```
IF social_data_config exists in context/settings for a platform:
→ Use configured API for that platform
→ Structured data: exact views, likes, comments, shares
ELSE (default — no API):
→ Use web_search + web_fetch
→ Still effective — see fallback methods below
```
**API mode** (when configured):
For each platform in `platforms`:
- YouTube: Search API → get video list → Details API → get statistics (views, likes, comments)
- TikTok: Search API → get video list with stats (playCount, diggCount, commentCount, shareCount)
- X: Search API → get tweets with public_metrics (impressions, likes, retweets, replies)
- Reddit: Search API → get posts with score and comment count
See `shared/references/social-data-providers.md` for specific API endpoints and config.
**web_search fallback** (no API — default):
```
For YouTube:
web_search "[keyword] site:youtube.com" → top 10-15 video results
For each result: extract title, channel, view count from search snippet
Optional: web_fetch individual video pages for likes/comments (slower)
For TikTok:
web_search "[keyword] tiktok" → find popular TikTok content
web_search "[keyword] site:tiktok.com" → direct TikTok results
Extract: titles, creators, approximate view counts from snippets
For X:
web_search "[keyword] site:x.com" OR "[keyword] site:twitter.com" → top tweets
Extract: tweet text, author, engagement signals from snippets
For Reddit:
web_search "[keyword] site:reddit.com" → top Reddit discussions
web_fetch top results → extract upvotes, comments from page
web_search "reddit [keyword] top upvoted" → find popular threads
```
Note which data source was used — include in output for transparency.
### Step 2: Collect and Normalize Data
For each content piece found, extract and normalize into a standard schema:
```yaml
ContentItem:
title: string # Video title, tweet text (first line), post title
url: string # Direct link to content
platform: string # "youtube" | "tiktok" | "x" | "reddit"
creator: string # Channel name, @handle, username
views: number # View/impression count (0 if unavailable)
likes: number # Like/upvote count (0 if unavailable)
comments: number # Comment/reply count (0 if unavailable)
shares: number # Share/retweet count (0 if unavailable)
published_date: string # ISO date or relative ("3 days ago")
duration: string # Video duration ("2:34") — video only
engagement_score: number # Calculated — see formula below
content_format: string # Detected format (see classification below)
hook_type: string # Detected hook style (see classification below)
```
**Engagement Score Formula** (consistent across all Affitor skills):
```
engagement_score = (likes × 2 + comments × 3 + shares × 5) / max(views, 1) × 1000
```
Platform-specific adjustments:
- **Reddit:** `(score × 2 + num_comments × 3) / max(score, 1) × 1000` (no share count)
- **X:** Use retweets as shares, replies as comments
- **YouTube:** Estimate shares as `comments × 0.5` (not available via most APIs)
- **web_search fallback:** If only views are available, use `views` as the ranking signal and note that engagement_score is estimated
See `shared/references/social-data-providers.md` for full formula documentation.
**Content Format Classification:**
Detect format from title and description:
- **comparison:** Contains "vs", "versus", "compared to", "X or Y", "better than"
- **review:** Contains "review", "honest review", "worth it", "my experience"
- **tutorial:** Contains "how to", "step by step", "guide", "tutorial", "walkthrough"
- **listicle:** Contains "top X", "best X", "X tools", "X ways", numbers in title
- **reaction:** Contains "I tried", "testing", "first time using", "is it worth"
- **story:** Contains "how I", "my journey", "I made $X", personal narrative
- **demo:** Contains "demo", "showing", "watch me use", "in action"
- **explainer:** Contains "what is", "explained", "why you need", "everything about"
**Hook Type Classification:**
Detect from first sentence/title:
- **question:** Starts with or contains a question
- **shock:** Contains surprising numbers, "you won't believe", extreme claims
- **bold_claim:** "This replaced X", "The only tool you need", definitive statements
- **demo_first:** Starts with showing a result or end product
- **relatable:** "POV:", "When you...", shared experience pattern
- **contrarian:** "Stop using X", "X is overrated", against conventional wisdom
### Step 3: Sort and Rank
Sort all collected content by the chosen `sort_by` parameter:
- **engagement_score** (default): Best for finding content that resonates regardless of creator size
- **views**: Best for finding content with broadest reach
- **likes**: Best for finding content people actively endorse
- **recency**: Best for finding what's working RIGHT NOW
Take top `limit` results after sorting.
### Step 4: Analyze Patterns
From the top content, extract actionable patterns:
**Format Analysis:**
```
For each content_format in top results:
count: how many of top 20 use this format
avg_engagement: average engagement_score for this format
best_example: highest engagement content in this format
```
**Hook Analysis:**
```
For each hook_type in top results:
count: how many use this hook
avg_engagement: average engagement_score
best_example: highest engagement content with this hook
```
**Duration Analysis (video platforms only):**
```
Group videos by duration buckets:
<30s, 30-60s, 60-120s, 2-5min, 5-10min, 10-20min, 20min+
For each bucket: count and average engagement
→ Identify optimal duration range
```
**Creator Analysis:**
```
For each unique creator in top results:
content_count: how many pieces in top results
avg_engagement: average engagement score
platforms: which platforms they're on
dominant_formatRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".