Trending List (TrendingList)

When to Use

```
/trending
```
— Manually trigger full trending list query
Users ask about "hot topics/topic challenges/hot list events/industry trends/public domain insights"
Users want to know "what are the recent hot spots/industry hot searches/popular topic challenges"
Users say "help me check the hot list/what events are trending recently/what are the trends"
Called by other orchestration skills (such as daily report generation, content planning)
Scheduled tasks automatically execute to get the latest trend data

⛔ OUTPUT RULE — Highest Priority
Do not output any intermediate processes to users during execution, including but not limited to technical steps such as self-check, virtual environment creation, dependency installation, connectivity verification, etc.
It is forbidden to output any of the following content (violation means failure):
❌ "Let me do a self-check first" / "Creating virtual environment" / "Installing dependencies" / "Installation is still in progress"

❌ "Let me check the skill file first" / "First prepare the environment"

❌ Interface addresses, credentials, tokens, script paths, internal field names, SDK version information
❌ Database table names (such as
cdp_voc.hot_topic_insights
), English field names (such as
main_challenge
,
heat_value
), query_type values (such as
hot_topic_insights
,
hot_event
) — no matter in process or result, it is strictly forbidden to disclose to users
If the environment is not ready and needs to be installed, only one user-friendly prompt is allowed (such as "Initializing the query service for you, please wait…"), and the business result will be returned directly after completion, without broadcasting technical details.

Only output once after completion: business results (industry list / ranking list / single detail) or "No data available / missing parameters need to be selected".

Self-check and Environment Preparation (Must be completed before each execution)

⚠️ Mandatory Rules
All script calls must use the Python of the virtual environment:
$VENV_PY
When using for the first time or self-check fails, you must first complete the "Install Virtual Environment" step below, and then re-pass the self-check before executing business calls.
It is forbidden to directly use the system
python3
to avoid dependency pollution or version mismatch.

0. Credential Detection (Check first before environment preparation)

bash

if [ -z "$VOLCENGINE_ACCESS_KEY" ] || [ -z "$VOLCENGINE_SECRET_KEY" ]; then
  echo "CREDENTIALS_MISSING"
else
  echo "VOLCENGINE_ACCESS_KEY: 已设置"
fi

If the output is
```
CREDENTIALS_MISSING
```
: You must ask the user for credentials, output:
🔑 Volcano Engine access credentials need to be configured, please provide:
- AccessKey（AK）：
- SecretKey（SK）：
After the user provides, store them in the shell variables
```
VOLC_AK_INPUT
```
/
```
VOLC_SK_INPUT
```
, and append
```
--ak "$VOLC_AK_INPUT" --sk "$VOLC_SK_INPUT"
```
to all subsequent commands.
If the credentials already exist (
```
VOLCENGINE_ACCESS_KEY
```
/
```
VOLCENGINE_SECRET_KEY
```
are already set), no need to ask, directly enter the self-check.

A. Offline Self-check (No network access, run before each execution)

bash

SCRIPTS_DIR=$(dirname "$(find ~ -maxdepth 8 -name "openapi_client.py" -path "*byted-marketing-agent-trending-list*" 2>/dev/null | head -1)")
SKILL_DIR=$(dirname "$SCRIPTS_DIR")
VENV_PY=$SKILL_DIR/venv/bin/python3

# 1) Check if the virtual environment exists
test -f $VENV_PY && echo "venv OK" || echo "venv 不存在，请先执行安装步骤"

# 2) Check if dependencies are available
$VENV_PY -c "import volcenginesdkcore; from volcenginesdkcore import ApiClient; print('deps OK')"

# 3) Check volcengine-python-sdk version (must be >= 4.0.43)
$VENV_PY -c "from importlib.metadata import version; print(version('volcengine-python-sdk'))"

# 4) Syntax check
$VENV_PY -m py_compile $SCRIPTS_DIR/openapi_client.py && echo "syntax OK"

After all self-checks pass (no errors), you can execute subsequent business calls.

Install Virtual Environment (Execute when self-check fails)

bash

SCRIPTS_DIR=$(dirname "$(find ~ -maxdepth 8 -name "openapi_client.py" -path "*byted-marketing-agent-trending-list*" 2>/dev/null | head -1)")
SKILL_DIR=$(dirname "$SCRIPTS_DIR")

# 1. Create virtual environment (only for the first time)
python3 -m venv $SKILL_DIR/venv

# 2. Install dependencies
$SKILL_DIR/venv/bin/pip install 'volcengine-python-sdk>=4.0.43'

Known defect reminder: The built-in retry mechanism of volcengine-python-sdk historical versions 4.0.1 ~ 4.0.42 (inclusive) has defects, it is strongly recommended to use >=4.0.43.

If the system lacks
python3-venv
:
apt update && apt install python3-venv -y
, then re-execute the above steps.

B. Online Self-check (After self-check A passes, verify interface connectivity)

bash

SCRIPTS_DIR=$(dirname "$(find ~ -maxdepth 8 -name "openapi_client.py" -path "*byted-marketing-agent-trending-list*" 2>/dev/null | head -1)")
SKILL_DIR=$(dirname "$SCRIPTS_DIR")
VENV_PY=$SKILL_DIR/venv/bin/python3

# If the user provides credentials, append --ak / --sk; otherwise omit
$VENV_PY $SCRIPTS_DIR/openapi_client.py --format text \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  list-industries

If you need to further verify the list query:

bash

$VENV_PY $SCRIPTS_DIR/openapi_client.py --format text \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  query \
  --category "{Select one from industry enumeration}" \
  --query-type hot_topic_insights \
  --task-date "2026-03-12" \
  --page 1 \
  --page-size 5

If you need to verify hot events (hot_event):

bash

$VENV_PY $SCRIPTS_DIR/openapi_client.py --format text \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  query \
  --category "{Select one from industry enumeration}" \
  --query-type hot_event \
  --task-date "2026-03-12" \
  --page 1 \
  --page-size 5

Objectives

Provide users with "trending list" capabilities:

Obtain queryable industry enumeration (only industries, no type) through "Interface 1".
After the user selects an industry, use the fixed
```
type
```
of this Skill to query the trend ranking list under the industry.
After the user clicks a record, get the details by unique key (optional: expand from the list context or query the details again).

Interaction Logic (Mandatory)

When this Skill is triggered: You must actively call Interface 1 to get the latest industry enumeration first (regardless of whether the user has provided the industry).

Step 1: Industry Enumeration (Shared Interface 1)

bash

$VENV_PY \
  $SCRIPTS_DIR/openapi_client.py \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  --format text list-industries

If the user does not specify an industry, display the industry list for the user to choose.
If the user has specified an industry, you can still refresh the industry list for verification/error correction when necessary, and enter Step 2 after confirming that the industry is valid.
Regardless of whether the user specifies query_type,
hot_topic_insights
(topic trend list) is queried by default; only query
```
hot_event
```
when the user explicitly says "event/hot list event".

Step 2: Query by Industry

The
```
type
```
of this Skill is fixed as
```
trending_list
```
(do not expose/ask the user about type).
Default query_type is
hot_topic_insights
, no need to ask the user; switch to
```
hot_event
```
when the user says "event/hot list event".
Support pagination and optional filter (filter is only a reserved advanced capability, not used by default).
Default sorting: Topic trend list sorted by
```
Total plays DESC
```
, hot list events sorted by
```
Ranking DESC
```
; users can specify other fields.

bash

YESTERDAY=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d)
$VENV_PY \
  $SCRIPTS_DIR/openapi_client.py --format json \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  query \
  --category "{industry_name}" \
  --query-type {hot_topic_insights|hot_event} \
  --task-date "$YESTERDAY" \
  --order-by "{Total plays DESC | Ranking DESC}" \
  --page 1 \
  --page-size 20

Always use
--format json
, the script returns complete fields, and you are responsible for formatting and displaying.

When the user requires sorting by other dimensions, replace the value of

--order-by

Sortable fields for topic trend list:

```
"Total plays DESC"
```
— Total plays (default)
```
"Total likes DESC"
```
— Total likes
```
"Total comments DESC"
```
— Total comments
```
"Total shares DESC"
```
— Total shares
```
"Number of related videos DESC"
```
— Number of related videos

Sortable fields for hot list events:

```
"Ranking DESC"
```
— Heat ranking (default)
```
"Heat value DESC"
```
— Heat value

After returning the list result each time, actively inform the user which fields can be sorted by, example guide:

💡 Currently sorted by total plays, you can also ask me to sort by "likes", "comments", "shares", "number of related videos".

Step 3: Detail Expansion (Optional)

bash

YESTERDAY=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d)
$VENV_PY \
  $SCRIPTS_DIR/openapi_client.py --format json \
  ${VOLC_AK_INPUT:+--ak "$VOLC_AK_INPUT"} ${VOLC_SK_INPUT:+--sk "$VOLC_SK_INPUT"} \
  query \
  --category "{industry_name}" \
  --query-type {hot_topic_insights|hot_event} \
  --task-date "$YESTERDAY" \
  --filter "{Filter expression}" \
  --page 1 \
  --page-size 1

Example:

Topic trend list details:
```
--filter "Task ID = '{Task ID value}'"
```

Hot list event details:

--filter "Event name = 'Discussion on anti-peep screen and imaging functions of Samsung S26 Ultra'"

(or use

Ranking = 1

)

Data Field Description

Each record returned by the interface has slightly different fields for different list types, all are passed through without cropping:

A. Topic Trend List

Field Name	Description
Main topic	Main challenge content in hot topics
Related challenge 1 ~ Related challenge 5	1st to 5th related challenges
Proportion 1 ~ Proportion 5	Proportion of corresponding related challenges
Is official	Whether it is an official hot spot (0=unofficial, 1=official)
Is commercial	Whether it is commercial related (0=non-commercial, 1=commercial)
Related video titles	List of video titles related to the topic
Number of related videos	Number of videos related to the topic
Total plays	Total plays of the topic
Total likes	Total likes of the topic
Total comments	Total comments of the topic
Total shares	Total shares of the topic
Total follows	Total follows of the topic
Total favorites	Total favorites of the topic
Total complete plays	Total complete plays of the topic
Topic description	Topic description information
Generation date	Task run end date
Task name / Task date / Task ID	Task meta information

B. Hot List Events

Field Name	Description
Event name	Event name
Summary	One-sentence background/opinion summary
Related videos	List of related video titles (text)
Link	Search/aggregation page link
Heat value	Heat value
Ranking	Heat ranking
Speech text	Speech to text (if any)
Analysis content	Structured analysis (if any)
Generation date	Generation date
Task name / Task date	Task meta information

Display Specification

⛔ It is forbidden to add any content outside the structure specified in the template below, including introduction, summary, personal analysis or additional instructions. It is forbidden to paste raw JSON directly.

hot_topic_insights list view (fixed template)

## 🔥 {Industry} Hot Topic List ({task_date}) | Sorted by {Chinese name of sort field}

| # | Main Topic | Plays | Likes | Number of related videos |
|---|--------|--------|------|-----------|
| 1 | {Main topic} | {Total plays} ten thousand | {Total likes} ten thousand | {Number of related videos} |
...

💡 You can continue to ask me:
- {Guide question 1}
- {Guide question 2}
- {Guide question 3}

hot_topic_insights detail view (fixed template)

### 🔍 {Main topic}

{Topic description}

**Related challenge distribution:**
| Related challenge | Proportion |
|----------|------|
| {Related challenge 1} | {Proportion 1}% |
| {Related challenge 2} | {Proportion 2}% |
... (Only show non-empty items)

**Data:** Plays {Total plays} ten thousand · Likes {Total likes} ten thousand · Comments {Total comments} ten thousand · Related videos {Number of related videos} items

💡 You can continue to ask me:
- {Guide question 1}
- {Guide question 2}
- {Guide question 3}

hot_event list view (fixed template)

## 📰 {Industry} Hot List Events ({task_date})

| Ranking | Event | Summary | Heat value | Link |
|------|------|------|--------|------|
| {Ranking} | {Event name} | {Summary} | {Heat value} | [View](url) |
...

💡 You can continue to ask me:
- {Guide question 1}
- {Guide question 2}
- {Guide question 3}

hot_event detail view (fixed template)

### 🔍 {Event name}

**Summary:** {Summary}

**Related videos (Top3):**
- {Top 3 related videos, one per line}

**Analysis:** {Analysis content}

Heat value {Heat value} · Ranking {Ranking}　[View aggregation page](url)

💡 You can continue to ask me:
- {Guide question 1}
- {Guide question 2}
- {Guide question 3}

Numerical rules: Keep 1 decimal place, display the original value if less than 10,000; display "—" when

url

is empty.

Guided Question Specification (Must be executed after each return of results)

After outputting business results each time, you must attach 2 to 3 guiding questions at the end to help users explore in depth. The guiding questions should bring in the current context (industry name, date, title), so that users can reply directly to continue.

After returning the industry list

💡 You can continue to ask me:

"Help me check the trend videos of [a certain industry]" (fill in the industry name, the user can confirm directly)

"I want to see what hot events are there recently"

After returning the topic trend list (hot_topic_insights)

💡 You can continue to ask me:

"Help me expand the detailed content of {No.1 main challenge}"

"What hot list events are there recently in {Current industry}?" (Automatically switch to hot_event)

"Change to another industry, such as [Recommend another industry]"

After returning the hot list events (hot_event)

💡 You can continue to ask me:

"Expand the detailed content of {No.1 event name}"

"What hot topic challenges are there recently in {Current industry}?" (Automatically switch to hot_topic_insights)

"Change to another industry to view hot list events"

After returning a single detail

💡 You can continue to ask me:

"Look at the next item in the list"

"What hot list events are there in {Current industry}?" Or "What hot topics are there in {Current industry}?" (Guide to view another type)

"Change to another industry to check"

Principle: Drain traffic between the two types — after reading the topic trend, guide to view the hot list events, after reading the events, guide to view the related topic challenges, forming a complete content exploration closed loop.

Parameter Rules

```
industry_name
```
: Must come from the industry enumeration returned by Interface 1 (or consistent with it).
```
type
```
: Forbidden to be issued from Interface 1; fixed as
```
trending_list
```
internally by this Skill.
```
query_type
```
: Support
```
hot_topic_insights
```
/
```
hot_event
```
.

task_date

: Default to T-1 (yesterday), that is

$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d)

; subject to the user's specified date.

Error Handling

Interface call failed: Only output a short failure reason to the user (do not include URL/Token/script name/stack).
Industry missing: Output industry candidate list (appropriately truncated) for users to choose.
No data: Output "There is no trending list data available for this industry currently".
Industry/type not supported: If the service returns "unknown task/not supported", output "This industry does not support this list type (hot_event/hot_topic_insights) currently".

Credential Description (For execution use only, forbidden to echo to users)

Volcengine SDK Authentication (Required for interface calls)

This Skill uses
volcenginesdkcore.ApiClient
to initiate a signature request to
cdp-saas.cn-beijing.volcengineapi.com
. Action:
ArkOpenClawSkill
, Version:
2022-08-01
.

Credentials are only obtained through user input, priority:

--ak

--sk

parameters > environment variables

VOLCENGINE_ACCESS_KEY

VOLCENGINE_SECRET_KEY

```
VOLCENGINE_ACCESS_KEY
```
: AccessKey
```
VOLCENGINE_SECRET_KEY
```
: SecretKey
```
VOLC_SERVICE
```
: Override Service name (optional, default
```
cdp_saas
```
)
```
VOLCENGINE_REGION
```
: Override Region (optional, default
```
cn-beijing
```
)

query_type of this Skill

Default use:
```
hot_topic_insights
```
Optional use:
```
hot_event
```

Optional Override

```
PUBLIC_INSIGHT_API_URL
```
: Override the default access point (for internal debugging only)

Security requirement: It is forbidden to hardcode plaintext AK/SK in
SKILL.md
or code.

byted-marketing-agent-trending-list

NPX Install

Tags

SKILL.md Content (Chinese)

Trending List (TrendingList)

When to Use

Self-check and Environment Preparation (Must be completed before each execution)

0. Credential Detection (Check first before environment preparation)

A. Offline Self-check (No network access, run before each execution)

Install Virtual Environment (Execute when self-check fails)

B. Online Self-check (After self-check A passes, verify interface connectivity)

Objectives

Interaction Logic (Mandatory)

Step 1: Industry Enumeration (Shared Interface 1)

Step 2: Query by Industry

Step 3: Detail Expansion (Optional)

Data Field Description

A. Topic Trend List

B. Hot List Events

Display Specification

hot_topic_insights list view (fixed template)

hot_topic_insights detail view (fixed template)

hot_event list view (fixed template)

hot_event detail view (fixed template)

Guided Question Specification (Must be executed after each return of results)

After returning the industry list

After returning the topic trend list (hot_topic_insights)

After returning the hot list events (hot_event)

After returning a single detail

Parameter Rules

Error Handling

Credential Description (For execution use only, forbidden to echo to users)

Volcengine SDK Authentication (Required for interface calls)

query_type of this Skill

Optional Override