playlet-gzh-feed

Short Drama - Official Account Information Source

📝 Introduction

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

With simple commands, you can:

🔥 Discover the day's viral official account short drama articles
📊 Get popular content intelligently clustered by genre
📈 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 official account owners who need to track official account short drama hot topics.

⚠️ Important Reminder: Data is updated daily at 15:00 with the previous day's data. When there is no data for the target date,you must first inform the user and wait for confirmation before calling the interface. Automatic retrieval is prohibited.

✨ Features

🎯 Core Features

Feature Module	Capability Description	Core Value
Viral Discovery	Filter popular content from official account short drama articles by read count	Precisely locate high-heat short drama works
Genre Clustering	Automatically identify genre directions (time travel/domineering CEO/rebirth/suspense, etc.)	Daily genre classification is dynamically determined by content
Intelligent Query	By default, query all short dramas; when data is insufficient, automatically expand genres for batch queries	Save interface quota and obtain data efficiently
Custom Query	Users can specify any genre/official account/keyword for targeted queries	Flexibly cover any short drama niche direction
Creative Insights	Analyze viral title characteristics, genre trends, and official account performance	Deeply uncover creative patterns
Visual Daily Report	Dark-themed HTML, cover images + engagement data + direct article links	Intuitively display daily short drama hot topics
One-Click Subscription	`--subscribe` Enable automatic daily production	Daily reports are automatically accumulated in a local folder

✨ Technical Highlights

⚡ Batch Query: All genres are queried at once through a batch interface, saving the number of interface calls
🧠 Intelligent Clustering: Automatic classification into 9 major genres (time travel/domineering CEO/rebirth/suspense/sweet romance/counterattack/period/war god/costume)
🔒 Secure Access: Authenticated via API Key, no account or password required
📅 Intelligent Date Judgment: Built into the script DATA_UPDATE_HOUR = 15 constants, automatically detects the validity of the target date
💾 Caching Mechanism: 1-hour validity period, avoiding duplicate charges

🔑 Installation and Configuration

Prerequisites

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

Environment Variable Configuration

The data query interface authenticates via the request header X-API-KEY ; the Key is obtained from the environment variable REDFOX_API_KEY .

Variable Name	Required	Description
`REDFOX_API_KEY`	Yes	RedFox 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 interface, record synchronously via the source field (value is 短剧公众号信息源-GitHub), no additional request to the save interface is needed.

📖 Usage Guide

Basic Usage

1. Date validity pre-check (must be executed, before any interface call)

⛔ Core rule: without user confirmation, calling any data interface is prohibited, and automatically executing --latest

Data Update Rules: data for the previous day is updated daily at 15:00

Before 15:00: latest available date = T-2 (the day before yesterday)
After 15:00: latest available date = T-1 (yesterday)

Execution flow (mandatory before each query):

Get the current system date T and current time, and calculate the latest available date according to the 15:00 rule
Determine whether the target date requested by the user is in the no-data interval (i.e., > latest available date)
If the target date has data(≤ latest available date): directly execute step 2, no additional confirmation needed
If the target date has no data(> latest available date), output a prompt to the user andonly after the user explicitly confirmscan you continue:

**⚠️{查询日期}数据尚未更新**
数据更新规则:每日15:00更新前一天的数据
当前可查询的最新日期:{最新可查询到数据的日期}

是否需要查询{最新可查询到数据的日期}的数据?

If the user refuses, do not execute any interface call

Example Dialogue:

用户:查询今天的短剧公众号日报
Agent:⚠️2026-06-16数据尚未更新
      数据更新规则:每日15:00更新前一天的数据
      当前可查询的最新日期:2026-06-14

      是否需要查询2026-06-14的数据?
用户:好的
Agent:(执行 python3 daily_report.py --latest)

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); when data is insufficient, automatically add popular themes (time travel → domineering CEO → rebirth → suspense → sweet romance → counterattack); all themes are queried at once through the batch interface, no need to call them one by one. When the user customizes themes, use only the list provided by the user, also queried in batch.

3. Creative Trend Analysis

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

Read the theme clustering results and select the TOP 5 popular themes
Analyze the number of viral hits, average interaction data, and top work characteristics for each theme
Identify emerging rising themes (few in number but high in interaction)
Output a structured creative trend report

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

Advanced Usage

Custom Theme Query

In addition to the default short drama daily report, users can specify any combination of themes 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:

All themes provided by the user are queried at once through the batch interface, 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 use the latest date with data, skipping intervals without data	—
`--date YYYY-MM-DD`	Query by specified date (if there is no data, a prompt will appear and ask to switch)	Today
`--topics "题材1,题材2"`	Custom topic keywords, separated by commas	`短剧`
`--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 when 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 is theonly 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", the section title must still be retained

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

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

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

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

---

### 题材概览

| 题材 | 数量 | 占比 | 爆款亮点 |
|------|------|------|---------|
| #{题材名} | {N}篇 | {X}% | 头部作品亮点描述 |
| ... | ... | ... | ... |

---

### 创作趋势分析

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

- 🔥 **#{题材}** — 仅{N}篇但均阅读{X}+,描述
(若无新兴题材,输出:暂无新兴起量信号)

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

| 特征模式 | 出现次数 | 典型案例 | 平均阅读 |
|---------|---------|---------|---------|
| {特征1} | {N}次 | 《{标题}》 | {X}w |
| ... | ... | ... | ... |
(若无标题数据,输出:暂无爆款标题数据)

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

| 公众号 | 作品数 | 总阅读 | 代表作 |
|--------|--------|--------|--------|
| @{公众号} | {N}篇 | {X}w | 《{作品}》 |
| ... | ... | ... | ... |
(若无公众号数据,输出:暂无核心公众号数据)

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

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

**题材特征**:{描述该题材的共性特征}
**创作建议**:{针对该题材的创作建议}

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

(同上格式)

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

(同上格式)

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

- **{题材}** — 建议同步关注{相关题材}的联动创作,观察题材融合趋势
(若无建议,输出:暂无跨题材对比建议)

---

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

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

The above format isa mandatory specification, all fields cannot be omitted, and the section titles (One, Two, Three, Four, Five, Six, Seven) must be retained. If a module has no data, mark "None yet" within that section; do not delete the section itself.

🎯 Use Cases

Scenario One: Topic Research for Short Drama Screenwriters

Role: Short drama screenwriter

Need: Understand which short drama topics are currently hottest on official accounts, 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 growth signals and discover blue-ocean topics
Analyze the characteristics of hit titles and learn the traffic code

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

Scenario Two: Daily Tracking for Content Operations

Role: Official account operations / MCN operations

Need: Track short drama official account hits 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 official account rankings and discover high-quality benchmark accounts

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

Scenario Three: Competitor Analysis

Role: Brand side / media buying manager

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

How to Use:

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

Expected benefits: Adjust the distribution strategy in a timely manner and optimize content differentiation

Scenario 4: Creative trend review

Role: Content Director / Data Analyst

Requirement: 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 genre distribution and hit characteristics across different dates
Identify continuously growing genres and declining genres

Expected benefits: Grasp medium- and long-term trends and guide content strategy planning

🏗️ Project Architecture

Directory Structure

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

Tech Stack

Component	Technology	Description
Runtime Environment	Python 3	Scripting Language
Data Source	Honghu Hub API	WeChat Official Account short drama data interface
Authentication Method	X-API-KEY	Request header authentication
Output Format	HTML/CSS	Dark theme visual daily report
Caching Mechanism	JSON file	1-hour validity period

Platform Adaptation Notes

This skill is based on "Short Drama - Douyin Information Source" and has made the following core adaptations for the WeChat Official Account platform:

Dimension	Douyin Version	WeChat Official Account Version (this skill)
Platform Identifier	`platform: 1`	`platform: 2`
Core Metric	Like count (likeCount)	Read count (readCount)
Account Field	userName	accountName
Displayed Metrics	Likes, comments, shares	Reads (👁), likes (👍), shares (↗)
Theme Color	Pink #FB7299	Green #07C160
Icon	🔗👍⭐	👁👍↗
File Naming	Short Drama Douyin Daily Report	Short Drama WeChat Official Account Daily Report
Cache File	playlet_douyin_data.json	playlet_gzh_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_gzh_data.json"

Parts Kept Consistent: Date pre-check mechanism, data update rules, batch query strategy, genre clustering algorithm, deduplication mechanism, caching mechanism, output format template, subscription feature, creative trend analysis logic.

Notes:

The API interface uses the same endpoint https://redfox.hk/story/api/parseWork/queryPlayletMsgs
Must set platform: 2 to retrieve WeChat Official Account data
WeChat Official Account 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 the Honghu Hub official website to register, then get it from the personal center after logging in. The format is ak_xxxxxxxx. Newly registered users receive free credits.

Q2: Configured the API Key but it says invalid?

A: Please check:

Whether the Key was copied correctly (no spaces before or after)
On Windows, the terminal must be restarted for environment variables to take effect
Confirm the Key format is ak_ beginning

Usage Related

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

A: Data is updated daily at 15:00 with the previous day's data. Before 15:00, the latest queryable data is the day before yesterday; after 15:00, it is yesterday. The script will indicate the latest queryable date and ask whether to switch.

Q4: Which genres can be queried?

A: The script has 9 built-in genre categories: time travel, domineering CEO, rebirth, suspense, sweet romance, counterattack, period, war god, and costume. You can also pass any custom keyword via --topics .

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

A: The default query covers all short drama content (pageSize=200), and automatically adds popular genres when there is insufficient data; a custom query uses only the genre list you provide, also queried in batches.

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 do the API error codes mean?

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 the `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 红狐Hub to top up

Getting 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

About this skill

📝 Introduction

✨ Features

🎯 Core Features

✨ Technical Highlights

🔑 Installation and Configuration

Prerequisites

Environment Variable Configuration

📖 Usage Guide

Basic Usage

1. Date validity pre-check (must be executed, before any interface call)

2. Generate Viral Daily Report

3. Creative Trend Analysis

Advanced Usage

Custom Theme Query

Time Range Query

Subscription Feature

Command Quick Reference

📊 Output Format (Mandatory)

🎯 Use Cases

Scenario One: Topic Research for Short Drama Screenwriters

Scenario Two: Daily Tracking for Content Operations

Scenario Three: Competitor Analysis

Scenario 4: Creative trend review

🏗️ Project Architecture

Directory Structure

Tech Stack

Platform Adaptation Notes

❓ FAQ

Installation Related

Usage Related

Troubleshooting

Getting Help