Viral Team Video

Get shareable team clips ready to post, without touching a single slider. Upload your raw team footage (MP4, MOV, AVI, WebM, up to 500MB), say something like...

Security Scan

The skill's behaviour mostly matches a cloud video-editing tool, but there are small inconsistencies (metadata vs. skill frontmatter) and runtime instructions that deserve attention before installing or using it.

Purpose & Capability

Name/description match the runtime instructions: the skill uploads user video to a remote nemovideo.ai backend, creates editing jobs, and returns downloadable MP4s. Declared primary credential (NEMO_TOKEN) is consistent with a hosted service. Minor incoherence: registry metadata lists no required config paths, while the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/).

Instruction Scope

SKILL.md stays inside the video-editing scope: it instructs session creation, SSE message flow, uploads, polling render status, and downloading results. It will upload user files to an external service (expected for this purpose). The instructions also ask the agent to derive an X-Skill-Platform header from the agent's install path (checking ~/.clawhub/ or ~/.cursor/skills/), which requires reading filesystem paths that are not strictly necessary for editing and is worth noting.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an installer step.

Credentials

Only NEMO_TOKEN is declared as required, which fits a hosted video API. However, SKILL.md instructs that if NEMO_TOKEN is absent it will request an anonymous token from the API (POST to /api/auth/anonymous-token). That makes the declared required env var less strict than advertised. Also the frontmatter's configPaths (present in SKILL.md) are not reflected in the registry 'Required config paths: none' field — a minor inconsistency that could imply the skill expects or may read a local nemovideo config directory.

Persistence & Privilege

always is false and autonomous invocation is allowed by default — standard for skills. The skill does not request persistent system-wide privileges or attempt to modify other skills' configuration in its instructions.

What to consider before installing

This skill routes uploaded videos to a third‑party backend (mega-api-prod.nemovideo.ai). Before using it: (1) Don’t upload confidential or sensitive footage you wouldn’t want sent to an external service. (2) Understand NEMO_TOKEN: you can either supply your own token or the skill will obtain an anonymous 7‑day token automatically — if you prefer control, provide your own token and verify its scope. (3) Note the skill may read certain local paths to set an attribution header (it infers X-Skill-Platform from install paths and the SKILL.md mentions a config directory) — if you’re concerned about local info disclosure, ask for clarification or run in a restricted environment. (4) Because there’s no homepage or vendor info, consider validating the service (domain ownership, privacy/TOS) before sending production or sensitive content. If you need higher assurance, request full network request logs or an explicit statement from the publisher about what it stores and for how long.

Getting Started

Ready when you are. Drop your raw team footage here or describe what you want to make.

Try saying:

• "create a 3-minute behind-the-scenes team recording into a 1080p MP4"
• "cut the highlights, add upbeat music, and format for social media sharing"
• "turning team moments into shareable social media videos for marketers and team managers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Viral Team Video — Turn Team Footage Into Shareable Clips

This tool takes your raw team footage and runs AI viral video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute behind-the-scenes team recording and want to cut the highlights, add upbeat music, and format for social media sharing — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keep source clips under 90 seconds for the fastest turnaround.

Matching Input to Actions

User prompts referencing viral team 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is viral-team-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

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.

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "cut the highlights, add upbeat music, and format for social media sharing" → Download MP4. Takes 1-2 minutes 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the highlights, add upbeat music, and format for social media sharing" — 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 LinkedIn, Instagram, and Slack.