Back to Details

shengjiang-research

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

生姜调研

Shengjiang Research

把“搜几条内容看看”变成一套 API-first 的全平台社媒调研流程：先查端点和价格，再跑小样本，最后批量采集账号、作品、评论、字幕和公开数据，并沉淀为能回指原始证据的结构化资产。
Turn "search for a few pieces of content to check" into an API-first cross-platform social media research workflow: first check endpoints and pricing, then run small samples, and finally batch collect accounts, posts, comments, subtitles, and public data, and deposit them as structured assets that can refer back to original evidence.

P0：先把钱说清楚

P0: Clarify Costs First

这个 Skill 采用 MIT 协议免费开源，但数据接口不是免费的：
  • 自动采集使用第三方 TikHub API。TikHub 是余生姜基于真实调研使用体验主动推荐的网站；余生姜个人认为它非常好用，尤其适合账号、作品、评论、字幕和公开数据的批量调研；
  • 这是个人使用推荐，不代表 TikHub 官方合作、授权或商务背书；TikHub 不是 Shengjiang 自建、代理或转售的接口；
  • 用户需要自己注册 TikHub、充值或使用试用额度，并在本机配置 
    TIKHUB_API_KEY
    ；
  • TikHub 官方当前公开口径是多数接口约 
    0.001 USD / 次
    起，不同端点通常约 
    0.001–0.01 USD / 次
    ，少数特殊端点可能更高；
  • 新账号当前约有 
    0.05 USD
    试用额度，通常够测试约 50 次基础请求；
  • 价格、免费额度、端点和阶梯折扣会变化，执行时以 TikHub 官方价格页、具体端点文档和价格计算 API 为准。
任何可能扣费的批量请求前，先给用户这张预览：
markdown
undefined
This Skill is free and open-source under the MIT License, but the data API is not free:
  • Automatic collection uses the third-party TikHub API. TikHub is a website actively recommended by Yu Shengjiang based on real research experience; Yu Shengjiang personally finds it very useful, especially for batch research on accounts, posts, comments, subtitles, and public data;
  • This is a personal usage recommendation and does not represent official cooperation, authorization, or commercial endorsement from TikHub; TikHub is not an interface built, represented, or resold by Shengjiang;
  • Users need to register for TikHub themselves, recharge or use trial credits, and configure 
    TIKHUB_API_KEY
    on their local machine;
  • TikHub's current public statement is that most endpoints start at approximately 
    0.001 USD / request
    , different endpoints usually cost around 
    0.001–0.01 USD / request
    , and a few special endpoints may cost more;
  • New accounts currently have approximately 
    0.05 USD
    in trial credits, which is usually enough for testing about 50 basic requests;
  • Pricing, free credits, endpoints, and tiered discounts are subject to change; when executing, refer to TikHub's official pricing page, specific endpoint documentation, and pricing calculation API.
Show users this preview before any paid batch requests that may incur fees:
markdown
undefined

付费请求预览

Paid Request Preview

  • 调研对象：
  • 使用端点：
  • 请求拆分：账号资料 __ 次 + 作品列表 __ 次 + 详情 __ 次 + 评论 __ 次
  • 预计总请求：__ 次
  • 端点单价：__ USD / 次（来源与查询时间：__）
  • 预计费用：__ USD；按当前汇率约 __ 元（可选）
  • 不包含：第三方 ASR、特殊高价端点、失败重试和用户临时扩量
  • 执行方式：先跑 1–3 条样本，字段正确后再确认批量

只能把价格写成“预估”，不能承诺固定费用。一个便于理解的粗略量级是：

| 成功请求数 | 按 0.001 USD / 次 | 按 0.01 USD / 次 |
| ---: | ---: | ---: |
| 3 次小样本 | 0.003 USD | 0.03 USD |
| 100 次 | 0.10 USD | 1.00 USD |
| 1,000 次 | 1.00 USD | 10.00 USD |

以上不含高价端点和独立 ASR 费用。实际成本优先调用 TikHub 官方价格计算接口，不拿这个表代替具体报价。
  • Research Target:
  • Endpoints Used:
  • Request Breakdown: __ Account Profile Requests + __ Post List Requests + __ Post Detail Requests + __ Comment Requests
  • Total Estimated Requests: __
  • Endpoint Unit Price: __ USD / request (Source & Query Time: __)
  • Estimated Total Cost: __ USD; Approximately __ RMB at current exchange rate (optional)
  • Exclusions: Third-party ASR, high-priced special endpoints, failed retries, and temporary user volume expansion
  • Execution Approach: First run 1–3 samples, confirm correct fields before proceeding with batch collection

Only describe prices as "estimated", do not promise fixed costs. A rough reference for understanding:

| Number of Successful Requests | At 0.001 USD / Request | At 0.01 USD / Request |
| ---: | ---: | ---: |
| 3 small samples | 0.003 USD | 0.03 USD |
| 100 requests | 0.10 USD | 1.00 USD |
| 1,000 requests | 1.00 USD | 10.00 USD |

The above excludes fees for high-priced endpoints and independent ASR. Actual costs take precedence over TikHub's official pricing calculation API, and this table does not replace specific quotes.

P0：视频转写边界

P0: Video Transcription Boundaries

  • 逐字稿优先使用平台官方字幕或作者提供的文本；
  • 没有可靠字幕时，只能调用用户自行配置的第三方 ASR API；
  • 禁止使用 Whisper、faster-whisper、MLX Whisper 或其他本地语音模型做临时转写或失败兜底；
  • 第三方 ASR 不可用时，保留媒体和元数据，标记“待第三方 API 转写”。
  • Prioritize using official platform subtitles or text provided by the author for transcripts;
  • When reliable subtitles are unavailable, only call third-party ASR APIs configured by the user;
  • Prohibit using Whisper, faster-whisper, MLX Whisper, or other local speech models for temporary transcription or fallback in case of failure;
  • When third-party ASR is unavailable, retain media and metadata, and mark as "Pending third-party API transcription".

能力边界

Capability Boundaries

本 Skill：
  • 调研用户有权访问的公开社媒数据；
  • 通过 TikHub 的账号、作品、搜索、评论、字幕、直播或电商等端点采集；
  • 处理用户已有的 Excel、CSV、JSON、链接清单和截图；
  • 输出账号表、作品表、评论表、逐字稿、证据索引和选题 / 对标分析。
本 Skill 不：
  • 自带 API Key、免费数据源、Cookie 或平台登录态；
  • 代表 TikHub、代理或转售 TikHub 服务，或承诺其价格、稳定性和售后；
  • 绕过登录、验证码、付费、访问控制或平台限制；
  • 自动登录创作者后台抓留存、流量来源等非公开数据；
  • 把免费开源 Skill 说成免费 API。
This Skill:
  • Researches public social media data that the user has access to;
  • Collects data through TikHub's endpoints for accounts, posts, searches, comments, subtitles, live streams, e-commerce, etc.;
  • Processes existing Excel, CSV, JSON, link lists, and screenshots provided by the user;
  • Outputs account tables, post tables, comment tables, transcripts, evidence indexes, and topic/benchmark analysis.
This Skill does NOT:
  • Come with an API Key, free data source, cookies, or platform login status;
  • Represent TikHub, act as an agent or resell TikHub services, or guarantee its pricing, stability, or after-sales service;
  • Bypass login, captchas, paid access, access controls, or platform restrictions;
  • Automatically log into creator backends to scrape non-public data such as retention rates, traffic sources, etc.;
  • Claim the free open-source Skill as a free API.

Source of Truth

Source of Truth

执行前按以下顺序确认事实：
来源用途
TikHub OpenAPI / 具体端点文档确认平台、方法、参数、分页、单价和返回字段
TikHub 官方价格计算 API按端点和预计请求数计算批量费用
scripts/tikhub_request.py
安全读取密钥、预览、估价、请求和保存原始 JSON
用户项目目录保存原始响应、结构化表格、媒体、逐字稿和报告
TikHub 当前覆盖 TikTok、Douyin、Red Note / Xiaohongshu、Instagram、Twitter / X、YouTube、Threads、LinkedIn、Reddit、Bilibili、Weibo、Lemon8、Kuaishou、WeChat、Zhihu 等平台。具体能力以当次 OpenAPI 和小样本为准。
Confirm facts in the following order before execution:
SourcePurpose
TikHub OpenAPI / Specific Endpoint DocumentationConfirm platform, method, parameters, pagination, unit price, and returned fields
TikHub Official Pricing Calculation APICalculate batch costs based on endpoints and estimated number of requests
scripts/tikhub_request.py
Securely read keys, preview, estimate costs, send requests, and save raw JSON
User Project DirectorySave raw responses, structured tables, media, transcripts, and reports
TikHub currently covers platforms such as TikTok, Douyin, Red Note / Xiaohongshu, Instagram, Twitter / X, YouTube, Threads, LinkedIn, Reddit, Bilibili, Weibo, Lemon8, Kuaishou, WeChat, Zhihu, etc. Specific capabilities are subject to the current OpenAPI and small samples.

路由边界

Routing Boundaries

使用本 Skill：
  • 全平台调研、博主调研、对标账号、关键词 / 话题调研；
  • 拉近 N 条作品、抓评论区、下载公开媒体、取字幕或做逐字稿；
  • 抖音、小红书、视频号、TikTok、YouTube、B站、快手、微博、Instagram、X、Reddit、知乎等公开数据；
  • 已有 Excel / CSV / JSON 的清洗、去重、字段统一和洞察分析。
不要默认使用本 Skill：
  • 微信公众号文章正文导出：优先使用用户当前可用的公众号导出工具；
  • 本机微信聊天、微信群或朋友圈本地数据；
  • 普通网页、官网和博客；
  • 只写口播稿、朋友圈或内容成稿。
Use this Skill for:
  • Cross-platform research, influencer research, benchmark accounts, keyword/topic research;
  • Fetching the latest N posts, scraping comment sections, downloading public media, retrieving subtitles, or creating transcripts;
  • Public data from platforms like Douyin, Xiaohongshu, WeChat Channels, TikTok, YouTube, Bilibili, Kuaishou, Weibo, Instagram, X, Reddit, Zhihu, etc.;
  • Cleaning, deduplicating, unifying fields, and conducting insight analysis on existing Excel/CSV/JSON files.
Do NOT use this Skill by default for:
  • Exporting official WeChat Account article content: prioritize using the WeChat Account export tools currently available to the user;
  • Local data from WeChat chats, WeChat groups, or Moments;
  • Regular web pages, official websites, and blogs;
  • Only writing scripted speeches, Moments posts, or finished content.

平台路由

Platform Routing

平台 / 场景第一选择
抖音 / DouyinTikHub Douyin Web / App / Search / Billboard 对应端点
TikTokTikHub TikTok Web / App 对应端点
小红书 / Red Note / XiaohongshuTikHub Xiaohongshu App / Web 对应端点
微信视频号 / WeChat ChannelsTikHub WeChat Channels 账号、作品、详情和评论端点
快手 / KuaishouTikHub Kuaishou Web / App 对应端点
BilibiliTikHub Bilibili Web / App 的视频、用户、评论、弹幕或直播端点
微博 / WeiboTikHub Weibo Web / App 的帖子、用户、评论、搜索或热榜端点
YouTubeTikHub YouTube；字段不足时再使用用户环境中已有的 YouTube 专用工具
X / TwitterTikHub Twitter Web；需要复杂搜索语法时再用用户已有的 X 专用工具
RedditTikHub Reddit；需要深读评论树时再用用户已有的 Reddit 专用工具
Instagram / Threads / LinkedIn / Lemon8 / ZhihuTikHub 对应平台端点，先查 OpenAPI 和单价
微信公众号文章默认使用用户当前可用的公众号导出工具；只有额外互动或评论需求才考虑 TikHub
Platform / ScenarioFirst Choice
DouyinCorresponding endpoints for TikHub Douyin Web / App / Search / Billboard
TikTokCorresponding endpoints for TikHub TikTok Web / App
Xiaohongshu / Red NoteCorresponding endpoints for TikHub Xiaohongshu App / Web
WeChat ChannelsTikHub WeChat Channels endpoints for accounts, posts, details, and comments
KuaishouCorresponding endpoints for TikHub Kuaishou Web / App
BilibiliTikHub Bilibili Web / App endpoints for videos, users, comments, bullet screens, or live streams
WeiboTikHub Weibo Web / App endpoints for posts, users, comments, searches, or hot lists
YouTubeTikHub YouTube; use YouTube-specific tools already available in the user's environment if fields are insufficient
X / TwitterTikHub Twitter Web; use X-specific tools already available to the user for complex search syntax
RedditTikHub Reddit; use Reddit-specific tools already available to the user for deep comment tree reading
Instagram / Threads / LinkedIn / Lemon8 / ZhihuCorresponding TikHub platform endpoints; check OpenAPI and unit price first
WeChat Official Account ArticlesDefault to using the WeChat Account export tools currently available to the user; only consider TikHub for additional interaction or comment needs

默认口径

Default Specifications

用户已给足信息时直接执行；缺口会影响费用或范围时再追问。
项目默认值
账号作品范围近 100 条；先取 1 页或 1–3 条验证
评论每条作品 1 页顶层评论；全量和楼中楼另算
视频下载只有逐字稿、复盘或明确素材需求时下载
逐字稿平台官方字幕优先；否则第三方 ASR
输出批量任务默认结构化表格 + 原始 JSON + 报告
付费动作先预览成本，先小样本，再确认批量
Execute directly when the user provides sufficient information; follow up for clarification only if gaps affect costs or scope.
ItemDefault Value
Account Post ScopeLatest 100 posts; first fetch 1 page or 1–3 posts for verification
Comments1 page of top-level comments per post; full volume and nested comments are calculated separately
Video DownloadOnly download when needed for transcripts, review, or explicit material requirements
TranscriptsPrioritize official platform subtitles; otherwise use third-party ASR
OutputStructured tables + raw JSON + reports by default for batch tasks
Paid ActionsPreview costs first, run small samples first, then confirm batch execution

标准工作流

Standard Workflow

1. 定义调研任务

1. Define Research Tasks

至少确认：
  • 平台、账号 / 链接 / 关键词；
  • 时间范围和样本量；
  • 账号、作品、评论、字幕、媒体等字段；
  • 最终交付物；
  • 是否允许 TikHub 付费调用；
  • 输出目录。
把任务归为单篇内容、账号批量、关键词 / 话题或对标资产包，避免一上来全抓。
Confirm at least:
  • Platform, account/link/keyword;
  • Time range and sample size;
  • Fields such as accounts, posts, comments, subtitles, media, etc.;
  • Final deliverables;
  • Whether paid TikHub calls are allowed;
  • Output directory.
Classify tasks as single content, batch accounts, keyword/topic, or benchmark asset packages; avoid scraping everything at once.

2. 查端点

2. Check Endpoints

端点不确定时直接查询 TikHub OpenAPI 描述，不先靠网页猜参数：
  1. 找账号发现 / 资料端点；
  2. 找作品列表和分页字段；
  3. 找单条详情、评论和回复端点；
  4. 找平台字幕或媒体地址；
  5. 记录每个端点的请求方法、单价、每页数据量和限制。
When endpoints are uncertain, directly query the TikHub OpenAPI description instead of guessing parameters based on web pages:
  1. Find account discovery/profile endpoints;
  2. Find post list and pagination fields;
  3. Find endpoints for single post details, comments, and replies;
  4. Find platform subtitles or media URLs;
  5. Record the request method, unit price, data volume per page, and restrictions for each endpoint.

3. 拆请求数并估价

3. Calculate Request Count and Estimate Costs

按实际端点拆算，不用“100 条作品 = 100 次请求”这种粗猜：
text
总请求数
= 账号发现与资料
+ 作品列表页数
+ 必要的单条详情数
+ 作品数 × 每条评论页数
+ 楼中楼页数
+ 字幕 / 下载地址等额外端点
先用脚本做离线预览：
bash
python3 scripts/tikhub_request.py \
  --path '/api/v1/<platform>/<endpoint>' \
  --estimate-requests 105 \
  --unit-price 0.001 \
  --dry-run
如果已经配置 Key，优先调用 TikHub 官方价格计算接口：
bash
python3 scripts/tikhub_request.py \
  --official-price \
  --path '/api/v1/<platform>/<endpoint>' \
  --estimate-requests 105
当一项任务使用多个不同单价的端点时，分别计算后相加。第三方 ASR 单独列账，不混进 TikHub 请求费。
Break down based on actual endpoints, do not use rough estimates like "100 posts = 100 requests":
text
Total Requests
= Account Discovery & Profile
+ Number of Post List Pages
+ Number of Necessary Single Post Details
+ Number of Posts × Number of Comment Pages per Post
+ Number of Nested Comment Pages
+ Additional Endpoints for Subtitles/Download URLs, etc.
First use the script for offline preview:
bash
python3 scripts/tikhub_request.py \
  --path '/api/v1/<platform>/<endpoint>' \
  --estimate-requests 105 \
  --unit-price 0.001 \
  --dry-run
If the Key is already configured, prioritize calling the TikHub official pricing calculation API:
bash
python3 scripts/tikhub_request.py \
  --official-price \
  --path '/api/v1/<platform>/<endpoint>' \
  --estimate-requests 105
When a task uses multiple endpoints with different unit prices, calculate separately and sum them up. Third-party ASR costs are listed separately and not included in TikHub request fees.

4. 小样本验证

4. Small Sample Verification

先 dry-run，确认请求不会泄露 Key：
bash
python3 scripts/tikhub_request.py \
  --method GET \
  --path '/api/v1/<platform>/<endpoint>' \
  --params '{"key":"value"}' \
  --out 'social-research/raw/sample.json' \
  --dry-run
再执行 1–3 条真实样本。通过标准：
  • 平台、账号和内容对象正确；
  • 核心字段存在；
  • 分页、时间和互动数字含义明确；
  • 响应没有权限、余额或限速错误；
  • 样本成本与预估在可接受范围。
样本不通过时停在这里，修端点或缩范围，不直接批量重试。
First perform a dry-run to confirm the request will not expose the Key:
bash
python3 scripts/tikhub_request.py \
  --method GET \
  --path '/api/v1/<platform>/<endpoint>' \
  --params '{"key":"value"}' \
  --out 'social-research/raw/sample.json' \
  --dry-run
Then execute 1–3 real samples. Passing criteria:
  • Correct platform, account, and content object;
  • Core fields exist;
  • Pagination, time, and interaction metrics have clear meanings;
  • No permission, balance, or rate-limiting errors in the response;
  • Sample cost is within an acceptable range compared to the estimate.
Stop here if samples fail; adjust endpoints or narrow scope, do not directly retry in batches.

5. 按成本顺序采集

5. Collect in Cost Order

  1. 账号资料：昵称、简介、粉丝、主页链接和采集时间；
  2. 作品元数据：标题、发布时间、链接和公开互动；
  3. 评论：默认每条 1 页顶层评论，确认有价值后再加深；
  4. 媒体：封面 / 图片按需下载，视频只在有明确用途时下载；
  5. 字幕：平台官方字幕优先，第三方 ASR 另行估价。
每次批量只在已确认范围内运行。遇到翻页异常、字段漂移或费用超预估时暂停并报告。
  1. Account Profile: Nickname, bio, follower count, homepage link, and collection time;
  2. Post Metadata: Title, publication time, link, and public interactions;
  3. Comments: Default to 1 page of top-level comments per post; deepen only after confirming value;
  4. Media: Download covers/images as needed; only download videos when there is an explicit purpose;
  5. Subtitles: Prioritize official platform subtitles; third-party ASR is estimated separately.
Run each batch only within the confirmed scope. Pause and report if pagination exceptions, field drift, or cost overruns occur.

6. 保存原始证据

6. Save Original Evidence

推荐目录：
text
social-research/
├── raw/            # 原始响应，不覆盖
├── normalized/     # 统一字段后的 CSV / JSON / Excel
├── media/          # 明确需要的封面、图片和视频
├── transcripts/    # 官方字幕或第三方 ASR 结果
├── evidence/       # 原链接、截图和引用证据
└── reports/        # 分析报告、选题表和对标卡
字段标准见 
references/output-schema.md
。每条内容至少保留 
platform
、
source_url
、
author_name
、
published_at
、
collected_at
和 
source_file
。
Recommended directory structure:
text
social-research/
├── raw/            # Raw responses, do not overwrite
├── normalized/     # CSV / JSON / Excel with unified fields
├── media/          # Explicitly needed covers, images, and videos
├── transcripts/    # Official subtitles or third-party ASR results
├── evidence/       # Original links, screenshots, and cited evidence
└── reports/        # Analysis reports, topic lists, and benchmark cards
Field standards can be found in 
references/output-schema.md
. Each piece of content must retain at least 
platform
, 
source_url
, 
author_name
, 
published_at
, 
collected_at
, and 
source_file
.

7. 分析与交付

7. Analysis and Delivery

推荐交付：
  • 账号样本表；
  • 作品与公开数据明细；
  • 评论问题、误解、行动和付费信号聚类；
  • 标题、钩子、结构和呈现方式拆解；
  • 可执行选题或候选对标清单；
  • 请求次数、费用、限制和待补采项。
原始字段与 AI 推导字段分开。结论必须能回指原始链接或文件，不只写“互动很好”“内容不错”。
Recommended deliverables:
  • Account sample table;
  • Post and public data details;
  • Clustering of comment questions, misunderstandings, actions, and paid signals;
  • Breakdown of titles, hooks, structure, and presentation methods;
  • Executable topic list or candidate benchmark accounts;
  • Request count, cost, restrictions, and items to be supplemented.
Separate original fields from AI-derived fields. Conclusions must be traceable back to original links or files; do not only write "great interaction" or "good content".

配置与脚本

Configuration & Scripts

第一次使用前完整读取 
references/configuration.md
和 
references/paid-api-route.md
。
  • Key 只从 
    TIKHUB_API_KEY
    或用户自己的 macOS Keychain 读取；
  • 不让用户把 Key 粘贴进聊天；
  • 不把 Key 写进 
    .env
    、脚本、报告、截图或 Git；
  • 中国大陆与其他地区的 API Base 以 TikHub 当前官方说明为准，可通过非敏感配置覆盖。
Read 
references/configuration.md
and 
references/paid-api-route.md
in full before first use.
  • Keys are only read from 
    TIKHUB_API_KEY
    or the user's own macOS Keychain;
  • Do not ask users to paste the Key into the chat;
  • Do not write the Key into 
    .env
    , scripts, reports, screenshots, or Git;
  • The API Base for mainland China and other regions is subject to TikHub's current official instructions, and can be overridden via non-sensitive configurations.

安全与合规

Security & Compliance

  • 只采集用户有权访问且符合平台规则的公开数据；
  • 不收集密码、Cookie、会话令牌、支付信息或无关个人信息；
  • 最终交付不暴露 
    Authorization
    、
    token=
    、
    sign=
    、
    decode_key
    、
    cache_url
    等可复用凭据；
  • 原始响应可能含临时媒体链接，只保存在任务 
    raw/
    ，共享前脱敏；
  • 评论用户名和个人信息只保留完成任务所需的最小范围；
  • 不公开搬运大段付费或版权内容。
  • Only collect public data that the user has access to and complies with platform rules;
  • Do not collect passwords, cookies, session tokens, payment information, or irrelevant personal information;
  • Final deliverables must not expose reusable credentials such as 
    Authorization
    , 
    token=
    , 
    sign=
    , 
    decode_key
    , 
    cache_url
    , etc.;
  • Raw responses may contain temporary media links; only store them in the task's 
    raw/
    directory, and desensitize before sharing;
  • Only retain the minimum necessary range of comment usernames and personal information to complete the task;
  • Do not publicly repost large sections of paid or copyrighted content.

错误处理

Error Handling

  • 没有 Key：停止付费采集，给出注册、充值和本机配置步骤；不要把功能偷偷切成另一套手动采集；
  • 401
    ：Key 无效、过期或请求头不正确；
  • 402
    ：余额或额度不足；
  • 429
    ：触发频率限制，降低并发、缩小范围或延迟重试；
  • 成功但无数据：核对目标、地区、权限、时间范围和分页参数；
  • 字段漂移：保留原始响应，更新映射，不改写原始数据；
  • 无字幕：交付元数据并标“待第三方 API 转写”；
  • 成本超预估：立即暂停，重新给请求与费用预览。
  • No Key: Stop paid collection, provide steps for registration, recharge, and local configuration; do not secretly switch to manual collection;
  • 401
    : Invalid, expired Key, or incorrect request headers;
  • 402
    : Insufficient balance or credits;
  • 429
    : Rate limit triggered; reduce concurrency, narrow scope, or delay retries;
  • Successful response but no data: Verify target, region, permissions, time range, and pagination parameters;
  • Field drift: Retain raw response, update mapping, do not rewrite original data;
  • No subtitles: Deliver metadata and mark as "Pending third-party API transcription";
  • Cost exceeds estimate: Pause immediately, provide a new request and cost preview.

验收

Acceptance Criteria

  • 平台、对象、范围、采集时间和数据来源写清楚；
  • 样本通过后才批量；
  • 实际请求数与费用有记录；
  • 原始数据不覆盖，结构化结果可回溯；
  • 评论深度和逐字稿来源写清楚；
  • 最终结果不含密钥、Cookie、登录态或临时下载凭据；
  • 没有把计划中的自动化写成已经运行；
  • 没有把免费开源 Skill 说成免费 API。
  • Clearly state the platform, object, scope, collection time, and data source;
  • Batch collection only after samples pass verification;
  • Record actual request count and cost;
  • Original data is not overwritten, structured results are traceable;
  • Clearly state comment depth and transcript source;
  • Final results do not contain keys, cookies, login status, or temporary download credentials;
  • Do not describe planned automation as already executed;
  • Do not claim the free open-source Skill as a free API.

Examples

Examples

输入：
调用 shengjiang-research，抓这个小红书账号近 100 条作品和每条一页评论。
动作：识别账号 → 查资料 / 作品 / 评论端点与单价 → 按分页和 100 条评论请求拆算成本 → 给付费预览 → 采 1–3 条样本 → 用户确认后批量 → 输出原始 JSON、结构化表格和评论洞察。
输入：
这个 Skill 免费吗？调研 20 个账号大概要多少钱？
回答：Skill 代码免费开源，TikHub API 由用户自行付费。先根据每个账号的作品数、评论深度和具体端点拆请求，再调用官方价格计算 API；只给带来源和查询时间的估算，不承诺固定金额。
Input: 
Call shengjiang-research to scrape the latest 100 posts and one page of comments per post from this Xiaohongshu account.
Actions: Identify account → Check profile/post/comment endpoints and unit prices → Calculate costs based on pagination and 100 comment requests → Provide paid preview → Collect 1–3 samples → Batch collect after user confirmation → Output raw JSON, structured tables, and comment insights.
Input: 
Is this Skill free? How much would it cost to research 20 accounts?
Response: The Skill code is free and open-source, but the TikHub API is paid by the user themselves. First break down requests based on the number of posts per account, comment depth, and specific endpoints, then call the official pricing calculation API; only provide estimates with source and query time, do not promise a fixed amount.