원클릭으로 Manus에서 모든 스킬 실행

nim-template-runner

스타2

포크3

업데이트2026년 6월 29일 15:17

Find, inspect, and run Nim templates through the Nim MCP. Use only when the user explicitly asks for Nim templates, says "template" / "шаблон", asks to browse or recommend templates, or asks to run a specific named Nim template. Uses explore_templates, get_template, media_upload, and run_template. NOT for ordinary image/video generation requests; use nim-generate for those.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nim-video

nim-video/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Nim Template Runner

Browse and run Nim templates through the Nim MCP. Templates are a separate path from ordinary image/video generation: use the template tools, not local runner apps or hand-built HTML.

UX Rules

Use templates only on explicit intent. The user must ask for a template, named template, or template browsing/recommendation.
Stay concise. Do not dump raw template contracts or JSON unless the user asks to inspect them.
Reply in the user's language. Keep technical values like 9:16 and numOutputs unchanged.
Ask only for required missing inputs. For optional inputs, ask only when they materially change the output.
Never invent result links. run_template starts an async job. Poll get_generation_status unless a Nim widget is actually rendered by the host.

Workflow

Find a template.
- If the user asks to browse or is unsure, call explore_templates with action: "recommend" and the user's creative task as query.
- If the user names a template, call explore_templates with action: "search" and the name as query.
- Present a short selectable list. Do not run a template until the user has picked one, unless the request clearly names a single template to run.
Inspect the template. Call get_template for the selected slug or template_id. Treat templateContract as the source of truth.
Collect inputs.
- Collect every required input.
- Ask about optional settings only when they affect the result in an obvious user-facing way, especially aspect ratio, number of outputs, number of visuals per output, and photo/style type.
- Use contract labels when talking to the user; use contract names only in the run_template payload.
Upload local files. For local paths or attachments, call media_upload, run the returned curl_example, and pass the resulting file_url under inputs.files.
Run the template. Call run_template with namespaced inputs:
- inputs.prompts for prompt/text inputs.
- inputs.files for uploaded file inputs.
- inputs.urls for URL branches of url_or_files inputs.
- inputs.fields for checkbox/select values.
- inputs.settings for aspect ratio and output counts.
Poll, then deliver. Poll get_generation_status with the returned workflowId / promptId until finished, failed, or cancelled, then deliver only the real final media URL(s).

When uploading media

Never pass local filesystem paths directly to run_template; use media_upload and pass the returned file_url.
If a template input depends on a reference file and upload fails, stop before run_template. Do not run the template without the file just because the Nim MCP widget or template tool is available.
In Claude Cowork, paths from the user's computer are never readable by the agent unless the file is in the current Cowork Working folder. If a file cannot be read, stop and ask the user to add it to the current Cowork Working folder, then retry from that accessible file.
Inline previews or images visible in chat are not always uploadable files. If no actual file path/attachment/source is available, ask for one before upload.
If media_upload returns an upload URL but the actual upload is blocked by DNS, network egress, CSP, sandboxing, or allowlist restrictions, stop. Do not try alternate domains, proxy URLs, guessed endpoints, custom upload formats, or invented fileInputs values such as upload:/path, local paths, or placeholder URLs. Do not claim the Nim widget can upload the file directly. Tell the user to add *.nim.video to their allowlist; the setup page is https://nim.video/mcp. Retry only after they confirm the environment is fixed.

Failure Handling

If run_template returns insufficient_credits, present the returned purchase/upgrade options and stop. Do not retry until credits are resolved.
If generation fails, surface the returned error / errorCode plainly. Do not silently switch templates or change inputs without user confirmation.
Never create local HTML artifacts, scripts, or mock runners instead of calling run_template.

이 저장소의 다른 Skills

같은 저장소

nim-human-generation

nim-video/skills

Use when generating believable editorial young-adult human portraits or fashion/UGC character images with Nim, especially Gen-Z fashion casting, model/person look development, aesthetic human references, or prompt-driven human generation. Asks for age or age range, sex/gender presentation, ethnicity/look, and additional notes; defaults to Nano Banana Pro in 9:16, but supports user-specified models such as GPT Image 2 by discovering the live Nim model contract.

2026-07-092

nim-quality-prompts

nim-video/skills

Use when improving, writing, rewriting, planning, or executing AI video prompts for Seedance, Higgsfield, Nim MCP, UGC, cinematic generation, image-to-video, reference frames, character consistency, GPT Image 2, Nano Banana Pro, 2K stills, LUTs, camera quality, shot lists, storyboards, beats, montage, sequence, camera angles, or visual grammar.

2026-07-092

nim-ugc-prompts

nim-video/skills

Use when writing, improving, planning, or generating Nim/Seedance UGC video prompts for TikTok, Reels, Shorts, creator ads, direct-to-camera hooks, selfie videos, iPhone footage, testimonials, street interviews, mirror try-ons, outfit changes, product/location walkthroughs, VO, lip sync, audio references, or image-to-video prompts with character/location/product references.

2026-07-092

nim-product-creative

nim-video/skills

Use when the user wants commercial product visuals or videos from product images, reference assets, or a product brief: ecommerce listing images, product photoshoots, studio/catalog shots, white-background product photos, lifestyle scenes, ad creatives, hero images, product launch visuals, social content, UGC-style creatives, on-model apparel/accessory shots, Shopify/Amazon PDP assets, product-in-use scenes, product videos, or similar selling, merchandising, marketplace, brand, or campaign imagery. Search Nim templates first for product/photoshoot/ad-style workflows, show the user matching template options with cost/input info, get an explicit template choice or approval, inspect the selected template contract, collect required inputs, upload references, and run the template. Fall back to Nim model generation only when no suitable template exists or the user explicitly asks for raw generation.

2026-07-092

nim-upscale

nim-video/skills

Improve image or video quality with Nim upscalers. Use when the user asks to make an existing image or video better, higher quality, sharper, clearer, cleaner, higher resolution, less blurry, less pixelated, enhanced, restored, upgraded, upscaled, 4K, HD, 60fps, smoother, or otherwise improved in visual quality without requesting a creative restyle or new generated content. Routes images to upscale_image and videos to upscale_video. Uses bytedance by default for video upscaling and asks for missing source/target details before running.

2026-07-092

nim-character-consistency

nim-video/skills

Create new Nim images of an existing character, person, product, object, mascot, avatar, or branded item while preserving visual identity across scenes, poses, lighting, outfits, or artistic media. Use for character consistency, consistent character images, identity-preserving edits, product consistency, same person/object in a new scene, or variants from one or more reference images. Discovers the current Nim model with models_explore, follows its generationContract exactly, uploads references with media_upload, and submits with generate_image.

2026-07-092

name	nim-template-runner
description	Find, inspect, and run Nim templates through the Nim MCP. Use only when the user explicitly asks for Nim templates, says "template" / "шаблон", asks to browse or recommend templates, or asks to run a specific named Nim template. Uses explore_templates, get_template, media_upload, and run_template. NOT for ordinary image/video generation requests; use nim-generate for those.

Nim Template Runner

Browse and run Nim templates through the Nim MCP. Templates are a separate path from ordinary image/video generation: use the template tools, not local runner apps or hand-built HTML.

UX Rules

Use templates only on explicit intent. The user must ask for a template, named template, or template browsing/recommendation.
Stay concise. Do not dump raw template contracts or JSON unless the user asks to inspect them.
Reply in the user's language. Keep technical values like 9:16 and numOutputs unchanged.
Ask only for required missing inputs. For optional inputs, ask only when they materially change the output.
Never invent result links. run_template starts an async job. Poll get_generation_status unless a Nim widget is actually rendered by the host.

Workflow

Find a template.
- If the user asks to browse or is unsure, call explore_templates with action: "recommend" and the user's creative task as query.
- If the user names a template, call explore_templates with action: "search" and the name as query.
- Present a short selectable list. Do not run a template until the user has picked one, unless the request clearly names a single template to run.
Inspect the template. Call get_template for the selected slug or template_id. Treat templateContract as the source of truth.
Collect inputs.
- Collect every required input.
- Ask about optional settings only when they affect the result in an obvious user-facing way, especially aspect ratio, number of outputs, number of visuals per output, and photo/style type.
- Use contract labels when talking to the user; use contract names only in the run_template payload.
Upload local files. For local paths or attachments, call media_upload, run the returned curl_example, and pass the resulting file_url under inputs.files.
Run the template. Call run_template with namespaced inputs:
- inputs.prompts for prompt/text inputs.
- inputs.files for uploaded file inputs.
- inputs.urls for URL branches of url_or_files inputs.
- inputs.fields for checkbox/select values.
- inputs.settings for aspect ratio and output counts.
Poll, then deliver. Poll get_generation_status with the returned workflowId / promptId until finished, failed, or cancelled, then deliver only the real final media URL(s).

When uploading media

Never pass local filesystem paths directly to run_template; use media_upload and pass the returned file_url.
If a template input depends on a reference file and upload fails, stop before run_template. Do not run the template without the file just because the Nim MCP widget or template tool is available.
In Claude Cowork, paths from the user's computer are never readable by the agent unless the file is in the current Cowork Working folder. If a file cannot be read, stop and ask the user to add it to the current Cowork Working folder, then retry from that accessible file.
Inline previews or images visible in chat are not always uploadable files. If no actual file path/attachment/source is available, ask for one before upload.
If media_upload returns an upload URL but the actual upload is blocked by DNS, network egress, CSP, sandboxing, or allowlist restrictions, stop. Do not try alternate domains, proxy URLs, guessed endpoints, custom upload formats, or invented fileInputs values such as upload:/path, local paths, or placeholder URLs. Do not claim the Nim widget can upload the file directly. Tell the user to add *.nim.video to their allowlist; the setup page is https://nim.video/mcp. Retry only after they confirm the environment is fixed.

Failure Handling

If run_template returns insufficient_credits, present the returned purchase/upgrade options and stop. Do not retry until credits are resolved.
If generation fails, surface the returned error / errorCode plainly. Do not silently switch templates or change inputs without user confirmation.
Never create local HTML artifacts, scripts, or mock runners instead of calling run_template.