SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsjianying-draft-export-prep

jianying-draft-export-prep

Design & creation

View repository

Updated 10-27 10:06

About this skill

JianYing Export Prep

Choose agent preview, draft archiving, or native export according to the delivery goal, and truthfully report the actual evidence.

When to use

  • The user explicitly requests the Jianying capability corresponding to this skill's title and accepts handling through the unified Rust jianying CLI.
  • The user needs auditable planning, execution, or verification evidence, rather than just a conceptual answer.
  • When the requirement is not yet clear, first hand it to jianying-draft-use routing; other editors, general video knowledge Q&A, or speculative execution lacking necessary materials should not be handled with this skill.

Capability boundaries

  • ✅ Can do: Generate deterministic plans based on real paths and probe results; when capability is supported , execute operations in this domain; output the actually achieved evidence level.
  • ⚠️ Requires conditions: Writes must use isolated copies; costs, external services, and native application actions must have precise approval; playback or export conclusions must have corresponding runtime evidence.
  • ❌ Out of scope: Do not automatically install or upgrade the CLI, do not generate Python draft scripts, do not call external headless checkout, do not overwrite source drafts, and do not fabricate resource IDs, media facts, or success statuses.

Step 1 — Establish a factual baseline

Record the user's goal, absolute paths, host platform, target deliverable, and allowed side effects; when information is insufficient, first provide a read-only diagnostic plan and list the missing facts item by item.

Step 2 — Handshake capabilities

Run version, doctor, and capabilities checks. A satisfied version does not mean the capability is available;partial、external_dependency or a missing state must enter the degraded path.

Step 3 — Validate inputs

Probe media, drafts, configuration, or task state; reject nonexistent paths, out-of-range times, unknown schemas, mismatched hashes, and approvals that cannot be bound to a target.

Step 4 — Form a deterministic plan

Write operations, parameters, output paths, risk levels, confirmation points, and expected evidence into the plan. Order multiple tasks as "read-only facts → reversible writes → external/native actions".

Step 5 — Execute or stop before the gate

Execute only steps that are supported and authorized. When output is ambiguous, times out, or partially succeeds, retain the task ID, audit logs, and artifacts; do not automatically retry.

Step 6 — Verify and deliver

Run structural validation, then append cold reopen, playback, or native export evidence according to the goal; report the actual level, failed fields, recoverable actions, and unverified items.

Rules

  • Material durations, dimensions, streams, hashes, and draft versions in the plan must come from tool output.
  • Approval must be bound to the command, parameters, target, validity period, and budget; reconfirm if any field changes.
  • User data is processed only within local target paths and declared external Provider boundaries; unrelated credentials must not be collected, uploaded, or recorded.
  • When current evidence is insufficient, use UNVERIFIED、BLOCKED or AMBIGUOUS; it is forbidden to fill in results with inference.

Gotchas

  1. Treating version as capability: Always check the specific capability; do not execute directly just because the CLI version is new enough.
  2. Treating structural validation as film acceptance: project verify only proves the structural layer; playback and native export require independent evidence.
  3. Modifying the source draft directly: First create an isolated copy and record the input hash; any in-place overwrite request must stop and be changed to a new output.
  4. Automatic retry for ambiguous: First query the task, audit, and external artifacts; only after confirming no side effects occurred can the user approve a retry.
  5. Filling in resources or times from memory: Resource IDs come from the catalog, times come from probe/ASR/project data; if they cannot be obtained, explicitly block.
  6. Vaguely asking for more information: First provide an executable read-only plan, then explicitly list the gaps such as paths, delivery level, or authorization.

Verification Checklist

  • CLI identity, version, and capability have been recorded.
  • All input paths, media facts, and hashes are reviewable.
  • Write targets are isolated from source drafts, and confirmation points are precisely bound.
  • Failure and ambiguous paths retain the task ID, logs, and recovery suggestions.
  • The final wording is consistent with the actual evidence level.

Execution Contract

  • Trigger conditions: the user is preparing to preview, deliver a draft, generate the final MP4, or check export readiness.
  • Required capability:render.proxy、render.native、runtime.profile。
  • Minimum CLI version:1.6.0; when the native capability or Runtime Profile is not supported, the native path must be stopped.
  • Default risk:external_native_execution; proxy rendering is a reversible local write.
  • Input facts: draft verification results, delivery type, absolute output path, overwrite policy, Runtime Profile, editor state, and authorization.
  • Confirmation points: precise confirmation before launching Jianying, native export, overwriting output, or using member resources or external services.
  • Success evidence:native_export; a proxy artifact can never serve as native_export.
  • Prohibited actions: do not generate Python draft scripts, do not call external headless checkout, do not describe an ffmpeg proxy preview as the final Jianying MP4, or automatically attempt on an unknown Runtime Profile.

Workflow

  1. Execute project verify, check the materials, subtitles, audio, and output path.
  2. When only a preview is needed, use render proxy or render batch, and make clear that it does not include the full native effects.
  3. Before native export, require render.native and runtime.profile to be supported, and obtain precise approval.
  4. Persist the native-export task and track progress; mark it ambiguous on timeout or when the result is unknown.
  5. Verify the output container, streams, duration, non-emptiness, and SHA-256, and perform playback spot checks when necessary.

For gates and result determination, see references/workflow.md. For a native export Job example, see examples/minimal-job.json。

Progressive Materials