Web Collection

Use this skill for browser-extension collection tasks on:

• - Douyin
• TikTok
• Xiaohongshu
• Amazon
• Bilibili

Human Tutorial

This skill is implementation-oriented. For end-user onboarding and step-by-step human instructions, use:

• - https://vcn5grhrq8y0.feishu.cn/wiki/BGUhwC0cKimwTJkXDSuc0YFBnib

When the user asks "how to use it" or needs UI-level operation guidance, prefer this tutorial and keep the response aligned with its wording.

Core Rules

1. 1. Use the user's normal Chrome environment, not the isolated openclaw browser profile.
2. Prefer the connector flow over generic browser tooling.
3. Default to synchronous closed-loop execution.
4. Do not reply before the collection script finishes.
5. Choose one execution mode first:

- local: talk to the local bridge directly - cloud: call the cloud connector dispatch API, which forwards to the user's connected local connector

1. 6. In cloud mode, do not rewrite the collection payload. Only wrap it in:

- device_id - action - INLINECODE6

First-Time Setup

This skill uses one preferences file:

INLINECODE7

Fallback:

INLINECODE8

Helper script:

CODEBLOCK0

Required defaults:

• - INLINECODE9
• INLINECODE10
• INLINECODE11
• INLINECODE12

Mode-specific defaults:

• - INLINECODE13

- no extra required key if the default local bridge URL works

• - INLINECODE14

- cloud base URL is fixed to https://i-sync.cn by default - defaultCloudDeviceId - INLINECODE17

INLINECODE18 enforces this. If these are incomplete, collection must not start.

First-run flow

On first use:

1. 1. Determine the execution mode first:

- local - cloud

1. 2. If the mode is cloud, collect these values first:

- defaultCloudDeviceId - defaultCloudToken - cloud URL is fixed and does not need user input

1. 3. Then handle the common defaults:

- 导出方式 - 默认采集条数 - 是否默认采集详情 - 默认采集速度

1. 4. Ask only one question for the common defaults:

- 推荐配置 - 自己配置

1. 5. If the user chooses 推荐配置, run:

CODEBLOCK1

1. 6. If the user chooses 自己配置, ask for all four values in one message, not one by one.
2. Only continue when check passes.

Preferred mode prompt:

CODEBLOCK2

Preferred cloud prompt:

CODEBLOCK3

Preferred quick-reply prompt for common defaults:

CODEBLOCK4

Preferred custom-config prompt:

CODEBLOCK5

Recommended defaults:

• - 运行位置：INLINECODE29
• 导出方式：INLINECODE30
• 采集条数：INLINECODE31
• 采集详情：INLINECODE32
• 采集速度：INLINECODE33

Cloud Mode

Use cloud mode when the collection request should be sent to the platform backend first, and then dispatched to the user's connected local connector.

Cloud responsibilities:

• - call INLINECODE35
• authenticate with INLINECODE36
• include INLINECODE37
• keep the collection body unchanged inside INLINECODE38
• enforce a strict cloud payload template before dispatch to avoid missing fields

- default fallback when missing: maxItems=20, mode=search, interval=300, fetchDetail=true, detailSpeed=fast

• - poll /api/v1/connector/cloud/commands/{command_id} for final status and result
• if single-command query is unavailable, fallback to INLINECODE45
• treat result + task_updates as the source of completion snapshot

Do not:

• - call the user's local 19820 port from the cloud path
• rewrite payload semantics
• mix local admin token logic into cloud requests

Connector Command Ladder

When collection fails, parameters look incomplete, or status is unclear, run connector checks in this order instead of guessing.

Layer 1: capability

• - INLINECODE50
• INLINECODE51
• INLINECODE52 (or platform/method scoped)

Layer 2: diagnostics

• - INLINECODE53
• INLINECODE54
• INLINECODE55
• INLINECODE56 with the final request body

Layer 3: execution and tracking

• - INLINECODE57
• INLINECODE58 (local mode)
• INLINECODE59 (cloud mode, preferred)
• INLINECODE60 (cloud fallback)
• INLINECODE61 or POST /api/reset when stuck

Local command template (admin token required):

CODEBLOCK6

Cloud command template (async result):

CODEBLOCK7

Export Behavior

• - INLINECODE63

- run with --export-target bitable - expect export.tableUrl on success

• - INLINECODE66

- run with --export-target csv - do not require a table link in the final reply

Entry Point

Preferred wrapper:

CODEBLOCK8

The wrapper:

• - applies stored preferences
• enforces required setup
• runs either local bridge mode or cloud dispatch mode
• prefers the connector repo's real local bridge loop when available
• falls back to the bundled local loop only if needed

Common Commands

Douyin keyword search:

CODEBLOCK9

Douyin keyword search via cloud dispatch:

CODEBLOCK10

Amazon keyword search:

CODEBLOCK11

Bilibili keyword search:

CODEBLOCK12

Platform Defaults

Wrapper defaults:

• - douyin => INLINECODE69
• INLINECODE70 => INLINECODE71
• INLINECODE72 => INLINECODE73
• INLINECODE74 => INLINECODE75
• INLINECODE76 => INLINECODE77

Supported methods:

• - douyin: videoKeyword, creatorKeyword, creatorLink, creatorVideo, videoComment, videoInfo, INLINECODE85
• INLINECODE86: keywordSearch, userVideo, tiktokComment, tiktokCreatorKeyword, INLINECODE91
• INLINECODE92: keywordSearch, creatorNote, creatorLink, creatorKeyword, noteLink, INLINECODE98
• INLINECODE99: keywordSearch, productLink, INLINECODE102
• INLINECODE103: keywordSearch, videoInfo, creatorVideo, INLINECODE107

Closed Loop

INLINECODE108 mode:

1. 1. verify INLINECODE109
2. wait for idle state
3. start INLINECODE110
4. handle TASK_RUNNING via INLINECODE112
5. poll /api/tasks/<taskId> until completed or INLINECODE115
6. if export is required, verify the expected export result

INLINECODE116 mode:

1. 1. query INLINECODE117
2. dispatch action=collect to INLINECODE119
3. keep querying command result (/api/v1/connector/cloud/commands/{command_id} preferred)
4. after each poll, refresh current collection state from command status
5. wait for completed or terminal error state
6. on completion, read result and task_updates for records/count/export snapshot and include key fields in the final reply

Quick query examples:

CODEBLOCK13

CODEBLOCK14

Final Reply

When successful:

1. 1. Mention whether the run used local or cloud mode.
2. If cloud mode was used, include the command status.
3. If export mode is bitable and export.tableUrl exists, include the table link first.
4. If export mode is csv, explicitly say export mode is CSV.
5. Then include:

- status - export status - collected count - short analysis

When bitable export is expected but no table link exists, explicitly say export did not finish correctly.

Troubleshooting

• - INLINECODE131

- Chrome/plugin is not connected to the bridge

• - bridge/status mismatch

- in local mode, ensure collect, status, and stop all use the same local base URL

• - cloud dispatch auth failed

- check defaultCloudToken

• - cloud dispatch could not reach device

- check defaultCloudDeviceId and whether the local connector is online

• - INLINECODE135

- use stop + retry, or --force-stop-before-start

• - long record output hiding key fields

- trust the connector loop's compact summary output rather than raw task JSON