• /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".

⚠️ 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.

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.

1. Obtain queryable industry enumeration (only industries, no type) through "Interface 1".
2. After the user selects an industry, use the fixed

   type

   of this Skill to query the trend ranking list under the industry.
3. After the user clicks a record, get the details by unique key (optional: expand from the list context or query the details again).

$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".

• 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.

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.

--order-by

• "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

• "Ranking DESC"

  — Heat ranking (default)

• "Heat value DESC"

  — Heat value

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

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

• 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

  )

⛔ 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.

• {Guide question 1}
• {Guide question 2}
• {Guide question 3}

undefined

• {Guide question 1}
• {Guide question 2}
• {Guide question 3}

undefined

• {Guide question 1}
• {Guide question 2}
• {Guide question 3}

undefined

• {Top 3 related videos, one per line}

• {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.

💡 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"

💡 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]"

💡 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"

💡 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.

• 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.

• 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".

This Skill uses

volcenginesdkcore.ApiClient

to initiate a signature request to

cdp-saas.cn-beijing.volcengineapi.com

. Action:

ArkOpenClawSkill

, Version:

2022-08-01

.

--ak

--sk

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

  )

• Default use:

  hot_topic_insights

• Optional use:

  hot_event

• 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.