SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsvmake-video-repair

vmake-video-repair

Design & creation

View repository

Updated 10-16 00:23

About this skill

Video quality repair

Capability and preparation

Use video-repair to improve clarity and detail and reduce blur and visual noise. Proceed when the input and quality goal are clear. Route audio-track processing to an appropriate audio capability.

Use parameters supported by the current CLI; consult help or contracts for details. Requires vmake-labs-cli, targeting version 0.1.11, compatible with >=0.1.11 <0.2.0.

Before the first invocation, read CLI setup, resolve the executable, and check its version and tool video-repair --help. If JSON fields or media limits are unclear, query the relevant vmake contracts entry. For output parsing, service questions, or interrupted execution, read runtime and recovery.

Collect input

  1. Obtain one actual video file or URL from the request or attachments. Do not ask again when it is clear. If several candidates are ambiguous, ask the user to choose; process multiple inputs individually only when authorized, and keep a record for each.
  2. Use a real readable path for a local input. Download remote originals according to CLI setup, then submit the local file. If only a media ID is available, query its session for the real URL first. If downloading fails, ask for the original local file.
  3. Add -r '<session_id>' to continue a task; omit it for a new one. Follow CLI setup for defaults, authentication, and missing information. Consult current help for optional parameters and omit unspecified values.
  4. Keep the original source, local path, and session for recovery. When the user supplies a downloaded file, continue the established goal. Do not treat failed output as a source.

Upload and submit

Use the resolved executable with the prepared local file as an individual argument:

vmake tool video-repair --video-file '<local-video-path>'

The CLI validates the file, uploads it through the built-in upload pipeline to obtain its CDN URL, then submits and observes the task. Do not first call create-room or add-media, or construct placeholder media references. Parameter files and separate preflight are optional; follow CLI setup for argument handling and cleanup.

Follow and deliver

  • Preserve original inputs, real session_id / room_url, and every Task ID. Read the original command's stdout and stderr separately without starting another concurrent observer.
  • Deliver only after TASK_STATE_COMPLETED and an actual usable output URL from this task. HTTP 200, stream closure, exit code 0, or end.reason=result alone do not prove completion. Never treat an unknown state as success.
  • Use native previews or attachments when available, otherwise complete clickable URLs with their query parameters. Deliver every usable Part and any successful partial result. Include an actual returned session URL; do not construct one from an ID.
  • For disconnection, timeout, or uncertain acceptance, query the original session and tasks first. Retry processing only after fixing a confirmed failure and obtaining authorization. If output download fails, recover the download without repeating successful processing. See runtime and recovery for details.