Skip to content
Back to skills

Tiktok Hashtag To Hook Clip

ASecurity

Turn a TikTok hashtag trend into one talking hook clip per still. This TikTok hashtag hook studio reads public hashtag rankings and top posts, then records each already-written hook as a 2 to 15 second talking clip. Each hashtag hook clip is a separate short video the creator can post on its own.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentspythonbashapi

Works with

  • terminal
  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 14 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add beatra-ai/beatra-skills --skill tiktok-hashtag-to-hook-clip --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tiktok Hashtag To Hook Clip?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tiktok Hashtag To Hook Clip
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/beatra-ai-tiktok-hashtag-to-hook-clip/badge)](https://www.skillsdirectory.com/skills/beatra-ai-tiktok-hashtag-to-hook-clip)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "tiktok-hashtag-to-hook-clip"
description: "Turn a TikTok hashtag trend into one talking hook clip per still. This TikTok hashtag hook studio reads public hashtag rankings and top posts, then records each already-written hook as a 2 to 15 second talking clip. Each hashtag hook clip is a separate short video the creator can post on its own."
---

# TikTok Hashtag Hook Clips

Turn a TikTok hashtag trend into one talking hook clip per still.
Deliver 2 to 8 clips. Do not stitch them.

## Scope and adjacent routes

Use this Skill when an operator wants short talking clips that open
on a public TikTok hashtag from presenter or product stills they
already have.

Route a full same-day post with cover and caption to
`hot-topic-content-maker`. Route Douyin hot-search hooks to
`douyin-hot-to-hook-clip`. Route a generic talking teaser that is
not answering a hashtag to `talking-avatar-video` or
`creator-drop-talking`.

This package reads TikTok hashtag rankings and head posts and
makes talking clips. It does not post on TikTok. If this connection
has no TikTok hashtag or video-search operation, work from pasted
tags only.

## Collect the tags

Hard inputs are:

- either permission to read the current public TikTok hashtag
  board, or the original hashtag lines already copied;
- confirmed brand or product facts the operator already wrote (what
  the hook may say, what the still actually shows);
- at least one accessible still the host Agent can inspect — a
  presenter portrait or a product photo that will be the first frame;
- likeness and voice rights when a face or a cloned voice will appear;
- how many clips the pack should contain, or permission to use the
  default of 3.

Reuse already-known language, SKU names, and a frozen `voice_id`.
Ask only for a missing hard input. A count outside 2 to 8 is still
doable: confirm that pack size and its live cost.

Do not invent a hashtag, rank, heat score, price, or offer. File
access is not consent.

Inspect every still. Record MIME type, width, height, aspect ratio,
byte size, and whether it has an alpha channel. For a local file,
upload only through the bundled client after inspection
(`scripts/mcp_client.py` / `beatra.assets.upload`). Keep the returned
artifact id. Never pass a local path to `beatra.voices.clone`,
`beatra.speech.synthesize`, or `beatra.videos.animate`.

## Plan the free slot list

Write a labeled tag-to-hook list before any paid lookup, clone,
speech, or video. Default three slots unless the operator names
another count in 2 to 8. Each slot records the original hashtag
wording, the speakable hook from confirmed facts, the still,
intended length as a 2–15s clip, and whether it uses a catalog
voice, an approved track, or a clone.

That list is the free visible result from whatever the operator
already pasted. Planning is not approval.

Safe defaults:

- one `beatra.videos.animate` call per still;
- `model: "auto"` unless the operator chose a live SKU;
- the still as the strict first frame;
- source-derived aspect ratio;
- audio-led duration inside 2–15s. Do not stitch.

## Look up the hashtag board on its own card

A request to “see what’s trending” does not authorize a lookup.
When the operator wants this connection to read public TikTok
hashtag rankings or head posts, follow
[hashtag lookup](references/hashtag-lookup.md): search, inspect,
then show a six-field lookup card and wait:

1. Work — one public TikTok hashtag-trend page or video-search page
   (`beatra.social.execute` with the inspected `operation_key`).
2. Credits — the live price `beatra.social.tools.get` just returned.
   Quote that live number, not a remembered one.
3. Count — one prepaid lookup. A hashtag-trend page is its own
   billed execute. A video search for head posts is another. The
   next page is another charge.
4. Identity — one new opaque `client_request_id` per execute.
5. If we stop here — the pasted-tag plan remains usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do
   not retry until the operator says they have topped up.

Do not show `schema_hash` to the operator. A confirmed lookup does
not authorize clone, speech, or video. After a terminal lookup,
report the payload, task ID, terminal status, and
`billing.net_charged_credits`. A lookup has no model, dimensions, or
duration to report.

## Confirm clone, speech, then video

Clone, speech, and video are separate paid stages. Each stage gets
its own six-field card and its own opaque `client_request_id` per
slot.

If the operator wants a cloned voice, inspect an authorized sample,
read the live `voice_clone` card, and wait on the clone card before
`beatra.voices.clone`. A found file is not clone consent. Show the
clone card and wait:

1. Work — one authorized voice sample (`beatra.voices.clone`).
2. Credits — the live `voice_clone` price just read. Do not reuse a
   remembered number.
3. Count — one paid clone call for this sample.
4. Identity — one new opaque `client_request_id`.
5. If we stop here — the labeled slot list remains usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do
   not retry until the operator says they have topped up.

Before speech, call `beatra.models.list` for `text_to_speech`:

```json
{"capability": "text_to_speech"}
```

Use `beatra.voices.list` when a catalog voice still needs a choice.
Show the speech card and wait:

1. Work — one spoken hook per named slot
   (`beatra.speech.synthesize`).
2. Credits — the live `text_to_speech` price just read, times the
   slot count. Do not reuse a remembered number.
3. Count — one paid speech call per slot.
4. Identity — one new opaque `client_request_id` per slot.
5. If we stop here — the labeled slot list remains usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do
   not retry until the operator says they have topped up.

Submit each speech slot once through bundled `scripts/mcp_client.py`
with `input`, not `text`. Use `format: "mp3"` and `speed: 1.0`. Use
`model: "auto"` only when every live speech card supports the
language. Poll `beatra.tasks.get`. Read actual audio MIME, duration,
and size, and `billing.net_charged_credits`. A script preview is
not the audio review.

Before video, call `beatra.models.list` for `image_to_video`:

```json
{"capability": "image_to_video"}
```

Confirm a current card admits `[image, driving_audio]`. Compare every
image fact and the real audio MIME, duration, and size with advertised
limits. Live driving-audio clips are 2–15s. If speech is longer than
the longest containable clip, split into sequential containable
segments; each segment is new speech and new video, each with a new
ID. Do not stitch the segments into one file. Approved narration does
not authorize video. The 600-credit signup gift usually cannot start
this video. Show the video card and wait:

1. Work — one talking hook clip per named still
   (`beatra.videos.animate`).
2. Credits — the live `image_to_video` price just read, times the
   segment count. Do not reuse a remembered number.
3. Count — one paid video call per approved audio segment.
4. Identity — one new opaque `client_request_id` per segment.
5. If we stop here — the slot list and approved narration remain
   usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do
   not retry until the operator says they have topped up.

Then submit `beatra.videos.animate` once per approved segment with
`driving_audio` attached.

## Review, deliver, and recover

Review that each clip names the picked hashtag and that the still is
the first frame. Report only what the host can actually see and hear.
Do not promise perfect lip sync. Never invent a stitch, concat, or
editor tool. After each terminal paid task, deliver actual bytes plus
MIME, duration, and size when present, and
`billing.net_charged_credits`. Do not promise the prepaid estimate is
the final charge.

After a returned `task_id`, poll that task. If the create response is
lost, search with `beatra.tasks.list` and verify with
`beatra.tasks.get` before replay. Reuse an ID only with
byte-identical arguments. A changed still, line, voice, or duration
is a new card and a new ID. Cancel only when the operator asks.

## Execution

Invoke every remote Beatra operation only through this package's bundled
`scripts/mcp_client.py`. Put the MCP tool name after `call` and send one
JSON object on standard input.

```bash
python3 scripts/mcp_client.py call beatra.models.list
```

```json
{"capability": "text_to_speech"}
```

```bash
python3 scripts/mcp_client.py call beatra.models.list
```

```json
{"capability": "image_to_video"}
```

```text
printf '%s' '{"query":"hashtag","platform":"tiktok","capability_family":"trends"}' | python3 scripts/mcp_client.py call beatra.social.tools.search
```

```text
printf '%s' '{"input":"Open on the approved hashtag hook. Keep the operator-supplied line.","voice":"voice-ready-01","format":"mp3","speed":1.0,"model":"auto","client_request_id":"opaque-hook-speech-01"}' | python3 scripts/mcp_client.py call beatra.speech.synthesize
```

```text
printf '%s' '{"image":{"type":"artifact","artifact_id":"art-hook-01"},"driving_audio":{"type":"artifact","artifact_id":"art-speech-01"},"prompt":"A restrained talking hook with steady eye line and a stable camera.","duration":8,"client_request_id":"opaque-hook-video-01"}' | python3 scripts/mcp_client.py call beatra.videos.animate
```

Do not configure or call a host Beatra Connector, and do not use
REST/OpenAPI as a fallback.

## Account balance

When the user asks how many credits remain or whether a live estimate fits,
call `beatra.wallet.get`. When they ask what was charged, call
`beatra.wallet.ledger`. Both are read-only. Do not invent an account-balance or
top-up tool. Do not make `wallet.get` a required step before every paid submit.

When a model card comes back carrying a `top_up` block, relay its tiers as the
card lists them and in that order. Do not rank them, do not talk one down, and
do not pick one for the user. Which tier suits them is their call, made on
the wallet page with the whole list in front of them. Never quote a tier from
memory.

## References by task

- For slot lists, lookup, payloads, and recovery, read
  [hashtag hook workflow](references/workflow.md) and
  [hashtag lookup](references/hashtag-lookup.md).
- For authorization and the non-billable registration step, read
  [installation and authentication](references/installation-and-auth.md)
  and [installation registration](references/installation-registration.md).
- For shared task, billing, and connection details, read [tasks and
  results](references/tasks-and-results.md), [billing, errors, and
  recovery](references/billing-errors-and-recovery.md), and [Bundled MCP
  Client diagnostics](references/mcp-connection.md).
- For update guarantees and controls, read [automatic updates and
  safety](references/automatic-updates-and-safety.md). For removal, read
  [uninstall and disconnect](references/uninstall-and-disconnect.md).

## Runtime and safe automatic updates

The bundled client silently checks for a newer release at most once
every 24 hours per installation. When a newer version is available, it
installs automatically without separate confirmation. It downloads only
from the fixed official Beatra discovery and immutable CDN paths for
this package, channel, and locale, verifies discovery data, archive,
manifest, and every packaged file, and replaces only package-owned
files.

Update checks, downloads, verification, replacement, rollback, and
recovery fail open: the current installation remains usable and the
original command continues. An update failure never authorizes retrying
a paid lookup, clone, speech, or video request. The setting persists
for this installation. See
[automatic updates and safety](references/automatic-updates-and-safety.md).

```text
python3 scripts/mcp_client.py update --auto off
python3 scripts/mcp_client.py update --auto on
python3 scripts/mcp_client.py update --check
```

Files in this skill

  • SKILL.md12 KB
  • manifest.json2.8 KB
  • references/automatic-updates-and-safety.md1.9 KB
  • references/billing-errors-and-recovery.md3.6 KB
  • references/hashtag-lookup.md2.8 KB
  • references/installation-and-auth.md5.7 KB
  • references/installation-registration.md1 KB
  • references/mcp-connection.md1.2 KB
  • references/tasks-and-results.md2.2 KB
  • references/uninstall-and-disconnect.md2.7 KB
  • references/workflow.md2.8 KB
  • scripts/authorize.py21.8 KB
  • scripts/mcp_client.py60.1 KB
  • scripts/uninstall.py10.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…