playlet-wechat-feed

Short Drama - WeChat Official Account Information Source

📝 Overview

Short Drama - WeChat Official Account Information Source is a WeChat official account viral content tracking tool designed specifically for short drama creators and content operators. It automatically scans WeChat official account short drama content daily, filters popular works by read count, intelligently clusters topic directions, and then generates a visualized HTML daily report and creative trend analysis.

Through simple commands, you can:

🔥 Discover the day's viral WeChat official account short drama articles
📊 Get popular content intelligently clustered by topic
📈 Analyze viral title characteristics and creative trends
🔔 Enable daily subscription to automatically produce daily reports

Suitable for scenarios such as short drama screenwriters, content operators, MCN agencies, and WeChat official account owners who need to track hot topics in WeChat official account short dramas.

⚠️ Important reminder: Data is updated daily at 15:00 with the previous day's data (actual updates may be delayed; the script's real liveness check shall prevail). Before querying, the script first performs input validation: keywords must match the short drama topic keyword lexicon (topic_keywords as specified intopic name + all related words, e.g. "face-slapping" matches related words for the counterattack topic),after a match, use that keyword directly to query data; if not satisfied, remind "keyword does not meet query conditions" and recommend related words,do not initiate an API request; if the date exceeds the valid query range, remind and automatically fall back to the most recent date with data, without requiring user confirmation.No-data confirmation mechanism (v2.3): When a query has no matching data or the full dataset is insufficient,it is prohibited to automatically initiate any additional queries(automatic fallback to the full dataset is prohibited, and automatic topic expansion is prohibited). You must first show the user recommended topic keywords and wait for confirmation; only after confirmation may you re-query using the recommended words.

✨ Features

🎯 Core Features

Feature Module	Capability Description	Core Value
Viral Discovery	Filter popular content from WeChat official account short drama articles by read count	Precisely locate high-heat short drama works
Topic Clustering	Automatically identify topic directions (time travel/domineering CEO/rebirth/suspense, etc.)	Daily topic classification is dynamically determined by content
Smart Query	By default, query all short dramas; when data is insufficient, prompt recommended topics and ask the user, and only expand the query after confirmation	Save API quota and do not automatically consume additional queries
Custom Query	Users can specify any topic/WeChat official account/keyword for targeted queries; when there is no matching data, do not automatically query, and ask the user whether to re-query by recommended words	Flexibly cover any short drama subdirection
Creative Insights	Analyze viral title characteristics, topic trends, and WeChat official account performance	Deeply uncover creative patterns
Visualized Daily Report	Dark theme HTML, cover image + engagement data (hidden when 0) + direct article link	Intuitively showcase daily short drama hot topics
One-click subscription	`--subscribe` Enable daily automatic output	Daily reports are automatically saved in a local folder

✨ Technical Highlights

⚡ Liveness-probe date pre-check:Before calling, use a lightweight request (no keyword, pageSize=1) to actually probe whether the target date has data, replacing pure local clock inference, automatically intercepting invalid queries and avoiding wasted API quota
🧭 Pre-input validation:Before querying, first determine whether the user's category/keyword hits the short drama genre lexicon (topic_keywords as specified ingenre name + all related words, and after a hit,directly use that keyword to query data), and whether the date is within the valid query range;when not satisfied, remind "keyword does not meet query conditions" and recommend related categories and keywords, without initiating an API request
🔄 Automatic fallback:--latest automatically fall back up to 7 days forward to find the most recent date with data before generating the daily report
🛑 No-data confirmation mechanism:When the query has no matching data / full data is insufficient,do not automatically initiate any additional queries(do not automatically downgrade to full data, do not automatically expand genres), output recommended genre keywords and wait for user confirmation, and only re-query after confirmation
🧠 Intelligent clustering:Automatic classification into 9 major genres (time travel/CEO romance/rebirth/suspense/sweet romance/counterattack/period drama/war god/costume drama)
🔒 Secure access:Authenticated via API Key, no account or password required
💾 Caching mechanism:1-hour validity period, avoiding duplicate charges

🔑 Installation and Configuration

Prerequisites

Python 3 runtime environment
Red Fox Hub API Key (go to Red Fox Hub official website to register and obtain it, format is ak_xxxxxxxx)

Environment Variable Configuration

The data query API is authenticated via the request header X-API-KEY , and the Key is obtained from the environment variable REDFOX_API_KEY .

Variable Name	Required	Description
`REDFOX_API_KEY`	Yes	Red Fox Hub API access key

Configuration Method:

macOS/Linux:Append export REDFOX_API_KEY=<值> to ~/.zshrc or ~/.bashrc, then source to make it take effect
Windows:[Environment]::SetEnvironmentVariable("REDFOX_API_KEY", "<值>", "User")(terminal restart required)
Verify after configuration:echo $REDFOX_API_KEY(macOS/Linux) or echo %REDFOX_API_KEY%(Windows)

When calling the query API, record it synchronously via the source field (value is 短剧公众号信息源-GitHub), no additional request to the save API is needed.

📖 User Guide

Basic Usage

1. Input and date pre-check (must be executed, before any API call)

⛔ Core rule: when the keyword/category does not satisfy the short drama genre lexicon, do not initiate any API request

Data Update Rules:Data for the previous day is updated daily at 15:00 (may actually be delayed; subject to the script's actual liveness probe)

Before 15:00: estimated latest available date = T-2 (the day before yesterday) — only as the initial starting point
After 15:00: estimated latest available date = T-1 (yesterday) — only as the initial starting point

Execution flow (mandatory before each query):

Keyword/Category Pre-validation: Determine whether the category/keywords entered by the user match the short drama genre lexicon
- When not satisfied, remind "keywords do not meet the query conditions", recommend related categories and keywords,do not initiate an API request, stop directly and guide the user to use the recommended terms
- Mixed-term scenario: keep valid keywords and continue the query, automatically ignore invalid keywords and notify
- All invalid:do not request the API, stop and recommend related terms
Date Pre-validation: Determine whether the target date format is valid and whether it is later than today; when out of range, notify and recommend the nearest available date
Real Liveness Check: Use pageSize=1 a lightweight request without keywordactually probewhether the target date has data, based on the API response (replacing pure local clock inference)
Date Fallback: When the target date has not been updated or exceeds the query time range, automatically fall back to obtain the most recent time range data, and clearly inform "the current query time has not been updated or exceeds the query time range; the most recent time range data has been automatically obtained for you", without requiring user confirmation
--latest mode also automatically falls back (up to 7 days) to locate the most recent date with data
No-data Confirmation System (v2.3): When a genre keyword query has no matching data / the full dataset is insufficient (<100 records),it is prohibited to automatically initiate any additional queries(automatic downgrade to full dataset is prohibited, automatic genre expansion is prohibited); you must show the user recommended genre keywords and ask "whether to re-query by recommended genre", and only after obtaining user confirmation may a query be initiated
If there is no data within the 7-day fallback period, prompt the user to try again later or contact the data source to confirm the update status

Example Dialogue:

用户:查询今天的短剧公众号日报
Agent:(执行 --latest，脚本自动向前回退定位最近有数据的日期，直接生成日报)

用户:查询"智能辅助驾驶"题材的短剧文章
Agent:⚠️ 关键词 ['智能辅助驾驶'] 不满足短剧查询条件（短剧按题材/剧情词匹配标题，非短剧题材词大概率无结果）
       💡 推荐相关分类和关键词：穿越、霸总、重生、甜宠、悬疑、逆袭、年代、战神、古装、都市
       🛑 关键词均不满足短剧查询条件，未发起任何接口请求。请使用推荐题材词重新查询。

用户:查询"古装"题材的短剧文章（该日期无匹配数据）
Agent:📭 未查询到相关数据 [原因: 查询条件(题材词)在该日期无匹配作品]
       🛑 未发起任何额外查询（禁止自动降级全量 / 自动扩展题材）
       💡 推荐题材：穿越、霸总、重生、甜宠、悬疑、逆袭、年代、战神、古装、都市
       ❓ 是否按推荐题材（如 穿越/霸总）重新查询？请确认后我再查询。

2. Generate Viral Daily Report

# 生成最新一期日报(用户确认后,自动跳过无数据日期,不扣积分)
python3 "$SKILL_PATH/assets/daily_report.py" --latest

# 生成指定日期日报(历史日期已有数据,无需确认)
python3 "$SKILL_PATH/assets/daily_report.py" --date 2026-06-10

# 自定义题材查询(用户指定方向;无匹配/数据不足时不自动扩展,询问用户确认后重查)
python3 "$SKILL_PATH/assets/daily_report.py" --topics "穿越,霸总,重生,悬疑" --latest

# 订阅 / 取消订阅
python3 "$SKILL_PATH/assets/daily_report.py" --subscribe
python3 "$SKILL_PATH/assets/daily_report.py" --unsubscribe

Query Strategy: By default, query all short drama content (pageSize=200).No-data Confirmation System (v2.3): When data is insufficient (fewer than 100 records)no longer automatically expand genres, the script prompts recommended genres (time travel → domineering CEO → rebirth → suspense → sweet romance → counterattack) and waits for user confirmation; only after confirmation, re-query via --topics ; when the user defines custom genres, only use the list provided by the user. Automatically check the liveness of the target date before querying; automatically retry once for empty results.

3. Creative Trend Analysis

After the daily report is generated,mustautomatically perform creative trend analysis based on the clustering results:

Read the genre clustering results, select the TOP 5 trending genres
Analyze the number of viral works, average interaction data, and top work characteristics for each genre
Identify emerging genres gaining traction (small quantity but high interaction)
Output a structured creative trend report

The generated HTML daily report is saved in ~/Downloads/QoderReports/, automatically opened in the browser. The terminal simultaneously outputs the genre classification table + creative trend analysis report.

Advanced Usage

Custom Genre Query

In addition to the default short drama daily report, users can specify any combination of genres for targeted queries:

# 查询穿越题材热门短剧文章
python3 "$SKILL_PATH/assets/daily_report.py" --topics "穿越,时空,重生"

# 查询霸总/甜宠题材
python3 "$SKILL_PATH/assets/daily_report.py" --topics "霸总,甜宠,总裁,虐恋"

# 查询悬疑/反转题材
python3 "$SKILL_PATH/assets/daily_report.py" --topics "悬疑,推理,反转,惊悚"

Custom Query Logic:

Pre-validation (v2.2): Before querying, first check whether the keyword/category matches the short drama theme vocabulary (time travel/domineering CEO/rebirth/sweet romance/suspense/counterattack/period drama/war god/costume drama, etc.). When it does not match, clearly remind "the keyword does not meet the short drama query conditions," andrecommend related categories and keywords(prioritize extracting theme words from the invalid words, then supplement with popular themes), anddo not initiate an API request, guide the user to query again using the recommended words
Automatically ignore invalid words: In mixed-word scenarios, keep the valid keywords and continue querying; automatically ignore invalid keywords and give a prompt; when all are invalid,do not request the API, stop directly and recommend related words
No-data confirmation mechanism (v2.3): When the keyword/theme specified by the user has no matching data,automatic downgrade to a full query is prohibited; automatic theme expansion is prohibited, the script stops and outputs recommended theme keywords; the Agent must first ask the user "whether to re-query according to the recommended themes," and may initiate the query only after receiving confirmation
Insufficient-data confirmation mechanism: For default queries without a specified theme, when the full data is insufficient (<100 records), likewise do not automatically expand the theme; only prompt the recommended themes and ask the user; the data already obtained is still used to normally generate the daily report
All themes provided by the user are queried in one batch through the batch API, with no need to call them one by one
Query results are automatically deduplicated; theme clustering and trend analysis are both generated based on the query results

Time range query

# 查询 6 月短剧爆款
python3 "$SKILL_PATH/assets/daily_report.py" \
  --start-time "2026-06-01 00:00:00" \
  --end-time "2026-06-30 23:59:59"

# 查询近 7 天短剧
python3 "$SKILL_PATH/assets/daily_report.py" \
  --start-time "2026-06-10 00:00:00" \
  --end-time "2026-06-17 23:59:59"

Subscription feature

# 开启每日订阅 — 日报自动产出并保存至 ~/Downloads/QoderReports/
python3 "$SKILL_PATH/assets/daily_report.py" --subscribe

# 取消订阅
python3 "$SKILL_PATH/assets/daily_report.py" --unsubscribe

Command quick reference

Command/parameter	Function	Default value
`--latest`	Automatically fall back up to 7 days forward, locate the most recent date with data, and skip intervals with no data	—
`--date YYYY-MM-DD`	Query by specified date (automatically falls back to the most recent date with data when not updated or out of range)	Today
`--topics "题材1,题材2"`	Custom theme keywords, comma-separated. Before querying, first verify whether they match the short drama theme vocabulary; when they do not, remind + recommend related words anddo not request the API; when there is no matching data, do not query automatically; re-query only after asking the user for confirmation	`短剧`
`--start-time`	Custom start time YYYY-MM-DD HH:MM:SS	—
`--end-time`	Custom end time YYYY-MM-DD HH:MM:SS	—
`--count N`	Number of articles to scan; stop once satisfied	`200`
`--output-dir`	Output directory	`~/Downloads/QoderReports`
`--api-key`	Specify API Key (overrides environment variable)	—
`--subscribe`	Enable daily subscription	—
`--unsubscribe`	Disable daily subscription	—

📊 Output format (mandatory)

⛔ Strictly enforce the rules:

The following template isthe only legal output format; no free-form improvisation, omission, simplification, or reorganization is allowed

It is prohibited to output extra content not defined in the template (such as colloquial text like "Let me help you..." or "The following is...")

It is prohibited to merge or skip any section; even if a section's data is "none yet," that section's title must still be retained

After the daily report is generated, the conversational replymay onlycontain the following content, and must not contain any other text

After each daily report run, the conversational outputmust strictlybe output as-is according to the following template (only replacing the {...} placeholders):

## 短剧-公众号信息源 · {日期} 日报

**扫描 {N} 篇热门短剧文章,聚类 {M} 个题材方向**

---

### 题材概览

| 题材 | 数量 | 占比 | 爆款亮点 |
|------|------|------|---------|
| #{题材名} | {N}篇 | {X}% | 《{头部作品标题}》{阅读数}阅读，{该题材当日内容特征简述} |
| ... | ... | ... | ... |

---

### 创作趋势分析

**一、新兴起量信号**

- 🔥 **#{题材}** — 仅{N}篇但{核心互动指标描述(如:均阅读X+、点赞率X%等)}，{起量原因/内容特征分析}
(若无新兴起量信号，输出：暂无新兴起量信号)

> 新兴起量判断标准：作品数≤3篇但头部阅读超过大盘均值，或互动率(点赞/阅读)显著高于其他题材

**二、爆款标题特征**

| 特征模式 | 出现次数 | 典型案例 | 平均阅读 |
|---------|---------|---------|---------|
| {标题结构特征描述(如:感叹号情绪钩子（！）、"N部"清单推荐体、AI+工具/平台名等)} | {N}次 | 《{标题}》 | {X} |
| ... | ... | ... | ... |
(若无标题数据，输出：暂无爆款标题数据)

> 标题特征分析维度：标点符号使用(！/？/…)、数字清单体(N部/N条)、关键词类型(AI/明星/工具)、情绪钩子结构(反差词/悬念词/承诺词)

**三、核心公众号榜**

| 公众号 | 作品数 | 总阅读 | 代表作 |
|--------|--------|--------|--------|
| @{公众号} | {N}篇 | {X}w | 《{作品}》 |
| ... | ... | ... | ... |
(若无公众号数据，输出：暂无核心公众号数据（本日接口未返回 accountName 字段）)

**四、题材趋势报告**

**题材**：#{题材1}
**作品数**：{N}篇
**平均阅读**：{X}
**头部作品**：《{标题}》— {阅读}阅读

**题材特征**：{基于当日数据描述该题材的内容形态、标题特征、受众画像、流量天花板等}
**创作建议**：{基于数据给出可执行的创作方向、标题公式、题材融合建议等}

**五、#{题材2}**

(同上格式)

**六、#{题材3}**

(同上格式)

> 题材趋势报告选取 TOP 3 题材(排除"其他")逐一展开分析，每个题材必须包含「题材特征」和「创作建议」两个子模块

**七、跨题材对比建议**

- **{题材A} × {题材B}** — {两题材的联动创作建议，基于当日数据中发现的跨题材信号}
- **{主题线索(如:AI短剧)} × 全题材** — {当日数据中发现的跨题材共性趋势及创作机会}
(若无建议，输出：暂无跨题材对比建议)

---

**日报地址**：{HTML文件绝对路径}

> 数据说明：每日15:00更新昨天的数据

The above format isa mandatory specificationAll fields are mandatory and cannot be omitted. The section titles (I, II, III, IV, V, VI, VII) must be retained. If a module has no data, mark "暂无" within that section; the section itself must not be deleted.

Output Quality Requirements：

The "爆款亮点" in the topic overview must include a brief description of the content characteristics of that topic on that day, and must not merely list the top works
The characteristics of viral titles must be summarized based on actual data, and the characteristic patterns must be specific and actionable (e.g., "感叹号情绪钩子" rather than "情绪化标题")
The "题材特征" and "创作建议" in the topic trend report must be based on that day's data and must not use generic descriptions
Cross-topic comparison suggestions must discover real linkage signals from that day's data and must not be speculated out of thin air
In the HTML daily report, each interaction metric (reads 👁 / likes 👍 / comments 💬)when it is 0, do not display that field, and only display metrics that have actual data

🎯 Use Cases

Scenario 1: Short drama screenwriter topic research

Role: Short drama screenwriter

Need: Understand which topics of current public account short dramas are the hottest, so as to choose a topic for the next work

How to Use:

Run the default daily report to view the topic overview and trend analysis
Pay attention to emerging volume signals and discover blue-ocean topics
Analyze the characteristics of viral titles and learn the traffic code

Expected Benefits: Accurately grasp topic trends and improve the hit rate of topic selection

Scenario 2: Content operations daily report tracking

Role: Public account operations / MCN operations

Need: Track viral short drama public accounts daily and form internal team intelligence

How to Use:

Enable --subscribe subscription to automatically produce a daily report every day
Query by topic (--topics "穿越,霸总") to focus on the directions the team cares about
Analyze the core public account rankings and discover high-quality benchmark accounts

Expected Benefits: Establish a team short drama intelligence system and drive content decisions

Scenario 3: Competitor analysis

Role: Brand side / media buying manager

Need: Monitor the short drama promotion performance of competitor public accounts

How to Use:

Use --topics to query competitor-related keywords
Analyze competitor topic distribution and readership data
Compare the differences in topic layout between yourself and competitors

Expected Benefits: Adjust media buying strategies in a timely manner and optimize content differentiation

Scenario 4: Creative trend review

Role: Content director / data analyst

Need: Review changes in short drama creative trends over a period of time

How to Use:

Use --start-time and --end-time to query a specified time period
Compare topic distribution and viral characteristics on different dates
Identify continuously growing topics and declining topics

Expected Benefits: Grasp medium- and long-term trends and guide content strategic planning

🏗️ Project Architecture

Directory Structure

短剧-公众号信息源/
├── SKILL.md                    # 主文档(Skill 定义)
├── README.md                   # 快速开始指南
├── assets/
│   └── daily_report.py        # 主脚本
├── scripts/
│   └── playlet_wechat_daily.py   # 脚本副本
└── references/
    ├── core_workflow.md       # 核心执行流程、日期预检、输出格式模板、错误处理
    └── examples.md            # 使用示例与常见用法组合

Tech Stack

Component	Technology	Description
Runtime Environment	Python 3	Scripting Language
Data Source	Honghu Hub API	Official Account Short Drama Data API
Authentication Method	X-API-KEY	Request Header Authentication
Output Format	HTML/CSS	Dark Theme Visualized Daily Report
Caching Mechanism	JSON File	1-Hour Validity

Platform Adaptation Notes

This skill is adapted from "Short Drama - Douyin Information Source", with the following core adaptations for the Official Account platform:

Dimension	Douyin Version	Official Account Version (This Skill)
Platform Identifier	`platform: 1`	`platform: 0`
Core Metric	Like Count (likeCount)	Read Count (readCount)
Account Field	userName	accountName
Displayed Metrics	Likes, Comments, Shares	Reads (👁), Likes (👍), Comments (💬),hide the field when it is 0
Theme Color	Pink #FB7299	Green #07C160
Icon	🔗👍⭐	👁👍💬
File Naming	Short Drama Douyin Daily Report	Short Drama Official Account Daily Report
Cache File	playlet_douyin_data.json	playlet_wechat_data.json

Core Code Differences:

# 排序逻辑 — 公众号以阅读量为核心排序指标
# 抖音: unique_items.sort(key=lambda x: x.get("likeCount", 0), reverse=True)
# 公众号: unique_items.sort(key=lambda x: x.get("readCount", 0), reverse=True)

# 文件命名
# 抖音: f"短剧抖音日报_{date_str}.html" / "playlet_douyin_data.json"
# 公众号: f"短剧公众号日报_{date_str}.html" / "playlet_wechat_data.json"

Parts Kept Consistent:Input and date pre-check mechanism (no API request if keywords are not satisfied), no-data confirmation system (no automatic downgrade/no automatic expansion, confirm with the user before querying again), data update rules, genre clustering algorithm, deduplication mechanism, caching mechanism, output format template, subscription feature, and creative trend analysis logic.

Notes:

The API uses the same endpoint https://redfox.hk/story/api/parseWork/queryPlayletMsgs
You must set platform: 0 to retrieve Official Account data
Official Accounts and Douyin use different cache files and do not interfere with each other

❓ FAQ

Installation-Related

Q1: How do I get an API Key?

A: Go to Honghu Hub official website to register. After logging in, get it in the personal center. The format is ak_xxxxxxxx. Newly registered users receive free credits.

Q2: I configured the API Key but it says it is invalid?

A: Please check:

Whether the Key has been copied correctly (no leading or trailing spaces)
On Windows, you need to restart the terminal for the environment variable to take effect
Confirm the Key format starts with ak_ Beginning

Usage-Related

Q3: Why does querying today's data show no data?

A: Data is updated daily at 15:00 for the previous day's data (there may be actual delays; refer to the script's real liveness check). The script will automatically fall back to obtain the most recent time range data and clearly inform you that "the current query time has not been updated or exceeds the query time range, so the most recent time range data has been automatically obtained for you." No manual handling is required.

Q4: Which genres can be queried?

A: The script has 9 built-in genre categories: time travel, domineering CEO, rebirth, suspense, sweet romance, counterattack, era, war god, and costume. You can also pass any custom keyword through --topics , but before querying it will first verify whether the keyword matches the short drama genre vocabulary. If not, it will remind you and recommend related terms,without requesting the API, to avoid wasting API quota.

Q5: What is the difference between the default query and a custom theme query?

A: The default query covers all short drama content (pageSize=200). When data is insufficient, it suggests recommended themes and asks the user; only after confirmation does it expand the query. A custom query uses only the theme list you provide. When there is no matching data, it does not automatically query, but asks the user whether to re-query by recommended terms.

Troubleshooting

Q6: What should I do if the script reports a UnicodeEncodeError?

A: On Windows, you need to set the environment variable PYTHONIOENCODING=utf-8. You can add it before the command: $env:PYTHONIOENCODING='utf-8';。

Q7: What are the API error codes?

A: Common error code reference:

Error Code	Meaning	Solution
1002	Page size exceeds 200	Automatically limited by the script; no action needed
3106	Missing API Key	Configure `REDFOX_API_KEY` environment variable
3107	Invalid API Key	Check the Key format and validity
3108	Requests too frequent	Wait and retry
3109	Daily call limit reached	Try again the next day
3201	Insufficient credits	Go to Red Fox Hub to top up

Get Help

If you have other questions, you can check the reference documentation:

core_workflow.md — Core execution flow, date pre-check, output format templates, error handling
examples.md — Usage examples and common usage combinations

📋 Real Output Example (2026-06-15)

The following is a real sample of the complete daily report, for the Agent to refer to regarding output depth and format specifications.

Short Drama - Official Account Information Source · 2026-06-15 Daily Report

Scanned 176 popular short drama articles, clustered into 6 theme directions

Theme Overview

Theme	Count	Share	Hit Highlights
#Other	156 articles	88.6%	"Value Upgrading: The 2.0 Era of Short Dramas and Celebrities Moving Toward Each Other" 23k reads, a large number of AI short drama tool-related content emerged
#Sweet Romance	7 articles	4.0%	"Hot Plant Language" warm bedtime story, average reads 800+, stable audience
#CEO	6 articles	3.4%	Clara's transition to a short drama actor sparked discussion, highest single article 4,905 reads
#Suspense	3 articles	1.7%	"The Truth Behind the Death of a Short Drama Actor" 3,801 reads, gossip-oriented content has strong interaction
#Time Travel	3 articles	1.7%	Shaanxi short drama base's tens-of-millions real-life set fell flat, industry observation content attracted attention
#Costume	1 article	0.6%	"Costume Hairstyle Prompts, with Images" 1,058 reads, a single AI creation assistance article surged

Creative Trend Analysis

1. Emerging Growth Signals

🔥 #Costume — Only 1 article but the like rate reached 3.6% (38 likes/1,058 reads). AI-assisted creation tool content interaction far exceeds the average, indicating prompt/workflow content has sustained breakout potential
🔥 #Suspense — Only 3 articles but top reads reached 3,801. The combination title of gossip reveal + short drama industry insider has higher interaction efficiency than the overall average

2. Hit Title Characteristics

Feature Pattern	Occurrences	Typical Examples	Average Reads
Exclamation mark emotional hook (!)	93 times	"OiiOii 2.0 Major Upgrade, Short Drama E-commerce Is Really Going Crazy..."	1374
Question mark suspense hook (?)	55 times	"The Boundary Between Long and Short Dramas Blurs, What Opportunities Do Actors Have in the Hundred-Billion Short Drama New Landscape?"	1325
"N Works" List Recommendation Format	13 times	"5 High-Scoring Addictive Short Drama Collection! CEO Sweet Pet, Urban Healing"	1072
AI + Tool/Platform Name	15 times	"The AI Short Drama with 700 Million Views Across the Internet, I Found the God-Level Production Tool Behind It!"	About 6500

III. Core Official Account Ranking

No core official account data available (the API did not return the accountName field today)

IV. Genre Trend Report

Genre: #SweetPet Number of Works: 7 articles Average Reads: about 900 Top Work: "Hot Plant Language" by Dick Sheep Boy (warm sweet pet bedtime story) — 1,258 reads

Genre Characteristics: The sweet pet genre mainly takes the forms of "bedtime stories," "couple avatars," and "hidden gem drama recommendations." Titles generally feature emotional keywords such as "sweet," "healing," and "complete," with high audience stickiness but a low traffic ceiling, and overall readership concentrated in the mid-tier. Creative Suggestions: Can combine "CP-oriented" fan-created content and "sweet pet + other genres" composite tags (such as sweet pet × historical, sweet pet × time travel) to break out of the niche; add completion-promise hooks like "watch with eyes closed," "hidden gem," and "super sweet ending" to titles to increase clicks.

V. #CEO

Genre: #CEO Number of Works: 6 articles Average Reads: about 2911 Top Work: "'Asia's No. 1 Beauty' Clara, Abandoned by a Wealthy Family, Transitions to Short Drama Actress!" — 4,905 reads

Genre Characteristics: Today's heat in the CEO genre was mainly driven by gossip news about "celebrities entering the short drama scene," rather than traditional CEO drama recommendations. Contrast words such as "wealthy family," "transition," and "abandoned" form the core traffic hooks, and the Hannan filming location topic also drove localized spread. Creative Suggestions: Can leverage celebrity/actor topics to enter the CEO genre; use a "status contrast + twist" formula for title structure (such as "abandoned by XX, transitions to XX"), while also combining "high-score collection" and "addictive short drama" list formats for long-tail traffic.

VI. #Suspense

Genre: #Suspense Number of Works: 3 articles Average Reads: about 2047 Top Work: "The Truth Behind the Death of a Short Drama Actor, Ady An's Comeback, Hou Minghao Dragged Out to Test the Waters..." — 3,801 reads

Genre Characteristics: Today, the suspense genre appears in the form of "industry gossip + truth reveal," with titles generally using a hook structure of multiple celebrity names linked together + suspense question marks; there are also policy-oriented contents such as silver-haired anti-fraud AI micro short dramas (1,718 reads). Overall quantity is low, but per-article interaction is above the platform average. Creative Suggestions: Suspense-themed WeChat official account content is better suited to non-fiction directions such as "insider revelations" and "truth restoration." Titles can stack multiple celebrity/event names to create a sense of information density, while also paying attention to policy trends such as "anti-fraud" and "social issues," which makes it easy to gain platform traffic boosts.

VII. Cross-genre comparison suggestions

#Domineering CEO × #Sweet Romance — It is recommended to also pay attention to collaborative creation under the composite tag "Domineering CEO Sweet Romance." Today's "Compilation of 5 High-Scoring Addictive Short Dramas! Domineering CEO Sweet Romance, Urban Healing" (2,606 reads) has verified that the compilation format for fused genres is effective, and the audience overlap between the two genres can be further broken down.
#AI Short Dramas (implicit theme within Other categories) × All genres — Today's 38 AI short drama-related pieces all received 2,630 reads, far exceeding the overall average of 1,994. The direction of "production tutorials/tool reviews" combining AI tools + any genre is currently a notable traffic depression, and creators across genres are advised to pay attention to AI production workflow content.

Daily report address：C:\Users\马祯\Downloads\QoderReports\短剧公众号日报_2026-06-15.html

Data note: updated daily at 15:00 with yesterday's data

About this skill

📝 Overview

✨ Features

🎯 Core Features

✨ Technical Highlights

🔑 Installation and Configuration

Prerequisites

Environment Variable Configuration

📖 User Guide

Basic Usage

1. Input and date pre-check (must be executed, before any API call)

2. Generate Viral Daily Report

3. Creative Trend Analysis

Advanced Usage

Custom Genre Query

Time range query

Subscription feature

Command quick reference

📊 Output format (mandatory)

🎯 Use Cases

Scenario 1: Short drama screenwriter topic research

Scenario 2: Content operations daily report tracking

Scenario 3: Competitor analysis

Scenario 4: Creative trend review

🏗️ Project Architecture

Directory Structure

Tech Stack

Platform Adaptation Notes

❓ FAQ

Installation-Related

Usage-Related

Troubleshooting

Get Help

📋 Real Output Example (2026-06-15)

Short Drama - Official Account Information Source · 2026-06-15 Daily Report

Theme Overview

Creative Trend Analysis