Douyin Traffic Monitor

Problem to solve

Douyin traffic changes rarely come from one cause: publishing cadence, live status, ad spend, content structure, and platform permission changes can all affect exposure and engagement in the same time window. Operators often need to answer specific questions: Is this change normal or anomalous? Does it mainly come from organic traffic, live sessions, ads, or external channels? Which metrics support the next action? Which claims still need verification because of data delay or unclear metric definitions?

How the skill works

The skill treats account data, video metrics, live data, and the observation period as inputs, then organizes output around traffic trends, anomaly alerts, source breakdowns, and action recommendations.

• Check input boundaries: Confirm data sources, time range, metric definitions, authorization scope, and whether external writes are allowed.
• Separate facts and assumptions: Keep known facts, assumptions to verify, constraints, risks, and action items distinct so speculation is not presented as conclusion.
• Build baselines: Establish hourly or daily baselines for publishing, live sessions, and paid traffic, then identify significant changes; if real-time platform access is missing, state the data delay.
• Preserve evidence: Keep source, calculation method, or reasoning for key judgments, and mark unverified items as “unverified.”
• Make actions actionable: Each recommendation should include owner, action, reason, and acceptance signal, so operations, live teams, and leads can follow up.

Boundaries and cautions

This skill is useful for structured Douyin traffic reviews, such as daily monitoring, anomaly localization, source breakdown, and cross-team alignment. It does not promise to bypass platform permissions, fill missing data, or generate performance claims without evidence. When the workflow touches sending, payment, deletion, accounts, privacy, or external writes, confirm authorization and target system state; if key facts are missing, the safer path is to list the gaps first, then provide the smallest analysis plan that can proceed safely.