Based on multi-dimensional data analysis, it provides comprehensive account health diagnosis and optimization suggestions for official accounts
Overview
Official Account Diagnosis is an intelligent analysis tool that obtains real operational data of official accounts through the RedFox API, performs scoring diagnosis based on the four dimensions of content health, user activity, core data performance, and operational compliance, and automatically generates optimization suggestions benchmarked against industry levels.
- Core Value: Say goodbye to subjective judgment and use data to drive official account operational decisions. One diagnosis lets you see the full picture of the account and clarify the direction for optimization
- Target Users: Official account owners, new media operators, MCN agencies, brands, content creators
- Technical Foundation: Based on RedFox API real-time data + Python scoring engine + Agent intelligent suggestion generation
Features
Core Capabilities
| Feature | Description |
|---|---|
| 📊 Four-Dimensional Scoring | Four-dimensional diagnostic scoring (content health/user activity/core data/operational compliance), v4.1 category adaptation (automatic weight/threshold adjustment for 6 account categories), explicit scoring of viral hit rate (100,000+) |
| 🏆 Intelligent Rating | S/A/B/C/D/E six-level rating (S≥80 points) + industry benchmarking analysis |
| 📈 Data Visualization | Recent work data table, with reads/likes/comments/Wow clearly visible at a glance |
| 💡 Optimization Suggestions | Divided into three levels: urgent/key/continuous, with each suggestion including expected quantitative effects |
| 🔍 Similar Accounts | Automatically matches benchmark accounts in the same track and compares horizontally to find gaps |
| 🔗 Clickable Links | Account names and work titles both support one-click jumps to WeChat |
Highlights
- ⚡ One-Sentence Diagnosis: Enter the official account name to get a complete report, with no complex configuration required
- 🔄 Multi-Account Comparison: Supports diagnosing multiple accounts simultaneously and generating comparison reports
- 📋 Enforced Format Output: 5-chapter fixed template, with chapters/order/format strictly locked and no deviation allowed
One-Click Installation
Prerequisites
- Python 3.8+ installed
- Registered RedFox Hub account and obtained an API Key
Installation Steps
- Place the skill folder into your Skills directory
- Install Python dependencies:
pip install requests - Configure API Key (see below)
Configure API Key
Obtain API Key
- Visit the RedFox Hub official website to learn more about the service
- Go to the registration page to register an account
- Newly registered users will receive free credits, and can start using it immediately
- After registering and logging in, obtain the API Key in the personal center, in the format
ak_xxxxxxxx
Set Environment Variables
REDFOX_API_KEY must be obtained from environment variables. If not set, the Agent will proactively help you configure it:
- macOS/Linux:Add
export REDFOX_API_KEY=<值>to~/.zshrcor~/.bashrc, thensourcethe corresponding file - Windows:Use
[Environment]::SetEnvironmentVariable("REDFOX_API_KEY", "<值>", "User")to set a user-level permanent environment variable (terminal restart required)
After configuration is complete, verify:echo $REDFOX_API_KEY(macOS/Linux) or echo %REDFOX_API_KEY%(Windows)
Usage Guide
Trigger Methods
Automatically activates when the user mentions any of the following keywords:
- "Diagnose Official Account", "Account Analysis", "Official Account Checkup"
- "Account Evaluation", "View XX Official Account Data", "Analyze XX Account"
- Directly enter the official account name + "diagnose/analyze" (e.g., "Shidian Dushu diagnose")
On the first interaction, the Agent will proactively greet the user and guide them to enter an account.
Common Commands Quick Reference
| Command | Description |
|---|---|
诊断"公众号名称" |
Enter the name to get a complete diagnostic report |
对比诊断"A"和"B" |
Multi-account horizontal comparison + differentiated recommendations |
诊断公众号ID"xxx" |
Query by official account ID (not the Chinese name) |
Usage Examples
Example 1: Standard Diagnosis
User: Diagnose the "Shidian Dushu" official account AI: Output a complete diagnostic report (account information → overall score → work data → optimization recommendations → industry benchmarking)
Example 2: Multi-account Comparison
User: Compare and diagnose "Shidian Dushu" and "Dongjian" AI: Output two diagnostic reports separately + horizontal comparison summary table + differentiated recommendations
Example 3: Account Not Found
User: Diagnose "Nonexistent Official Account 123" AI: No account found [Nonexistent Official Account 123]. This account may not yet be indexed or the name may be incorrect. Please verify the official account name and try again.
⚠️ Mandatory Output Format Specification
Diagnostic ReportMust and can onlybe output using the fixed 5-section template:1. Account Information → 2. Overall Score → 3. Recent Work Data → 4. Optimization Recommendations → 5. Industry Benchmarking Analysis. Sections cannot be omitted, the order cannot be changed, and the format cannot deviate. All field names, table structures, and emoji markers must be strictly consistent with the template. Output that violates the template is considered unqualified.
For detailed technical specifications, scoring algorithms, and output format templates, see Core Workflow
Use Cases
Scenario 1: Account Owner Self-Check and Optimization
Needs:Understand your own official account's standing in the industry and find directions for optimization
How to Use:
- Directly enter your own official account name for diagnosis
- Check the four-dimension scores to find weaknesses
- Improve gradually according to the priority of the optimization recommendations
Expected Benefits:Clarify account health, quantify optimization results, and avoid blind operation
Scenario 2: Competitor Benchmarking Analysis
Needs:Analyze competitors' operation strategies and data performance
How to Use:
- Diagnose the target competitor's official account
- Check industry benchmarking and similar accounts
- Compare and analyze differentiated advantages and gaps
Expected Benefits:Grasp competitor trends, learn from successful experience, and adjust your own strategy
Scenario 3: MCN Batch Evaluation
Needs:Evaluate the value of accounts under management or potential signing accounts
Usage:
- Diagnose candidate accounts one by one
- Compare overall scores and core metrics side by side
- Assess growth potential based on optimization suggestions
Expected Benefits: Data-driven signing decisions, quantify the account's commercial value
Scenario 4: Content Strategy Formulation
Requirement: Formulate content plans based on account diagnosis results
Usage:
- Diagnose accounts to obtain scores for quality stability, content verticality, etc.
- Determine improvement priorities based on the "modules to be optimized"
- Adjust content direction and publishing strategy with reference to industry benchmarks
Expected Benefits: Evidence-based content planning, improve overall operational efficiency
Project Architecture
Directory Structure
公众号账号诊断/
├── SKILL.md # 技能说明文档(本文件)
├── scripts/
│ ├── wechat_analyzer.py # 入口点:argparse 命令路由(query/sync/generate_html)
│ ├── api_client.py # HTTP 通信层:红狐 API 凭证管理 + POST 请求封装
│ ├── scoring.py # 评分引擎:作品辅助函数 + 四维度评分 + 等级判定
│ ├── analyzer.py # 分析编排:单账号评分处理 + 查询/同步命令
│ ├── report.py # HTML 报告:模板替换 + 单账号/多账号报告生成
│ └── test_wechat_analyzer.py # 单元测试:辅助函数 + 评分函数容错(42 个测试)
├── references/
│ ├── core_workflow.md # 核心工作流(Agent执行参考)
│ ├── workflow_guide.md # 工作流详细指南
│ └── api_guide.md # API接口与评分逻辑说明
├── assets/
│ └── report_template.html # 单账号HTML报告模板
└── output/ # 输出目录(运行时自动生成)
├── raw_data.json # API原始数据
└── report_data.json # 结构化诊断数据
Tech Stack
| Component | Technology |
|---|---|
| Runtime Environment | Python 3.8+ |
| HTTP Client | requests (native) |
| Data Source | RedFox API (redfox.hk) |
| Output Format | Markdown + JSON + HTML |
| Authentication Method | Header X-API-KEY + environment variable REDFOX_API_KEY |
Core Modules
| Module File | Function | Responsibility |
|---|---|---|
wechat_analyzer.py |
main |
argparse entry point, routes to each subcommand |
api_client.py |
https_post |
RedFox API HTTP POST request wrapper |
api_client.py |
_get_credential |
Read API Key from environment variable → shell configuration file |
scoring.py |
_score_content_health |
Content health (6 sub-items weighted, 0-10 points) |
scoring.py |
_score_user_activity |
User activity (5 sub-items weighted, 0-10 points) |
scoring.py |
_score_core_data |
Core data performance (6 sub-items, 0-31 points) |
scoring.py |
_score_operation_compliance |
Operational compliance (3 sub-items, 0-10 points) |
analyzer.py |
cmd_query |
API query + raw data saving |
analyzer.py |
_analyze_single_account |
Four-dimension score calculation + structured output |
analyzer.py |
cmd_sync_notes |
Sync account work data (subscription push) |
report.py |
cmd_generate_html |
Single-account HTML report generation |
report.py |
cmd_generate_multi_html |
Multi-account comparison HTML report generation |
FAQ
Installation-related
Q1: What should I do if it prompts "REDFOX_API_KEY not found"?
A: Please set the environment variable according to the steps in "One-click Installation → Configure API Key." If you don't know how to configure it, just tell the Agent, and it will do it for you.
Q2: What dependencies need to be installed?
A: Only the requests library:pip install requests. Python 3.8+ is sufficient to run it.
Usage-related
Q3: Does it support querying by official account ID?
A: Yes. If you know the official account ID (e.g., gh_xxxxxxxx), the Agent will automatically recognize it and use the ID for the query.
Q4: Can multiple accounts be diagnosed at the same time?
A: Yes. Enter "Compare diagnosis of A and B" to get a multi-account comparison report.
Q5: How often is the data updated?
A: The data comes from the RedFox API, and its timeliness depends on the API cache policy. The data confidence level will be indicated at the end of the report.
Troubleshooting
Q6: It prompts "No information found for this official account"?
A: Possible reasons: ① The account name was entered incorrectly; ② The account's recent posts did not meet the inclusion criteria. Please check the accuracy of the name and try again.
Q7: What should I do if the data looks incorrect?
A: All data comes from the Honghu API interface; diagnostic results only reflect the data returned by the interface. If you have any questions, you can contact the Honghu platform to confirm data accuracy.
Get Help
- Honghu Hub official website:https://redfox.hk/
- Skill implementation details: see Core Workflow