Used for default text, styled text, bubbles, animations, text templates, and style operations in the CapCut "Text" panel. Batch subtitle timeline work is handled by the subtitle category; this skill focuses on regular on-screen text.
When to use
- Create titles, captions, corner labels, chapter text, styled text, or bubbles.
- Adjust font, font size, color, font weight, local styles, and in/out animations.
- Search official text templates and apply them to an isolated draft.
Capability boundaries
- ✅ Can do: regular text, basic/local styles, bubble styled text, animations, and verifiable text template plans.
- ⚠️ Requires conditions: fonts must be available; official resources require entitlements; visual appearance requires a cold restart.
- ❌ Should not use: does not handle batch subtitle alignment, ASR, or translation timelines, and does not claim pixel consistency with unknown fonts.
Quick start
You can directly say: "Add a main title from 0–2 seconds," "Change the second line of the title to yellow bold," "Add a fade-out animation to the ending text." On first use, load feature flow。
Run contract
- Trigger conditions: the user requests new text, text styles, styled text, bubbles, animations, or text templates in the Text panel.
- Required capability:
captions.edit、captions.style、captions.style_ranges、captions.bubble、captions.animation、media.official_resource_apply。 - Minimum CLI version:
1.6.19; when the official text template application capability is not supported, stop at the preview/approval gate. - Default risk:
reversible_write。 - Input facts: target draft copy, text content, time range, position/safe area, font availability, styles, and resource authorization.
- Confirmation points: confirm separately for writing to an existing draft, using Pro/trial text resources, replacing brand copy, and native playback.
- Success evidence:
cold_reopen; the mere existence of JSON fields cannot prove font and line-break appearance. - Prohibited actions: must not treat batch subtitle time estimates as regular text layout, must not forge effect/resource IDs, and must not claim style consistency when fonts are missing.
Workflow
Step 1 — Locate text
List existing text and read the target segment ID.
Step 2 — Choose action
Follow feature flow to choose the create, style, styled text/bubble, animation, or template path.
Step 3 — Isolated execution
Execute fixed argv on the isolated copy; for official resources, preview first, verify entitlements, and obtain a receipt.
Step 4 — Verify
captions get/list and project verify check the structure; cold restart to check fonts, line breaks, safe area, and animations.
Step 5 — Restore
On failure, restore the text segment snapshot or delete the newly added segment.
Rules
- Text content, range, position, and style must be bound to the same segment ID.
- If a font is missing, report replacement candidates first; do not silently substitute.
- Official templates and local styles are different routes and must not impersonate each other.
- Brand statement changes must be confirmed separately.
Gotchas
- Mixing regular text and subtitles: use the subtitle skill for narrative subtitles; only titles/corner labels go through this skill.
- UTF-16 range out of bounds: validate local styles by code unit; do not guess by the number of visible characters.
- Font exists only on this machine: check font resources and fallback before cold restart.
- Forged bubble resource ID: Use only IDs from the catalog or verified drafts.
- Template application becomes default text: When capability is insufficient, remain blocked; do not degrade into a disguise.
Security and Data
Do not upload copy or font files; networked templates, translation, or Providers are invoked only within the precise authorization scope, and logs retain only summaries and resource identities.
For a minimal Job, see examples/minimal-job.json。