SuperAPI AI Directory

jianying-draft-smart-package

Design & creation

View repository

Updated 10-27 10:06

About this skill

JianYing Smart Package

Used for CapCut's "Smart Packaging" and "Smart B-Roll". They are combined workflows, not a one-click button that can be tapped blindly; the proposal must first be broken down into reviewable change sets.

When to use

  • Choose smart recommendations, tech style, lifestyle Vlog, marketing sales, knowledge sharing, or variety entertainment packaging.
  • Request AI to automatically add B-Roll, subtitles, decorative text, sound effects, visual effects, or transitions.
  • Review, approve, partially rework, stop, or resume smart packaging tasks.

Capability boundaries

  • ✅ Can do: style routing, preview requests, proposal breakdown, protection rules, approval, application, review, and resume.
  • ⚠️ Requires conditions: a version-bound Adapter, budget, allowed tracks, and a pre-application snapshot.
  • ❌ Should not use: does not accept unexplainable changes, does not delete protected content, does not treat GUI prompts as quality passing.

Quick start

You can directly say: "Preview lifestyle Vlog smart packaging but do not change the dialogue", "Break the proposal into B-Roll and subtitles for my review", "Resume the last timed-out packaging task". On first use, load feature flow。

Run contract

  • Trigger conditions: the user requests smart packaging, one-click video generation, smart B-Roll, or composite AI editing.
  • Required capability:runtime.control_catalog、runtime.controls、media.official_resource、project.edit_isolated、render.proxy。
  • Minimum CLI version:1.6.19; when there is no version-bound Adapter and change set evidence, only preview planning is allowed.
  • Default risk:external_native_execution。
  • Input facts: style, material list, allowed tracks, protected dialogue/brand/shots, budget, maximum duration, target channel, and editor version.
  • Confirmation points: preview, resource download, applying composite changes, model calls/costs, and native playback are confirmed separately.
  • Success evidence:playback; proposal success or a GUI toast does not equal passing the draft and narrative.
  • Prohibited behavior: must not automatically delete protected content, accept unexplainable changes, silently resubmit ambiguous tasks, or replace user-specified editing methods with smart packaging.

Workflow

Step 1 — Freeze the request

Form jianying-smart-package-request/v1, freeze the input summary, protected items, and budget.

Step 2 — Preview and breakdown

Follow the feature flow to generate a preview proposal and split it into B-Roll, subtitles, decorative text, sound effects, visual effects, and transitions.

Step 3 — Independent approval

Verify protection rules, resource rights, time range, and budget, then request approval bound to the change summary.

Step 4 — Apply and verify

Apply to an isolated draft and re-check the draft diff, proxy preview, and playback.

Step 5 — Resume

On failure, locally delete explainable changes or restore the pre-application snapshot; when the state is unclear, keep the task ID for querying.

Rules

  • Requests, proposals, approvals, and evidence are chained using stable digests.
  • Protected dialogue, brand statements, and locked shots are non-modifiable by default.
  • Validate rights, scope, and cost separately for each resource.
  • For ambiguous tasks, only query/resume; do not create a new request.

Gotchas

  1. Treating one-click packaging as a black box: Must break down observable changes.
  2. Content drift between preview and application: Approval binds to the proposal digest.
  3. AI deletes key dialogue: Reject immediately when protection rules fail.
  4. Budget is checked only after submission: must be gated before preview and approval.
  5. GUI toast falsely claims completion: rely on draft diffs, playback, and human narrative review.

Security and Data

Do not upload original assets unless precise approval includes the Provider, file digest, purpose, retention period, and cost; credentials and raw account data do not enter plans or logs.

For a minimal Job, see examples/minimal-job.json。