/alibabacloud-yike-cli

name: alibabacloud-yike-cli
description: "Use when the user needs Yike CLI for local image/video upload or uploading media to the cloud (including Agent chat attachments exposed as local paths), standalone image/video generation, media info or quality inspection, async media/job wait and recovery, account/auth/config/update checks, listing or installing bundled skill packages, or help showing and choosing Yike CLI model, resolution, ratio, size, duration, and task type parameters for video generation."

Using Yike CLI

This skill is the Agent operation protocol for the `yike` command. Load the appropriate `references/` sub-module based on the user's request, then execute the command. When commands conflict with documentation, treat the current CLI help as authoritative and report the inconsistency to the user; only modify documentation when the user explicitly requests skill maintenance.

Mandatory Loading Rules

Load this skill whenever the user raises any of the following needs:

• Standalone image or video generation.
• Upload local images/videos or upload a video/image to the cloud, or use image/video attachments provided as local paths in Agent chat.
• Generate images/videos based on local attachments, reference images, reference videos, URLs, or mediaIds.
• Query a mediaId's URL, status, duration, resolution, or file size.
• Perform quality gating on generation results.
• Continue, recover, or troubleshoot a known `jobId` / `resumeCommand`.
• Check Yike CLI login, account info, configuration, version, or list/install available bundled skill packages.
• Query Yike CLI model, resolution, ratio, size, duration, or show all task type parameters for video generation.
• Query which reference media types (image/video) and how many references a video model accepts.

Orchestration Logic

This skill orchestrates the **Alibaba Cloud Yike CLI** — a single-binary tool that manages media upload, image/video generation, job lifecycle, and account authentication against the Yike cloud API.

Module Routing Decision Criteria

When a user request arrives, the agent selects the reference module(s) to load based on the primary intent:

1. **Authentication / Setup** → load `references/account-and-setup.md`

• Trigger: login, logout, whoami, config, update, skill install

2. **Upload** → load `references/upload.md`

• Trigger: local file path, Agent chat attachment, or need to convert a local asset to a mediaId

3. **Generation** → load `references/generate.md` (core), plus optionally:

• `references/generate-image.md` — natural-language image generation
• `references/generate-video.md` — natural-language video generation
• Trigger: user wants to create an image or video from a prompt/reference

4. **Model Capabilities** → load `references/video-model-capabilities.md`

• Trigger: need to determine which reference types (image/video) or how many references a model accepts

5. **Media Info / Jobs** → load `references/media-and-jobs.md`

• Trigger: query media status, run quality gate, poll/recover a job

Call Order

[Auth Check] → [Upload if local files] → [Generate with --dry-run] → [User confirms] → [Generate with --yes] → [Job Wait] → [Media Info / Doctor]

Module Interactions

• **Upload** produces a `mediaId` (status `Normal`) that feeds into **Generate** as `--reference-image` or `--reference-video`.
• **Generate** produces a `jobId` and `resumeCommand` consumed by **Media & Jobs** for polling.
• **Media & Jobs** returns the final `mediaId` of the output, which can be inspected with `media info` or validated with `media doctor`.
• **Account & Setup** must succeed (authenticated state) before any Upload or Generate call.

Module Routing Table

Load the relevant sub-module based on the request:

| Need | Command Family | Sub-module | | --- | --- | --- | | Local image/video upload, Agent chat attachment → mediaId, upload status wait | `yike media upload`, `yike media wait` | [`references/upload.md`](references/upload.md) | | Standalone image/video generation, model/resolution/ratio/size/duration/taskType selection | `yike generate image`, `yike generate video` | [`references/generate.md`](references/generate.md); natural-language image gen: [`references/generate-image.md`](references/generate-image.md); natural-language video gen: [`references/generate-video.md`](references/generate-video.md) | | Video model accepted reference media types and counts | `yike generate video` | [`references/video-model-capabilities.md`](references/video-model-capabilities.md) | | Media info / quality gating, job polling and recovery | `yike media info/doctor`, `yike job watch/recover` | [`references/media-and-jobs.md`](references/media-and-jobs.md) | | Authentication/context, account info, updates, skill installation | `yike auth/config`, `yike whoami/account/update`, `yike self skill install` | [`references/account-and-setup.md`](references/account-and-setup.md) |

Shared Execution Protocol

The following rules apply to all command families.

1. Verify Authentication and Context

Before any operation that accesses the Yike API, run:

yike auth status --format json
yike config get --format json

If not logged in, complete browser authorization with `yike auth login --format json`; do not proceed with upload or generation tasks until authorization completes. Use `yike auth logout --format json` when logout is needed. Do not report internal authentication handling to the user during normal flow; only surface authentication failures and recover using `details.reauthCommand`. Full rules for login, configuration, and context overrides are in [`references/account-and-setup.md`](references/account-and-setup.md).

2. Always Use JSON Format for Skill Execution

All commands that require parsing, decision-making, recovery, or delivery must explicitly append `--format json`. Only use the default text or `--format text` when the user explicitly requests human-re