Skip to content

beatra-ai/beatra-skills / skills/douyin-video-script-maker

douyin-video-script-maker

Verified

Create 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.

references/mcp-connection.md

View on GitHub
# MCP connection

All Beatra Skill packages use one connection path:

```text
scripts/mcp_client.py -> https://mcp.beatra.ai/mcp
```

The host follows this computer's network route, described below.

They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
package directory.

The bundled client performs MCP `initialize`, retains `MCP-Session-Id` when the
server returns one, sends `notifications/initialized`, and then uses
`tools/list` or `tools/call`. Its `verify` command runs the non-billable
`beatra.tasks.list` operation. It supplies the private `Authorization: Bearer`
header on every request without exposing its value.

Source attribution: every `tools/call` may carry two optional string
arguments, `source_package_slug` (this package's slug) and `source_platform`
(the agent environment, for example `claude-code` or `codex`). The bundled
client adds them automatically. They are telemetry only: missing values never
block a call, and the server treats them as `unknown`.

## Network route

Beatra serves two networks: the international hosts, and the mainland China
hosts `mcp.beatra.cn`, `api.beatra.cn`, `www.beatra.cn`, `cdn.beatra.cn` and
`console.beatra.cn`. The saved credential works on both. Packages of the
mainland China (`cn`) channel always use the mainland hosts and cannot change
network (`network` shows `"policy":"cn"`). Other packages choose once a day,
before their first command: the client asks Beatra which network suits this computer,
in a small request that carries no credential and no installation identity,
and records the answer in `~/.beatra/network.json`. Approval pages, console and
top-up links, uploads, and result downloads then follow the chosen network.

```text
python3 scripts/mcp_client.py network
python3 scripts/mcp_client.py network --use auto
```

`network` shows the current choice. Only when the user asks for a specific
network, run `network --use cn` (mainland China) or `network --use ai`
(international): it first checks that Beatra answers on that network and
refuses otherwise; packages of the `cn` channel refuse `--use`. If commands start failing to connect after a network was
chosen this way, run `network --use auto`. A request that failed is never
resent on the other network; the next command decides again unless a network was chosen with
`network --use`. A chosen network also keeps the version-list check on it.

On the mainland China network the approval page offers WeChat, phone and email
sign-in. If the user cannot find their sign-in method, or wants to sign in with
Google, run `python3 scripts/authorize.py --approval-link ai`: it shows the same
approval on Beatra's international site, and the network does not change;
`--approval-link auto` goes back. When you give the user a console or top-up
link on the mainland network, remind them to sign in the way they did before
(phone, email, or the same WeChat): scanning with a different WeChat creates a
separate account. If credits do not appear after a top-up, first check that
they signed in to the same account.
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall