SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillswechat-fastest-growing

wechat-fastest-growing

Marketing & growth

View repository

Updated 10-15 15:25

About this skill

Official Account Reading Growth Ranking

Introduction

The Official Account Reading Growth Ranking is a tool for content operations and new media research, providing areading growth rate rankingquery tool. It pulls official ranking data through scripts, helping users quickly discover official accounts and representative works with fast recent reading volume growth.

Through this Skill, you can:

  • 📊 Same author's viral article vs lowest-read article comparison: For the same account, compare the differences between its "viral article" and "lowest-read article" in topic selection, title, and angle. Directly tell you the specific tactics you can replicate.
  • 📈 High-growth account type analysis: Analyze the track distribution and common strategies of recently high-growth accounts, judge the current real traffic trends, and provide suggestions on which can be transferred to other platforms.

Suitable for roles such as official account operators looking for high-growth benchmarks, editors reviewing topic selection, and researchers observing track popularity.

Features

🎯 Core Features

  • 📊 Growth Rate Ranking: Query official account reading growth rate ranking data by date (script outputs a Markdown table)
  • 🔗 Clickable Titles: Titles in the table are already original text links, making it easy to jump and verify
  • 📌 Metric Description: The ranking includes fields such as "composite score index"; formula and weighting definitions see references/core_workflow.md
  • 📈 Growth Analysis: Based onthe same script outputcomplete three outputs (viral article table, work type table, 300–500 word summary); fields and item count limits are subject to the core process

✨ Highlights

  • ⏰ Date Semantics: Supports colloquial "latest/yesterday" and specified dates;rankDate supports "yesterday"、"today"、"YYYY-MM-DD"(mapping and default rules see core process)
  • 🔒 Data Authenticity: Mandatory use of scripts/fetch_growth_rank.py；script stdout must be displayed as-is, and the table must not be rewritten or rearranged
  • 📅 Query Window: Only supportswithin the last 30 daysof rankDate; when querying the latest, if there is no data for yesterday, it willautomatically trace backward(query day by day, stop when found, see core process)

One-Click Installation

Prerequisites

  • Python 3.8 or above
  • requests library:pip install requests
  • Red Fox Hub API Key, format ak_xxxxxxxx

Installation Method

SkillHub

  1. Go to SkillHub
  2. Search wechat-fastest-growing or Official Account Reading Growth Ranking
  3. Follow the platform instructions to complete installation (supports conversational installation or local Zip import)

ClawHub

  1. Go to ClawHub
  2. Search wechat-fastest-growing or Official Account Reading Growth Ranking
  3. You can use CLI:openclaw skills install wechat-fastest-growing or clawhub install wechat-fastest-growing, or download the skill package for local import

Method 2: Standalone Command-Line Use

No need to install the skill package; after configuring the API Key, you can run the script directly:

pip install requests
python scripts/fetch_growth_rank.py --rankDate yesterday

After installation is complete, visit Red Fox HubWebsite Log in Register and obtain an API Key (new users receive free credits), configure the environment variables REDFOX_API_KEY(see below), restart the terminal, and you can initiate queries in the conversation.

Environment Variable Configuration

Variable Name Required Description
REDFOX_API_KEY Yes Red Fox Hub API access key, format ak_xxxxxxxx
COZE_REDFOX_API_7633629455969337344 No Compatible with the old variable name (the script automatically falls back to read it)

macOS / Linux：

echo 'export REDFOX_API_KEY=<你的apikey>' >> ~/.zshrc
source ~/.zshrc

Windows（PowerShell）：

[Environment]::SetEnvironmentVariable("REDFOX_API_KEY", "<你的apikey>", "User")

After configuration, the terminal must be restarted. Verify:echo $REDFOX_API_KEY(macOS/Linux) or echo %REDFOX_API_KEY%（Windows）。

Three-level fallback mechanism: When the script reads the API Key, it automatically obtains it in the order of environment variable → shell configuration file (~/.bashrc / ~/.zshrc / ~/.bash_profile / ~/.profile) → prompt the user to configure, without needing to pass it in explicitly.

Authentication

Obtain API Key

  1. Visit Red Fox Hub official website to learn about the service details
  2. Go to registration page to register an account
  3. Newly registered users will receive free credits, and can immediately start using the API service
  4. After registering and logging in, obtain the API Key in the personal center, in the format ak_xxxxxxxx

Configure API Key

  • REDFOX_API_KEY Obtained from the environment variable, format ak_xxxxxxxx
  • The script supports three-level fallback reading: environment variable → shell configuration file auto-detection → prompt for manual configuration
  • It is recommended to persist the configuration through environment variables (see above for details Environment Variable Configuration）

Usage Guide

Basic Usage

1. Initiate a growth ranking query

Specify the date requirement in the conversation (can be omitted; defaults to querying yesterday):

User: Official account growth ranking

Assistant: Used according to the core process rankDate="yesterday"to fetch; the following is the complete table output by the script (as-is).…

2. View the ranking results

The assistant runs scripts/fetch_growth_rank.py, and displays the full stdout as-is (the Markdown table must not be omitted, recalculated on one's own, or replaced with a "summary table"). If the script fails or there is no data, state it truthfully,fabricating rankings or read counts is prohibited。

3. Growth trend analysis (as needed)

When the user needs interpretations such as "characteristics, patterns, why growth is fast", based on the real ranking already displayed, complete according to the core process 3 blocks of output(viral article analysis table ≤5 entries, work type analysis table ≤5 entries, summary 300–500 words).

Advanced Usage

1. Specify date and parameters

Determine according to the user's wording rankDate. If the date is beyond the last 30 days, state that it is not supported,fabrication is prohibitedranking.

User: Check the growth ranking for March 15

Assistant: Use rankDate="2026-03-15" to call the script; the following is the stdout as-is table.…

2. Pull the ranking directly from the command line

Execute in the project directory (parameter names and values must be consistent):

python scripts/fetch_growth_rank.py --rankDate "<yesterday|today|YYYY-MM-DD>"

3. Structured growth interpretation

User: Which accounts have grown fast recently, and what do they have in common?

Assistant: First output the script ranking (as-is), then provide two analysis tables and a summary according to the core process.…

4. Follow the hard constraints of the core process

Before running ranking retrieval and growth analysis, you must open and follow references/core_workflow.md(user intent → rankDate → script parameters → three-point analysis). Do not skip any of the hard constraints within.

Common commands quick reference

User wording / command Function
“Latest / Today / Official Account growth ranking” rankDate Map according to the core process (mostly yesterday）
“Yesterday / Growth ranking for a specified date” rankDate is YYYY-MM-DD or an alias allowed by the rules
“Growth trends / characteristics / patterns” Script table as-is + the 3-paragraph analysis specified by the core process
python scripts/fetch_growth_rank.py --rankDate yesterday Command line pulls yesterday's growth ranking

Use cases

Scenario 1: Find high-growth benchmarks

Role: Official account operator

Requirement: Want to see accounts with fast recent reading growth and their representative works

How to use：

  1. Run the script by date to pull the growth ranking
  2. Display the table as-is; click the title to jump to the original article for verification
  3. Optionally follow up with analysis of growth characteristics and commonalities

Expected benefits: Quickly identify benchmark accounts and viral topic directions

Scenario 2: Topic selection and review

Role: Content editor

Requirement: Combine the ranking to look at viral titles and account strategies

How to use：

  1. Pull the growth ranking for a specified date or “latest”
  2. Output the viral article analysis table and work type table according to the core process
  3. Read a 300–500 word summary to distill patterns

Expected benefits: Provide verifiable data reference for the next round of topic selection

Scenario 3: Review for a specified date

Role: Analyst / manager

Requirement: Check whether the growth ranking for a certain day is abnormal

How to use：

  1. Use rankDate="YYYY-MM-DD" to query (note the 30-day window)
  2. Compare the composite score index with reading and engagement metrics
  3. For abnormal entries, jump to the original article for secondary verification

Expected benefits: Discover single-day data fluctuations and potential operational actions

Scenario 4: Track observation

Role: Researcher

Requirement: Get a rough view of which accounts appear frequently on the growth ranking

How to use：

  1. Pull the ranking for multiple consecutive days and observe accounts that appear repeatedly
  2. First look at the ranking as-is; request structured analysis when needed
  3. Combine with the work type table to summarize the content forms of the track

Expected benefits: Grasp track popularity shifts and changes in content forms

Project architecture

Directory structure

wechat-fastest-growing/
├── SKILL.md                          # 产品说明文档
├── references/
│   ├── core_workflow.md              # 标准流程、公式、分析字段与硬性约束
│   └── api-spec.md                   # 红狐 Hub API 参数与响应说明
└── scripts/
    └── fetch_growth_rank.py          # 调用 API 获取榜单并输出 Markdown 表格

Tech stack

Project Description
Runtime environment Python 3.8+
Core dependencies requests(the rest are standard libraries)
Data source Red Fox Hub API (getGzhCozeSkillDataRaise）
Deployment method SkillHub / ClawHub / command-line script

Core modules

Module Responsibility
fetch_growth_rank.py Parse rankDate, call the Red Fox Hub API, and output a Markdown ranking table (with the title as a clickable link)
core_workflow.md User intent mapping,rankDate rules, stdout verbatim constraints, three-point analysis template, and item count limits
api-spec.md Endpoint, authentication, request parameters, and field descriptions

FAQ

Installation-related questions

Q1: What should I do if no API Key is detected?

Follow One-click installation to register with Red Fox Hub and configure REDFOX_API_KEY. Newly registered users get free credits.

Q2: How do I verify that the configuration has taken effect?

Run echo $REDFOX_API_KEY(macOS/Linux) or echo %REDFOX_API_KEY%(Windows), and confirm that the output starts with ak_ . If it has not taken effect, restart the terminal.

Q3: Which deployment methods are supported?

It supports installation via the SkillHub and ClawHub platforms, and can also be run directly with scripts/fetch_growth_rank.py for standalone invocation.

Usage-related questions

Q4：rankDate What formats are supported?

Supports "yesterday"、"today"、"YYYY-MM-DD". Colloquial expressions such as "latest/growth ranking" are mostly mapped to yesterday; when data is empty, it automatically traces back to the previous day, querying day by day until a date with data is found, and stops immediately once found (see the core workflow).

Q5: How far back can data be queried?

Only supportsthe most recent 30 days; beyond this range the script will report an error, so do not let the model fabricate rankings.

Q6: What does the growth analysis include?

When the user needs interpretation: a viral post analysis table (≤5 items), a work type analysis table (≤5 items), and a 300–500 word summary; all must be based on the script's actual output and must not be hallucinated.

Q7: How is the "composite score index" in the table calculated?

Formula: 8 + 2 × ((weighted value/reads - 0.2) / 0.8), range 8–10; weighted value = shares×10×0.35 + wow×5×0.25 + likes×2×0.15 + reads×1×0.25. See core_workflow.md。

Troubleshooting

Q8: The script returns empty data or fails?

Confirm that REDFOX_API_KEY is valid and the date is within the 30-day window. Check the script's stderr error message, and do not use the model to fill in the ranking.

Security and licensing

Q9: How should the API Key be kept?

REDFOX_API_KEY It is read only through environment variables; do not write it into a code repository or share it publicly.

Q10: What are the boundaries for data use?

Rankings are only based on successful script output; when citing external links and titles, comply with platform and copyright norms, and do not make exaggerated promises about unverified data.

Core workflow

Complete workflowMust first read references/core_workflow.md and follow the rules, script paths, and output constraints therein; the main text below is an outline and recall-oriented description.

For output format, user intent mapping, script parameters, three-point analysis fields, and precautions, see references/core_workflow.md。

When executing tasks, you must strictly follow them, including but not limited to:

  • Must call scripts/fetch_growth_rank.py, and the model is prohibited from generating rankings on its own
  • The script stdout Markdown table must beverbatimpresented
  • The three tables and one item count and word count limits for growth interpretation are subject to the core workflow

Precautions

  • Data: The ranking is based solely on successful script output; unavailable models must not be used to hallucinate rankings, read counts, or links.
  • Output: The title column is already a clickable link; do not change it to plain text, as this would lose the jump.
  • Date: Only queries within the last 30 days are supported; in the "Latest" scenario, if there is no data for yesterday, fall back to the day before yesterday.
  • Compliance: Comply with platform and copyright regulations; do not make exaggerated or false performance promises about unverified data.