tiktok-shop-operator
Skill158 starsChanged 4 months agoMITView on GitHub
Operate TikTok Shop research and planning with KSS MCP across product discovery, shop analysis, viral commerce videos, creator matching, caption extraction, pagination, sorting, and evidence-based action plans. Use when a user asks to research TikTok Shop products, shops, videos, creators, subtitles, competitors, or a complete commerce operations workflow.
In this repository5 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. About 0 are common, 20 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use KSS MCP to turn natural-language TikTok Shop research requests into verified results and actionable operating plans.
- Distinctive: line 12
Read references/mcp-tools.md before choosing tools, parameters, joins, or return fields.
- Distinctive: line 13
Read references/workflows.md for operational or multi-step tasks.
- Distinctive: line 14
Read references/output-templates.md before presenting results.
- Distinctive: line 15
Read references/examples.md only when intent, pagination, missing-data, or error behavior is unclear.
- Distinctive: line 17
Do not duplicate detailed tool schemas in this file.
- Distinctive: line 23
Ask one concise question only when a missing condition blocks a valid query.
- Distinctive: line 24
Use an MCP default only when valid, and disclose it in the query scope.
- Very specific: line 29
Use product_search for products, prices, ratings, sales, growth, shops, and product-level trend filters.
- Very specific: line 30
Use shop_search for shops, service metrics, shop ratings, product counts, and shop-level sales.
- Very specific: line 31
Use video_search for commerce videos, video sales, engagement, products, shops, and embedded creator data.
- Very specific: line 32
Use creator_search for creator discovery and creator metrics.
- Very specific: line 33
Use caption_extract for captions from a specific TikTok video URL.
- Very specific: line 35
Use IDs for joins. For video-to-creator enrichment, query by returned Handle/name with searchType=N, then confirm the returned creator ID …
- Distinctive: line 40
When the user requests “all,” paginate until there is no next page, the tool limit is reached, or quota/rate limiting stops collection.
- Distinctive: line 41
Never call the first page “all results.”
- Very specific: line 44
Do not invent an orderField value absent from the reference.
- Distinctive: line 45
Keep regions, currencies, and time windows separate.
- Very specific: line 46
Check the live tool schema or official examples before encoding a percentage growth filter.
- Distinctive: line 47
Never invent fields, results, links, quota status, or successful tool calls.
- Distinctive: line 48
Write missing fields as “未提供.”
- Very specific: line 49
Stop on 401, unavailable tools, ERROR_API_MINUTE_MAX, or ERROR_API_MONTH_MAX, and report completed versus remaining work.
- Distinctive: line 50
Do not silently broaden filters after an empty result.
- Distinctive: line 54
Never repeat, store, log, or place a user-provided MCP Key in generated files, examples, or answers.
- Distinctive: line 56
Do not purchase quota, change subscriptions, bypass limits, or weaken platform restrictions.
- Distinctive: line 57
Do not contact creators, send messages, place orders, or publish TikTok content.
- Distinctive: line 62
Start with the query scope: region, period, filters, sorting, pages, row count, and completeness.
- Very specific: line 63
Use the applicable template from references/output-templates.md.
- Distinctive: line 65
Use MCP-returned shop links directly.
- Distinctive: line 67
Do not invent product links.
- Very specific: line 77
If the KSS MCP tools are unavailable, explain that MCP must be connected or refreshed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TikTok Shop Operator
Use KSS MCP to turn natural-language TikTok Shop research requests into verified results and actionable operating plans.
Load References
- Read references/mcp-tools.md before choosing tools, parameters, joins, or return fields.
- Read references/workflows.md for operational or multi-step tasks.
- Read references/output-templates.md before presenting results.
- Read references/examples.md only when intent, pagination, missing-data, or error behavior is unclear.
Do not duplicate detailed tool schemas in this file.
Interpret the Request
- Extract region, keyword/category, price, rating, sales, revenue, growth rate, date window, requested count, and sorting.
- Preserve every explicit user condition.
- Ask one concise question only when a missing condition blocks a valid query.
- Use an MCP default only when valid, and disclose it in the query scope.
- Identify whether the task needs one tool or a cross-tool workflow.
Choose Tools
- Use
product_searchfor products, prices, ratings, sales, growth, shops, and product-level trend filters. - Use
shop_searchfor shops, service metrics, shop ratings, product counts, and shop-level sales. - Use
video_searchfor commerce videos, video sales, engagement, products, shops, and embedded creator data. - Use
creator_searchfor creator discovery and creator metrics. - Use
caption_extractfor captions from a specific TikTok video URL.
Use IDs for joins. For video-to-creator enrichment, query by returned Handle/name with searchType=N, then confirm the returned creator ID against the video creator ID when available.
Execute Safely
- Query the smallest useful scope first.
- When the user requests “all,” paginate until there is no next page, the tool limit is reached, or quota/rate limiting stops collection.
- Never call the first page “all results.”
- Deduplicate paginated objects by their stable ID.
- Apply the user's sort. If none is provided, sort the relevant returned sales amount descending.
- Do not invent an
orderFieldvalue absent from the reference. Sort locally within the disclosed collected scope when necessary. - Keep regions, currencies, and time windows separate.
- Check the live tool schema or official examples before encoding a percentage growth filter; never guess whether 50% means
50or0.5. - Never invent fields, results, links, quota status, or successful tool calls.
- Write missing fields as “未提供.”
- Stop on 401, unavailable tools,
ERROR_API_MINUTE_MAX, orERROR_API_MONTH_MAX, and report completed versus remaining work. - Do not silently broaden filters after an empty result. Suggest one relaxation and wait for approval.
Respect Action and Credential Boundaries
- Never repeat, store, log, or place a user-provided MCP Key in generated files, examples, or answers.
- Refer to credentials only as
${KSS_MCP_KEY}or a redacted value. - Do not purchase quota, change subscriptions, bypass limits, or weaken platform restrictions.
- Do not contact creators, send messages, place orders, or publish TikTok content.
- Produce research, drafts, recommendations, and action plans only. Treat any external execution as a separate user-authorized task requiring an appropriate tool.
Present Results
- Start with the query scope: region, period, filters, sorting, pages, row count, and completeness.
- Use the applicable template from
references/output-templates.md. - Mark interrupted collections as “非完整结果.”
- Use MCP-returned shop links directly.
- Construct creator or video links only when the required Handle and ID are present.
- Do not invent product links.
- Separate evidence from interpretation.
- End analytical tasks with:
- the main conclusion;
- supporting evidence;
- uncertainty and risks;
- prioritized next actions.
Handle Missing MCP
If the KSS MCP tools are unavailable, explain that MCP must be connected or refreshed. For 401, tell the user to verify the secret-key header and MCP permission. Never substitute ordinary web results and present them as KSS MCP data.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

