content-pattern-analyzer-sms

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.

在开始任何分析前,请阅读
.agents/social-media-context-sms.md
(如果存在)。该文件包含用户的垂直领域、人设语气、发布平台和目标,你需要基于这些信息让所有模式发现都贴合用户的具体情况,而非给出通用的内容建议。

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.
模式分析需要比单帖分析更大的样本量,目标是最少收集30条以上帖子的数据。如果帖子数少于15条,得出的模式并不可靠——请告知用户并在后续分析中加上相关提示。

Path A — With BlackTwist

路径A — 有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.
当可以使用BlackTwist工具时,按以下顺序收集数据:
  1. list_posts
    — 获取完整的发布历史,分页拉取直到拿到30条以上帖子的数据(如果需要可以扩大日期范围)
  2. get_post_analytics
    — 拉取每条帖子的详细指标:曝光量、点赞数、评论数、转发数、收藏数、链接点击量、主页访问量
  3. get_metric_timeseries
    — 拉取 engagement rate 随时间变化的数据,识别趋势方向(推荐按周维度查看)
  4. get_consistency
    — 检查发布频率和节奏,判断发布稳定性是否和模式变化相关
在开始模式分析前先收集完所有数据,不要直接展示原始数字,要将其解读为模式。

Path B — Without BlackTwist

路径B — 无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)DateFormatTopic/PillarHook typeImpressionsLikesCommentsRepostsSaves
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.

如果无法使用BlackTwist,请要求用户提供带指标的发布历史,可使用以下提示语:
"为了挖掘内容模式,我需要至少15-30条帖子的跨期数据,你可以提供:
  • 分析后台导出的CSV文件
  • 帖子分析页面的截图
  • 按照下方模板手动录入的数据
数据收集模板: 每条帖子请填写以下信息:
帖子(摘要)日期格式主题/内容支柱钩子类型曝光量点赞数评论数转发数收藏数
你提供的帖子数越多,分析得出的模式可靠性越高。"
如果帖子数少于10条,不要尝试进行模式分析——告知用户原因并请求提供更多数据。

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.
从以下七个维度分析内容表现,每个维度计算对应分类的平均 engagement rate,按表现从好到坏排序。

1. By Topic / Pillar

1. 按主题/内容支柱

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
按内容支柱或主题领域对帖子分组,识别:
  • 哪些内容支柱的表现持续优于用户的平均 engagement rate
  • 哪些内容支柱的表现持续不佳——是主题匹配度问题还是内容执行问题?
  • 是否有支柱存在高曝光低 engagement(有触达无共鸣)或低曝光高engagement(在小众受众中认可度高)的情况
  • 是否存在内容支柱缺口——根据上下文文件判断受众可能关心、但用户还没有发布过的主题
主题拆解示例:
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

2. 按格式

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
对比不同帖子格式(单帖、线程、列表、提问、投票、图片、视频、 carousel)的表现,识别:
  • 平均来看哪种格式带来的engagement rate最高
  • 哪种格式带来最多收藏数(长期价值指标)和转发数(传播度指标)
  • 是否存在表现持续更好的格式×主题组合
  • 是否有用户还没测试过、但受众通常反馈好的格式

3. By Posting Time

3. 按发布时间

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
按周几和每天的时间段对帖子分组,识别:
  • 平均engagement rate最高的最佳发布日期
  • 表现最好的时间窗口(早、午、晚、夜间)——使用上下文文件中用户的当地时区
  • 是否存在新近偏差(刚发布不久的帖子还没足够时间积累engagement,所以看起来表现差)——如果这个因素影响分析要明确标注出来
  • 是否存在持续的低峰区间——表现一贯不好的日期或时间段

4. By Length

4. 按长度

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)
将帖子分成不同区间:短(1-3句话/少于280字符)、中(4-8句话)、长(9句话以上或多帖线程),识别:
  • 用户受众对内容长度的engagement rate最优区间
  • 长度是否和格式有交互影响——长线程和长单帖的表现可能差异很大
  • 是否短帖的转发表现超预期(易分享),而长帖能带来更多收藏(有深度)

5. By Hook Type

5. 按钩子类型

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
将每条帖子的开头归类为不同的钩子模式:提问、大胆断言、具体数字/数据、个人故事开头、反常识观点、教程开头、列表预告(「X件事…」)、直接对话,识别:
  • 全数据集中哪种钩子模式带来的engagement最高
  • 是否某些钩子类型对特定主题或格式效果更好
  • 用户最常用的钩子类型——如果用户默认只用一种模式,提示用户尝试更多类型可能会获得更多曝光
  • 是否有用户还没测试过、在其垂直领域通常表现好的钩子类型

6. By Tone

6. 按语气

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
将帖子按语气分类:教育/指导类、个人/真实类、讲故事类、励志类、反常识/观点类、推广类、对话/轻松类,识别:
  • 用户受众共鸣度最高的语气(按engagement rate判断)
  • 不同语气带来的评论/收藏/转发占比是否有差异(教育类→收藏多;个人类→评论多;反常识类→转发多)
  • 用户的主流语气是否和受众偏好匹配,是否存在值得调整的错配

7. By Platform

7. 按平台

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)

如果用户在多个平台发布内容(Threads、X/Twitter、LinkedIn、Instagram等):
  • 对比相同内容在不同平台的engagement rate——同一条帖子或同一个主题的内容
  • 识别哪个平台的单帖投入回报率最高
  • 标注格式错配——为某个平台设计的内容不加调整直接跨平台发布导致表现不佳的情况
  • 识别任何平台特有的模式(比如线程在X上的表现比在Threads上好,教育类帖子在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

如果用户在多个平台发布内容,完成维度分析后需要做专门的跨平台对比:
  1. 找出在多个平台发布过的帖子
  2. 对比相同或几乎相同的内容在不同平台的engagement rate、收藏率、转发率
  3. 识别用户表现最好的平台是否和其明确的核心目标(增长、engagement、转化)匹配
  4. 标注用户是否在投入时间运营某个表现持续远差于其他渠道的平台

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 the user hasn't covered? Look for topics adjacent to their top-performing pillars.
  • Format gaps: Are there formats the user hasn't tested (e.g., they only post threads but their audience saves image posts)? Check what performs in their niche generally.
  • Untested combinations: High-performing pillar + high-performing format combinations the user hasn't tried (e.g., if "productivity tips" and "list format" each perform well but the user hasn't combined them)
  • Hook variety gaps: If the user defaults to one hook type, flag 2–3 alternatives worth testing
Frame gaps as experiments, not failures. The user hasn't tested them yet — they are opportunities.
Example content gap finding:
Gap: "Productivity tips" (top pillar) + "carousel" (top format) = untested
Rationale: Your productivity content averages 6.1% ER and your carousels
average 5.8% ER — but you have never published a productivity carousel.
Experiment: Write 2 productivity carousels over the next 2 weeks and
compare ER against your baseline.

分析完现有内容后,识别缺口——受众可能想要、但用户还没尝试过的主题或格式:
  • 主题缺口:基于上下文文件(垂直领域、受众、目标),有没有明显用户还没覆盖的主题?可以找和用户表现最好的内容支柱相邻的主题
  • 格式缺口:有没有用户还没测试过的格式(比如用户只发线程,但受众很喜欢收藏图片帖)?可以参考其垂直领域普遍表现好的格式
  • 未测试的组合:用户还没尝试过的高表现支柱+高表现格式组合(比如「效率技巧」和「列表格式」各自表现都很好,但用户还没把两者结合起来)
  • 钩子多样性缺口:如果用户默认只用一种钩子类型,推荐2-3种值得测试的替代类型
将缺口表述为实验而非失败,用户只是还没测试过,这些都是机会。
内容缺口发现示例:
Gap: "Productivity tips" (top pillar) + "carousel" (top format) = untested
Rationale: Your productivity content averages 6.1% ER and your carousels
average 5.8% ER — but you have never published a productivity carousel.
Experiment: Write 2 productivity carousels over the next 2 weeks and
compare ER against your baseline.

Output: Do More / Do Less Report

输出:多做/少做报告

Deliver findings in this structure. Do not bury patterns in data tables.
undefined
按以下结构呈现结论,不要把模式藏在数据表格里。
undefined

Content Pattern Analysis — [Date Range]

Content Pattern Analysis — [Date Range]

Posts analyzed: [N] Your baseline engagement rate: [X%] Analysis confidence: [High / Medium / Low — based on sample size]

Posts analyzed: [N] Your baseline engagement rate: [X%] Analysis confidence: [High / Medium / Low — based on sample size]

Do More

Do More

[Top 3–5 patterns with specific evidence]
Pattern: [Name the pattern clearly — e.g., "Tuesday morning threads on productivity"] Evidence: [Avg ER, number of posts, specific examples] Why it works: [Your interpretation — be specific, not generic]

[Top 3–5 patterns with specific evidence]
Pattern: [Name the pattern clearly — e.g., "Tuesday morning threads on productivity"] Evidence: [Avg ER, number of posts, specific examples] Why it works: [Your interpretation — be specific, not generic]

Do Less

Do Less

[Bottom 3–5 patterns with specific evidence]
Pattern: [Name the pattern — e.g., "Friday promotional posts"] Evidence: [Avg ER, number of posts] Why it underperforms: [Diagnosis — be direct but constructive]

[Bottom 3–5 patterns with specific evidence]
Pattern: [Name the pattern — e.g., "Friday promotional posts"] Evidence: [Avg ER, number of posts] Why it underperforms: [Diagnosis — be direct but constructive]

Experiment With

Experiment With

[2–4 untested combinations or gaps worth trying]
Experiment: [Specific combination to test] Rationale: [Why this is likely to work, based on existing patterns] How to test: [Specific suggestion — e.g., "Write 3 posts using X hook on Y topic and compare ER after 7 days"]

[2–4 untested combinations or gaps worth trying]
Experiment: [Specific combination to test] Rationale: [Why this is likely to work, based on existing patterns] How to test: [Specific suggestion — e.g., "Write 3 posts using X hook on Y topic and compare ER after 7 days"]

Key Takeaway

Key Takeaway

[1–2 sentence summary of the single most important pattern shift the user should make]

Use **bold for key terms**. Write in active voice. Keep each pattern description under 4 sentences — specificity beats length.

---
[1–2 sentence summary of the single most important pattern shift the user should make]

关键术语用**加粗**标注,使用主动语态,每个模式的描述控制在4句话以内——精准比冗长更重要。

---

Boundaries

边界说明

  • Does not provide per-post metric breakdowns — see performance-analyzer-sms for individual post analysis
  • Does not track follower growth or audience demographics — see audience-growth-tracker-sms for growth data
  • Does not generate a prioritized action plan — see optimization-advisor-sms for concrete next steps
  • Does not write or draft new content — see post-writer-sms, thread-writer-sms, or carousel-writer-sms for creation
  • Does not execute code or access external APIs unless BlackTwist MCP is connected
  • Does not work reliably with fewer than 10 posts — the skill requires a minimum sample size for pattern detection
  • 不提供单帖指标拆解——单帖分析请参考 performance-analyzer-sms
  • 不追踪粉丝增长或受众人口统计数据——增长相关数据请参考 audience-growth-tracker-sms
  • 不生成优先级排序的行动计划——具体下一步请参考 optimization-advisor-sms
  • 不撰写或生成新内容——内容创作请参考 post-writer-smsthread-writer-smscarousel-writer-sms
  • 除非连接了BlackTwist MCP,否则不执行代码或访问外部API
  • 帖子数少于10条时分析结果不可靠——该功能需要最低样本量才能检测模式

Related Skills

相关技能

  • social-media-context-sms — establish niche, voice, and goals before pattern analysis
  • performance-analyzer-sms — get raw post metrics and individual post diagnoses
  • optimization-advisor-sms — translate pattern findings into a concrete improvement plan
  • social-media-context-sms — 在模式分析前确定垂直领域、人设语气和目标
  • performance-analyzer-sms — 获取原始帖子指标和单帖诊断
  • optimization-advisor-sms — 将模式发现转化为具体的改进计划