agentleFS
WaveSpeedAIWaveSpeedAI/agent-skills/skills/wavespeed/SKILL.md

wavespeed

Skill2 starsChanged 11 days agoMITView on GitHub

Generate or edit AI media (image, video, audio, 3D) on WaveSpeed, through the WaveSpeed MCP tools when they are connected or the wavespeed CLI on the user's machine. Use whenever the user asks to create, edit, animate, extend, upscale, or transform an image or video, generate audio/TTS/music or 3D, or produce marketing creatives.

5 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 1

    1. WaveSpeedAI/wavespeed-kimi-plugin★ 1100% same

    Edited · 2

    1. WaveSpeedAI/wavespeed-cli★ 2695% same
    2. TheVeller/claude-skills★ 424% same

    Wrote their own version · 2

    1. Samin12/skills★ 8same name
    2. ai-ecoverse/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    The wavespeed CLI: use it when it is installed, for local files (@./path), batches and scripts.

    line 11
  2. Very specific:

    Every model on the platform is one wavespeed run <model-id> (MCP: run_model).

    line 43
  3. Very specific:

    If wavespeed.json exists (created by wavespeed init):

    line 75
  4. Distinctive:

    Never: ask the user to paste an API key into the chat.

    line 84
  5. Very specific:

    If a run fails with Insufficient credits (or says a top-up is required), the balance is too low: do not retry.

    line 90
  6. Very specific:

    Don't invent model IDs. Confirm with wavespeed models or wavespeed schema <id> (MCP: list_models, get_model_schema) before a generic run.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

WaveSpeed

WaveSpeed runs every model on its platform. There are two ways in, and they do the same things:

  • MCP tools (generate_image, generate_video, …): use them when the WaveSpeed MCP server is connected. The hosted server cannot read local files: pass public URLs, or use the CLI for files on disk.
  • The wavespeed CLI: use it when it is installed, for local files (@./path), batches and scripts.

For plain image and video work, use the shortcuts. For anything else (audio, 3D, upscaling, a specific endpoint, exact parameters), use the generic run.

Images and videos: the shortcuts

TaskCLIMCP tool
Image from a prompt (optionally with reference pictures)wavespeed generate image "<prompt>" [--image @./ref.jpg]generate_image
Edit, restyle, combine imageswavespeed edit image "<prompt>" --image @./photo.jpgedit_image
Video from a prompt, a first/last frame, or referenceswavespeed generate video "<prompt>" [--first-frame …] [--ref-image …]generate_video
Edit a videowavespeed edit video "<prompt>" --video @./clip.mp4edit_video
Continue a videowavespeed extend video "<prompt>" --video @./clip.mp4extend_video

They use the same models as the WaveSpeed /chat page and pick the endpoint (text, image, reference, edit) from the inputs you give. In the prompt, refer to media as @image 1, @video 1, @audio 1, in the order given ("put the product in @image 1 into the kitchen in @image 2").

  • Price first for videos: CLI --estimate --json, MCP estimate_only: true. It returns the endpoint, the exact request and the price, and submits nothing.
  • Models: pass -m / model only when the user names one; a named model is never switched. Without it the default is used, or another model only when the default cannot take the inputs.
  • Options: --aspect-ratio, --resolution, --duration (CLI) or the same fields (MCP). Set them only when the user asks; values are snapped to what the model supports, and every change is reported.
  • CLI: add --json to read the result, --download to save files.

Default models

DefaultAlternatives (-m / model)
Imageseedream-5-pro (Seedream 5 Pro)gpt-image-2.6 (GPT Image 2.6, the model behind ChatGPT Images 2.6; strong at text and photorealism), gpt-image-2.5, nano-banana-2.1, nano-banana-pro, nano-banana-2, gpt-image-2
Videoseedance-2.5 (Seedance 2.5)seedance-2.5-turbo, kling-4.0, wan-3.0, wan-3.0-prime, minimax-h3 (cheap and fast, native stereo audio; defaults to 768p, its counterpart of 720p), older Seedance 2.0 tiers

Video resolution is 720p unless the user asks for another (MiniMax H3: 768p). Offer 480p for a cheaper draft.

Everything else: the generic run

Every model on the platform is one wavespeed run <model-id> (MCP: run_model). The model id is always explicit.

# 1. FIND a model in the live catalog (MCP: list_models)
wavespeed models "upscale"
wavespeed models --type text-to-audio --popular

# 2. INSPECT its inputs (MCP: get_model_schema)
wavespeed run <model-id> -h

# 3. RUN it, with --json so you can read the result (MCP: run_model)
wavespeed run <model-id> -p "..." -i key=value --json

run --json returns { id, model, prompt, outputs: [url, ...], saved: [path, ...], elapsed_ms, raw }. Keep id: it is the handle for wavespeed show <id> (MCP: get_prediction) if anything is interrupted. Use the URL when the user wants a link; add --download when they need the file on disk.

# Local files: @path uploads the file and passes its URL
wavespeed run <model-id> -i image=@./photo.jpg --json
wavespeed run <model-id> -i images='["@./a.jpg","@./b.jpg"]' --json

# Or upload separately when you need the URL itself (MCP: upload_file / create_upload)
URL=$(wavespeed upload ./photo.jpg --json | jq -r .url)

# Save outputs with a template
wavespeed run <model-id> -p "..." --download "./out/{index}.{ext}"

The generic run never changes the user's prompt or inputs. The single exception is explicit: an @path value uploads that file and substitutes its hosted URL. Bare paths are never uploaded.

Project config and aliases

If wavespeed.json exists (created by wavespeed init):

  • defaultModel lets wavespeed run -p "…" (no model arg) work.
  • Aliases are named shortcuts that bundle model + default inputs. Run wavespeed aliases to see them; wavespeed run <alias> -h shows the resolved schema. CLI -i k=v overrides alias defaults.

Auth

  • CLI: wavespeed status shows whether the user is signed in. If not, ask them to run wavespeed login (opens https://wavespeed.ai/accesskey).
  • MCP: if the tools ask for authorization, the user approves the connection once (in Claude Code: /mcp, pick wavespeed).
  • Never ask the user to paste an API key into the chat.

Cost and credits

  • wavespeed price <id> -i k=v --json (MCP: get_price) estimates a run without generating or charging. The shortcuts have --estimate / estimate_only.
  • wavespeed balance (MCP: get_balance) shows the remaining credit; wavespeed usage and wavespeed billings show what was spent.
  • If a run fails with Insufficient credits (or says a top-up is required), the balance is too low: do not retry. Tell the user and give them https://wavespeed.ai/top-up. You cannot pay for them.

Pitfalls

  • Don't invent model IDs. Confirm with wavespeed models or wavespeed schema <id> (MCP: list_models, get_model_schema) before a generic run.
  • Local files: use @./file.jpg. Bare paths are NOT uploaded and the model will reject them. The hosted MCP server cannot read local files at all.
  • wavespeed delete requires --yes when run non-interactively (that includes you).
  • A run that fails with a gateway or network error (502/503/504, connection reset, timeout) does NOT mean the task failed, and the submit request is never retried automatically on those errors (only an HTTP 429 rate limit, which the API returns before any task exists, is retried), so re-running can create a duplicate paid task. Do not re-run immediately. If the error contains a task id (task_id / prediction id), keep checking it with wavespeed show <id> --json (MCP: get_prediction) until its status is terminal (completed, failed, cancelled, timeout, deleted). If no id was returned, check recent predictions with wavespeed history --json (MCP: list_predictions; add the model; default window is the last 24h) and re-run once only if none matches. A client-side wait timeout or an interrupted run does not mean the task failed: tasks can run for a long time, so do not give up after a fixed time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.