tiktok-shop-growth-research
Installation
SKILL.md
TikTok Shop Growth Research
Turn a seller's decision into a bounded recommendation by combining data-search and caption tools exposed through one active connection with the compatible KOLSprite tool contract. Use MCP automatically; do not ask whether to use it.
Compatible MCP routing
- Prefer the SellerSpace Yunya unified MCP when it is available and authenticated.
- Support direct business tools plus current and legacy Yunya facade entrypoints.
- In direct mode, resolve each required research tool by its semantic business name.
- In Yunya facade mode, when a required business tool is not visible at the host's top level, make at most one host-level discovery attempt and prefer the product-specific
yunya_search_kolsprite_tools. Query the smallest tool set needed for the selected workflow; use the exact internal tool names and complete input schemas returned, then invoke them throughcall_read_tool. - If the product-specific entrypoint is unavailable but the legacy generic
yunya__search_toolsis discoverable, use it with providerkolsprite, operationread, and the same query. Do not prefer the generic entrypoint when the product-specific one is available. - Do not guess a facade namespace, internal tool name, wrapper, category value, or arguments. Reuse discovered names, schemas, IDs, and evidence throughout the run.
- A host-level miss for a business tool does not prove internal absence. Only report a missing business dependency after direct exposure and the available current or legacy facade lookup fail. If neither facade entrypoint can be discovered, report a connector-discovery failure and continue only with evidence that supports a clearly bounded partial answer, not an unrelated substitute.
- A standalone KOLSprite MCP remains compatible only when it exposes the same required semantic tool names, input schemas, and response shapes.
- If both connections are enabled, use Yunya for all MCP evidence in the run and never duplicate a paid call across both services.
- If a required tool is absent or schema-incompatible, report the dependency gap and continue only when the remaining evidence supports a clearly bounded partial answer.