Douyin Keyword Search, Competitor Analysis & Hot List Monitoring

Core Problems Solved

In short-video operations and competitive analysis, extracting public content from Douyin—such as videos by specific keywords, a creator's recent posts, top comments on trending videos, and real-time hot lists—often faces anti-scraping restrictions, login-state dependencies, and unstructured data formats. This skill bypasses these obstacles by pulling structured public data via read-only interfaces. It converts unstructured web content into a stable JSON data source, providing a reliable foundation for AI summarization, competitor comparison, and sentiment clustering.

Core Capabilities & Workflow

Running on Node.js without heavy service deployment, the skill fetches data by calling a third-party API (requiring the GUAIKEI_API_TOKEN environment variable). Its core capabilities cover four main scenarios:
- Keyword Search: Supports sorting by comprehensive, most liked, or latest releases, with multi-dimensional filters for time, duration, and content type (video/image-text), returning up to 10,000 records per request.
- Creator Post Tracking: Batch-fetches a creator's public post list using their homepage URL or sec_uid.
- Comment Analysis: Extracts comment content, commenter info, and engagement metrics based on video/image-text URLs or aweme_id, facilitating opinion clustering.
- Real-time Hot Lists: Pulls current Douyin trending keywords, heat scores, and search volumes for hot-topic tracking.

In execution, the skill outputs pure JSON to stdout and logs/banners to stderr. This separation significantly improves the stability of result parsing for AI agents and automation scripts.

Boundaries & Considerations

• Read-only Public Data Only: It does not perform write operations like logging in, posting, liking, or commenting, nor does it fetch private/hidden data, eliminating account-ban risks.
• Third-party API Dependency: A valid GUAIKEI_API_TOKEN must be configured before execution, and data outbound and authorization scopes should be verified.
• Input Clarity: Specific keywords, video links, or creator homepage links are required before invocation. If the intent is vague (e.g., just mentioning "video"), the skill prompts for clarification to avoid blind execution.