MediaKit Professional Media Processing Entry

MediaKit is a professional toolset for audio-visual and image processing. It unifies common media processing, content understanding, and intelligent enhancement capabilities into

mediakit-cli

, suitable for complete workflows from material processing to final production.

Usage Rules

When actually executing
```
mediakit-cli
```
business commands through this Skill or domain Skills, you must inject the source and host in the same call to prevent the CLI from failing to recognize the call source:
- ```
MEDIAKIT_SURFACE=skill
```
  (fixed as
```
skill
```
  for calls from this Skill / domain Skills)
- ```
MEDIAKIT_RUNTIME=<current Agent host>
```
  (use
```
unknown
```
  if unable to determine)
Injection method: Set environment variables before the command (recommended), do not treat these two values as CLI flags or business parameters.
Read-only discovery commands like
```
--help
```
/
```
--schema
```
/
```
--domains
```
/
```
--version
```
do not require injection; injection is mandatory once real processing or
```
shared query-task
```
is initiated.

Example (attach this to every real call):

bash

MEDIAKIT_SURFACE=skill MEDIAKIT_RUNTIME=<runtime> mediakit-cli editing add-image-to-video --video-url <url> --sub-image-url <url>
MEDIAKIT_SURFACE=skill MEDIAKIT_RUNTIME=<runtime> mediakit-cli shared query-task --task-id <task_id>

Fill

<runtime>

with the current host identifier (e.g.,

cursor

claude-code

codex

); fill

unknown

if uncertain. Do not omit

MEDIAKIT_SURFACE=skill

Capability Scope

Video Editing and Synthesis: Cropping, splicing, transitions, speed adjustment, volume adjustment, video filters, camera movements, picture overlay, subtitle embedding, audio mixing, fade in/out, audio-visual extraction and merging, text scrolling, image-to-video conversion, and multi-screen arrangement.
Audio and Track Processing: Audio transcoding and media detection, speech boundary positioning, separation of human voice and background sound, as well as processing for video audio tracks.
Video Understanding and Enhancement: Video content analysis, plot/script and highlight clipping, image quality enhancement and detection, frame extraction, speech-to-subtitle and subtitle extraction, subtitle erasure, watermark processing, privacy protection, scene and semantic segmentation, picture text recognition, transcoding and repackaging, keying and face swapping, etc.
Image Processing and Content Understanding: Size scaling and volume management, metadata detection, cropping, rotation, flipping and rounding, color and sharpening, negative effect, blurring and masking, watermarking, background removal, text recognition, image quality evaluation and intelligent cropping, etc.

Capability Selection and Priority Loading

Select domain Skills according to the user's processing object and clear goal:

User Goal	Priority Loading
Crop, splice, add transitions, apply filters, adjust camera movements, overlay, mix audio, or arrange existing materials into a finished video	`byted-mediakit-editing`
Process audio transcoding, tracks, speech boundaries, or separation of human voice and background sound	`byted-mediakit-audio`
Process single or batch images, size/volume management, text recognition, image quality or image editing	`byted-mediakit-image`
Video understanding, highlight clipping, frame extraction, image quality enhancement or detection, subtitle extraction, speech-to-subtitle, subtitle erasure, watermarking, privacy protection, transcoding or intelligent video processing	`byted-mediakit-video`

If a request involves multiple stages, first load the domain Skill that best matches the main output, then load other domain Skills as needed for the workflow. When users only state "process a video" or "process an image" without specifying the goal, clarify with the user first, do not guess specific capabilities based on media type.

After selecting the domain, you must first read the corresponding domain Skill, then read the complete reference of the finally selected tool, and finally construct parameters according to the current CLI's machine contract. The shared entry is only responsible for capability navigation and general CLI usage, and does not repeat parameters, enumerations or result fields of specific tools.

Installation and Availability Check

Install the CLI and accompanying Skills for the first use:

bash

npx @volcengine/mediakit-cli install -y

Verify the public entry after installation:

bash

mediakit-cli --version
mediakit-cli --help

Execute this to reinstall Skills carried by the current version:

bash

npx @volcengine/mediakit-cli install --skills-only -y

Initialization and Check

bash

mediakit-cli init
mediakit-cli config show
mediakit-cli doctor

doctor

is used to check the current CLI and local processing dependencies; whether a specific tool supports local processing is subject to the corresponding domain Skill and tool reference.

Command Discovery and Machine Contract

bash

mediakit-cli --domains
mediakit-cli <domain> --help
mediakit-cli <domain> <tool> --help
mediakit-cli <domain> <tool> --schema

--schema

only reads the machine contract of the current valid mode and does not initiate business calls; the top-level includes

name

description

input_schema

and

output_schema

. Before constructing parameters, read the

--help

and

--schema

of the target tool, and use the field descriptions in the complete reference as the Agent usage guide.

Media Input

Directly pass the media input provided by the user to the tool parameters. For local files, pass the local file path (e.g.,

/path/to/file.jpg

./file.jpg

), do not add the

mediakit://

prefix on your own; the CLI's media input adapter will handle the upload. No additional upload commands or parameters are required.

Cloud / Local Mode

When no mode is specified, the CLI's current configuration selects Cloud-first or Local-first.

--local

and

--cloud

are only used to override for a single command; the CLI's

--help

and

--schema

only display parameters and results for the selected mode.

The standardized command order is:

bash

mediakit-cli --cloud <domain> <tool> [flags]
mediakit-cli --local <domain> <tool> [flags]

Parameters not supported by Local cannot be silently ignored; switch to Cloud or remove the corresponding parameter instead. Local tools return processing results synchronously and do not generate Cloud asynchronous tasks. The Local output directory is managed through CLI configuration:

bash

mediakit-cli config set output-path <output directory>

Asynchronous Results

Cloud asynchronous capabilities return

task_id

. First use the shared query command to obtain the task status and final business results:

bash

mediakit-cli shared query-task --task-id <task_id>

When continuous waiting for the final state is required, execute according to the query protocol in query_task.md.

Update

bash

mediakit-cli update
mediakit-cli update --check
mediakit-cli version --check

Shared Query Protocol

Protocol	Description	Command	Reference
query-task	Query the status and final business results of Cloud asynchronous tasks.	`mediakit-cli shared query-task`	reference/query_task.md

byted-mediakit-shared

NPX Install

Tags

SKILL.md Content (Chinese)

MediaKit Professional Media Processing Entry

Usage Rules

Capability Scope

Capability Selection and Priority Loading

Installation and Availability Check

Initialization and Check

Command Discovery and Machine Contract

Media Input

Cloud / Local Mode

Asynchronous Results

Update

Shared Query Protocol