nim-generate

Nim Generate

Generate and edit images and videos through the Nim MCP. One skill for both: model discovery is shared, and the only real branch is image vs. video.

UX rules

1. Be concise. Don't dump raw IDs, JSON, or tool plumbing into the chat — report the finished result, not the mechanics.
2. No jargon. Don't narrate "calling models_explore" or "polling status."
3. Reply in the user's language. Detect it from their message; keep technical values (16:9, 1080p) as-is.
4. Pick a sane default and move. Don't interrogate. Ask one thing at a time, and only when a required input is genuinely missing.
5. Don't pre-optimize for cost. Prefer the quality default first; only weigh cheaper models if the user asks. Check get_credit_balance before a deliberately expensive run (high resolution, long video, large batchSize).
6. Never invent Nim URLs. generate_image / generate_video return no link. Get the result by polling get_generation_status and report only the URL it actually returns.

Workflow

1. Pick the model. The Nim catalog is live — discover, don't hardcode.
   • Unsure which model fits → models_explore with action: "recommend", the user's intent as query, type: "image" or "video", and input: "image" when a reference will be supplied. For video, pass minDurationMs if the user named a length.
   • Comparing options → action: "search" / "list".
   • Then action: "get" on the chosen model_id to read its exact generationContract. This is the source of truth for which params are allowed.
2. Prepare references. For image editing, image references, or image-to-video, the reference must be a Nim file URL first:
   • Call media_upload, run the returned curl_example against the local path or Claude attachment, then pass the response file_url in fileInputs.
   • Never pass a local filesystem path straight to a generation tool.
3. Generate. Call generate_image or generate_video and pass only params the generationContract allows. Submit model_name alongside model_id for clearer user-facing status.
4. Poll, then deliver. generate_image / generate_video start an async job and return no result and no link. You are running in a terminal client (Claude Code / Codex) that does NOT render the Nim generation widget — so you must poll get_generation_status with the returned workflowId / promptId until finished / failed / cancelled, then deliver the final media URL from that response.
   • Never tell the user the result "will appear in a widget" — it will not appear here. Never describe a queued job as done.
   • The Nim widget only renders in MCP-Apps hosts (claude.ai, ChatGPT, Claude Desktop), which connect to the MCP directly rather than through this skill. Ignore it here.

Image vs. video — quick routing

• Still asset, edit, restyle, logo, poster, character art → image (generate_image).
• Motion, clip, animation, or "make this image move" → video (generate_video).
• "Animate this photo" / "image-to-video" → video with the reference in fileInputs (choose an image-input video model via input: "image").

Inputs

Pass a param only when the selected model's generationContract lists it.

Param	Applies to	Notes
prompt	both	Required. Carry the full creative intent.
model_id	both	Required. Always from models_explore.
fileInputs	both	Nim file URLs from media_upload. Required for edit / image-input / image-to-video models.
requestedAspectRatio	both	e.g. 16:9, 9:16, 1:1.
resolution	both	e.g. 1080p, 2K — only values the contract offers.
mediaLength	video	Input duration in ms (5000, 8000).
fps, keepSound	video	Only when the model supports them.
seed	both	Omit or -1 to randomize; reuse a value to reproduce.
batchSize	both	1–4 variations in one call. Use for ideation / options.

Variations & ideation

When the user wants options, directions, or "a few ideas," set batchSize (2–4) so Nim returns several takes from one request, each with a randomized seed. Present them as a set to compare, not as a single answer.

When a generation fails

Surface the returned error / errorCode plainly. Don't silently retry with changed params — ask the user first, unless they already told you to iterate.