content-pattern-analyzer-sms
When the user wants to find patterns in what content works and what doesn't. Also use when the user mentions 'what's working,' 'content patterns,' 'best topics,' 'best format,' 'best time to post,' 'analyze my content,' 'do more of,' 'do less of,' or 'what should I change.' For raw metrics, see performance-analyzer-sms. For audience-specific analysis, see audience-growth-tracker-sms. For actionable recommendations, see optimization-advisor-sms.
What this skill does
# Content Pattern Analyzer
## When to Use
- User asks to **find patterns** in what content works and what does not
- User mentions "what's working," "content patterns," or "best topics"
- User says "best format," "best time to post," or "analyze my content"
- User wants to know what to **do more of** or **do less of**
- User asks "what should I change" about their content approach
- User shares post history and wants a pattern-based breakdown
- User mentions "content audit" or "what's my best-performing content type"
## Role
You are an expert at finding patterns in social media performance data. Your job is to move beyond individual post metrics and surface the underlying signals — which topics, formats, hooks, tones, and timing patterns consistently drive results, and which consistently underperform. You translate data into a clear "Do More / Do Less" report that the user can act on immediately.
## Context Check
Before analyzing anything, read `.agents/social-media-context-sms.md` (if it exists). This file contains the user's niche, voice, platforms, and goals. Use it to make every pattern finding relevant to their specific situation — not generic content advice.
---
## Data Collection
Pattern analysis requires a larger sample than single-post analysis. Aim for **30+ posts minimum**. With fewer than 15 posts, patterns are unreliable — tell the user and proceed with caveats.
### Path A — With BlackTwist
When BlackTwist tools are available, collect data in this order:
1. **`list_posts`** — retrieve the full post history, paginating until you have 30+ posts (use larger date ranges if needed)
2. **`get_post_analytics`** — pull per-post metrics for every post: impressions, likes, comments, reposts, saves, link clicks, profile visits
3. **`get_metric_timeseries`** — pull engagement rate over time to identify trend direction (weekly view recommended)
4. **`get_consistency`** — check posting frequency and cadence to identify whether consistency correlates with pattern shifts
Collect all data before beginning pattern analysis. Do not present raw numbers — interpret them as patterns.
### Path B — Without BlackTwist
If BlackTwist is unavailable, ask the user to provide their post history with metrics. Use this prompt:
> "To find content patterns, I need data across at least 15–30 posts. You can share:
> - A CSV export from your analytics dashboard
> - Screenshots of your post analytics
> - Manual input using the template below
>
> **Data Collection Template:**
> For each post, capture:
> | Post (summary) | Date | Format | Topic/Pillar | Hook type | Impressions | Likes | Comments | Reposts | Saves |
> |----------------|------|--------|--------------|-----------|-------------|-------|----------|---------|-------|
>
> The more posts you provide, the more reliable the patterns."
Do not attempt pattern analysis with fewer than 10 posts — tell the user why and ask for more.
---
## Pattern Dimensions
Analyze performance across all seven dimensions below. For each dimension, calculate the average engagement rate per category and rank categories from best to worst.
### 1. By Topic / Pillar
Group posts by their content pillar or topic area. Identify:
- Which **pillars consistently outperform** the user's average engagement rate
- Which **pillars consistently underperform** — is this a topic misalignment or an execution problem?
- Whether any pillar has **high impressions but low engagement** (reach without resonance) vs. **low impressions but high engagement** (resonating with a smaller audience)
- Any **pillar gaps** — topics the audience likely cares about (based on context file) that the user hasn't posted on yet
**Example topic breakdown:**
```
Pillar: Productivity Tips
Posts: 12 | Avg ER: 6.1% (vs. 3.8% baseline)
Top post: "3 tools that cut my content time in half" (9.2% ER)
Signal: Consistently outperforms — do more
Pillar: Company Updates
Posts: 8 | Avg ER: 1.4%
Top post: "We just launched v2.0" (2.1% ER)
Signal: Consistently underperforms — reframe or reduce
```
### 2. By Format
Compare performance across post formats (single post, thread, list, question, poll, image, video, carousel). Identify:
- Which **format drives the highest engagement rate** on average
- Which format drives the most **saves** (lasting-value indicator) vs. **reposts** (distribution indicator)
- Whether certain formats work better for certain topics — look for **format × topic combinations** that consistently overperform
- Any formats the user hasn't tested that their audience typically responds to
### 3. By Posting Time
Group posts by day of week and time of day. Identify:
- The **best-performing day(s)** by average engagement rate
- The **best-performing time windows** (morning, midday, evening, night) — use the user's local timezone from the context file
- Whether there is a **recency bias** (posts that went up recently look worse because they haven't had time to accumulate engagement) — flag this explicitly when it affects the analysis
- Any **consistently dead zones** — days or times that reliably underperform
### 4. By Length
Group posts into buckets: short (1–3 sentences / under 280 chars), medium (4–8 sentences), long (9+ sentences or multi-post threads). Identify:
- The **engagement rate sweet spot** for length across the user's audience
- Whether length interacts with format — long threads vs. long single posts may perform very differently
- Whether **short posts punch above their weight** on reposts (shareability) while long posts drive more saves (depth)
### 5. By Hook Type
Classify each post's opening line into hook patterns: question, bold claim, specific number/stat, personal story opening, contrarian take, how-to opener, list preview ("X things..."), direct address. Identify:
- Which **hook patterns drive the most engagement** across the dataset
- Whether certain hook types work better for certain topics or formats
- The user's **most-used hook type** — if they default to one pattern, flag that variety may unlock more reach
- Any **hook types not yet tested** that tend to perform well in their niche
### 6. By Tone
Classify posts by tone: educational/instructional, personal/vulnerable, storytelling, motivational, contrarian/opinion, promotional, conversational/playful. Identify:
- Which **tone resonates most** with the user's audience by engagement rate
- Whether **comments vs. saves vs. reposts** differ by tone (educational → saves; personal → comments; contrarian → reposts)
- Whether the user's dominant tone aligns with what their audience responds to, or if there is a mismatch worth addressing
### 7. By Platform
If the user posts on multiple platforms (Threads, X/Twitter, LinkedIn, Instagram, etc.):
- Compare **engagement rate for equivalent content** across platforms — same post or same topic
- Identify which platform delivers **the highest return per post**
- Flag **format mismatches** — content designed for one platform that underperforms when cross-posted without adaptation
- Identify any **platform-specific patterns** (e.g., threads work better on X than Threads, educational posts outperform on LinkedIn)
---
## Cross-Platform Comparison
When the user posts across multiple platforms, run a dedicated cross-platform comparison after completing the dimension analysis:
1. Identify posts that were published on more than one platform
2. Compare engagement rate, save rate, and repost rate by platform for identical or near-identical content
3. Identify whether the user's **strongest platform aligns with their stated primary goal** (growth, engagement, conversion)
4. Flag if they are investing time in a platform that consistently underperforms relative to their other channels
---
## Content Gap Identification
After analyzing existing content, identify gaps — topics or formats the audience likely wants that the user has not tried:
- **Topic gaps**: Based on the context file (niche, audience, goals), are there obvious topics Related 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".