beatra-ai/beatra-skills / skills/douyin-video-script-maker
douyin-video-script-maker
VerifiedCreate a Douyin short-video script, Douyin spoken script, or Douyin product-video script from a topic, product or service facts, audience, and creator voice. This AI Douyin script writer produces three hook options, a ready-to-film short-video script, shot-by-shot beats, natural spoken lines, subtitle cues, title ideas, hashtags, and a comment prompt for knowledge sharing, local business, product demos, reviews, unboxings, shop content, and creator series. The chosen title then becomes a matching vertical 9:16 Douyin cover with a headline-safe composition.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.6 KB |
| install-source.json | config | 39 B |
| manifest.json | config | 4.7 KB |
| references/billing-errors-and-recovery.md | markdown | 5.8 KB |
| references/installation-and-auth.md | markdown | 9.3 KB |
| references/installation-registration.md | markdown | 2.0 KB |
| references/mcp-connection.md | markdown | 3.3 KB |
| references/tasks-and-results.md | markdown | 2.2 KB |
| references/uninstall-and-disconnect.md | markdown | 2.7 KB |
| references/updates-and-security.md | markdown | 5.9 KB |
| references/workflow.md | markdown | 10.5 KB |
| scripts/authorize.py | script | 61.1 KB |
| scripts/mcp_client.py | script | 86.4 KB |
| scripts/uninstall.py | script | 12.6 KB |
references/tasks-and-results.md
View on GitHub# Tasks and results
Generation returns an asynchronous task. Keep its `task_id` and use
`beatra.tasks.get` to poll it with bounded backoff: wait 2 seconds before the
first poll, then increase the interval toward 5, 10, and at most 15 seconds.
Honor `deadline_at` when the task response provides it. Otherwise stop active
polling after 30 minutes, report the task ID and current status, and explain
that the user or a later agent session can resume polling the same task.
## Interpret state
- `queued` and `running` are nonterminal. Continue polling; do not submit a
replacement generation.
- `succeeded`, `failed`, and `canceled` are terminal. Stop polling.
- On success, present returned artifacts, resolved model, actual usage, and
billing truth. For prepaid work, report `billing.net_charged_credits`; the gross charged value
may include a supplemental actual-usage debit and the refunded value may
return an unused request-time estimate.
- For a settled video task, `usage.video_seconds` is the authoritative
billable total. When present, `usage.input_video_seconds` and
`usage.output_video_seconds` are the authoritative components of that total.
This distinction matters for reference-video generation and video editing,
where both input and output can be billable. Do not infer either component
when Beatra returns it as `null`.
- On failure, preserve the structured error and apply the recovery reference.
Use `beatra.tasks.list` to recover a lost task ID or inspect recent work from
this connection. Filter only when doing so helps identify the task.
Call `beatra.tasks.cancel` only when the user requests cancellation. Before
remote execution starts, cancellation stops the task. After remote execution
starts, Beatra returns `canceled` only when the stop is confirmed. A `409`
means the task continues: do not promise a stop or refund, do not submit a
replacement, and continue polling the same task.
Do not infer an artifact URL, completion, usage, or charged credits from
elapsed time. Return only fields present in Beatra's task response.
For MCP task reads, prefer the direct `structuredContent.usage` and
`structuredContent.billing` objects; the complete envelope remains available
under `structuredContent.task`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |