Spicy Ai Video

Turn a 60-second talking head clip into 1080p high-energy edited videos just by typing what you need. Whether it's turning bland footage into visually intens...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-editing integration: it asks only for a service token, describes uploading user video files to a remote API, and contains no unexpected credential or install demands.

Purpose & Capability

Name/description (cloud GPU video editing) match the runtime instructions and API endpoints. Requiring a NEMO_TOKEN to authorize remote processing is proportionate to the stated purpose.

Instruction Scope

Instructions tell the agent to upload user video files and to create/maintain session tokens, poll render status, and return download URLs — all expected for a remote render service. This necessarily transmits user media to an external domain (mega-api-prod.nemovideo.ai); the README warns about not printing tokens. No instructions ask the agent to read unrelated system secrets or other services.

Install Mechanism

There is no install spec and no code files; this is instruction-only, so nothing is written to disk by the skill itself. Low install risk.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which matches the API Authorization header usage. Metadata also lists a config path (~/.config/nemovideo/) and the skill references detecting install paths for attribution — reading those paths is plausible but not strictly necessary for core functionality. No unrelated credentials are requested.

Persistence & Privilege

always is false and autonomous invocation is the platform default. The skill does not request permanent presence or modify other skills/configurations.

Assessment

This skill will upload your raw video files to a third-party API (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN (or it can obtain an anonymous token for short-term use). That behavior is expected for cloud rendering but means your media and any metadata will leave your machine. Before installing, verify you trust the nemo service (privacy policy, retention, and security practices), avoid sending sensitive videos, and avoid reusing high-privilege tokens for NEMO_TOKEN. If you need offline editing or strict data residency, do not use this skill.

Getting Started

Share your raw video clips and I'll get started on AI style enhancement. Or just tell me what you're thinking.

Try saying:

• "transform my raw video clips"
• "export 1080p MP4"
• "add bold color grading, dynamic cuts,"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Spicy AI Video — Make Videos Bold and Vivid

Send me your raw video clips and describe the result you want. The AI style enhancement runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 60-second talking head clip, type "add bold color grading, dynamic cuts, and energetic music to make this video pop", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds get the most consistent style results.

Matching Input to Actions

User prompts referencing spicy ai video, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip SSE?
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"	→ §3.3 Credits	✅
"status" / "状态" / "show tracks"	→ §3.4 State	✅
"upload" / "上传" / user sends file	→ §3.2 Upload	✅
Everything else (generate, edit, add BGM…)	→ §3.1 SSE	❌

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: spicy-ai-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add bold color grading, dynamic cuts, and energetic music to make this video pop" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "add bold color grading, dynamic cuts, and energetic music to make this video pop" → Download MP4. Takes 30-60 seconds for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.