Hot Topic Content Maker

The Problem: Time Pressure of Hot Topic Content

Hot topics on social media have extremely short windows of relevance. A manual workflow (monitoring, brainstorming angles, writing copy, designing covers, producing videos) often cannot keep pace, causing missed opportunities and stale content. Specific pain points include:
- Rigid Angles: Generating multiple brand-aligned entry points quickly is difficult with subjective judgment alone.
- Fragmented Process: Moving from a topic to final publishable assets (copy, cover, hashtags, short video) across multiple tools is cumbersome.
- Resource Risk: Investing design and video production resources upfront without validating the angle can lead to waste.

How It Works: Full Workflow from Hot Topic to Published Content

This skill is a structured, responsive workflow. Its core function is to rapidly associate a user-provided hot topic (or a queryable public trend list) with a specified account to generate a set of directly publishable content assets. The logic and key steps are:

1. Core Inputs and Outputs
- Mandatory Inputs: A hot topic (provided by the user or obtained via a paid query of public trend lists) and a publishing account (which defines the industry, brand, or persona).
- Default Output: Three potential angles (explaining the link between the topic and account), a cover image (featuring generated copy), a body text, and a set of topic hashtags. Together, this forms a complete, ready-to-publish post.

2. Key Workflow and Capabilities
- Angle Discovery (Find Entry Angles): This is the first step. The skill analyzes the topic and generates three angles tied to the account. It explicitly flags high-risk angles and explains the risk.
- Content Plan Construction (Build This Content): After an angle is chosen, the skill outlines the cover copy, body text, and hashtags. If a short video is required, it also includes a storyboard (with on-screen text and voiceover script separated).
- Media Generation & Confirmation:
- Generates the cover image and (optionally) storyboard stills.
- Synthesizes voiceover audio.
- Critical Checkpoint: Before calling paid APIs like beatra.images.generate or beatra.speech.synthesize, it freezes the plan and displays a cost estimate, proceeding only after user confirmation.
- Optional Short Video Production: Defaults to 12 seconds, animated from an opening scene. Requires explicit selection of a video model, as some models discard external voiceover. Before calling beatra.videos.animate, it confirms costs again and prompts for balance top-up.
- Task Delivery & Review: Polls all tasks using beatra.tasks.get to deliver final assets (images, audio, video) with their IDs, links, specifications, and credits consumed. It strictly verifies that generated content matches the approved copy.

3. Operational Constraints
- Speed-First: Provides angles in the first response without pre-emptive questioning.
- Cost Control: All paid operations (queries, media generation, video production) require explicit prior confirmation and record a client_request_id.
- Honest Data: Topic heat and trends are inferences; supporting evidence is provided. Factual details (e.g., numbers, outcomes) rely on user input and are not fabricated.

Boundaries and Key Considerations

• Applicable Scenario: When you already have a hot topic, event node, or calendar date and need to quickly produce one publishable piece of content. It takes precedence over workflows requiring long-term planning (e.g., evergreen product seeding, video replication).
• Inapplicable Scenario: If there is no specific hot topic, this workflow is unsuitable; use dedicated topic-finding or creative workflows instead.
• Platform Limits: Can query trend lists and search content on Douyin, TikTok, and X (paid). Xiaohongshu requires a pre-existing topic for searches. Instagram, YouTube, and WeChat Channels have no trend list features; topics must be user-provided.
• Recovery & Error Handling: If a task ID is lost, recovery involves listing tasks and matching them against local logs. For insufficient_balance errors, the message is relayed verbatim, and retries occur only after the user confirms top-up.
• Update Mechanism: The bundled client silently checks for updates (up to once per 24 hours), but update failures do not block the current task and do not justify retrying a paid generation.