Video News

Get broadcast-ready segments ready to post, without touching a single slider. Upload your raw news footage (MP4, MOV, MXF, AVI, up to 500MB), say something l...

Security Scan

The skill's declared purpose (cloud video editing) largely matches what it does (upload user videos to a third‑party API using NEMO_TOKEN), but there are inconsistent metadata fields, opaque runtime instructions, and a few odd/incoherent instruction fragments that warrant caution before installing.

Purpose & Capability

Name/description (video editing) aligns with required credential NEMO_TOKEN and the documented API endpoints for uploads and renders. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not present in the registry metadata, and the instructions ask the agent to detect an install path (to set X-Skill-Platform). These filesystem checks are not obviously required for editing and introduce a small mismatch between claimed requirements and runtime behavior.

Instruction Scope

The instructions tell the agent to read NEMO_TOKEN (expected) or obtain an anonymous token via an external POST (reasonable). They further instruct streaming SSE handling, polling, and uploading user media to https://mega-api-prod.nemovideo.ai — all expected for a cloud editor. Concerns: (1) SKILL.md says to 'keep the technical details out of the chat' which hides transmission/authorization steps from users; (2) the doc instructs the agent to detect install paths and include derived headers (requires filesystem awareness); (3) there's an odd truncated mapping ('click [button]' → 'Execute vi…') which looks incoherent and may indicate incomplete or incorrect instructions. The skill will upload user media to a third party — that is central to its function but requires explicit user consent and clear privacy/retention terms.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest filesystem/write risk. Nothing is downloaded or written by an installer according to the manifest.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for a cloud API. The SKILL.md also includes a mechanism to mint anonymous tokens if none are present. The frontmatter's configPaths entry (~/.config/nemovideo/) is declared in the skill file but not in registry metadata — this inconsistency suggests the skill may attempt to read a local config path even though the registry reported none.

Persistence & Privilege

always:false and no install operations. The skill does not request permanent presence or modifications to other skills. Note: the skill can be invoked autonomously by the agent (platform default) — combine that with the opaque 'keep technical details out of the chat' instruction and automated uploads to an external service, and you should consider whether you want the agent to run this skill without explicit per-use confirmation.

What to consider before installing

This skill appears to be a legitimate cloud video editor that uploads your footage to a third‑party API and needs a NEMO_TOKEN. Before installing or using it: (1) Confirm you are comfortable uploading potentially sensitive video to https://mega-api-prod.nemovideo.ai and ask for the provider's privacy/retention policy; (2) Prefer using an ephemeral / limited-scope token rather than a long-lived high-privilege secret; (3) Ask the publisher to explain the apparent metadata inconsistency (the SKILL.md frontmatter lists ~/.config/nemovideo/ while registry metadata lists no config paths) and to clarify why the skill needs to detect install paths; (4) Request clarification of the truncated/incoherent instruction fragment (the 'click [button]' → 'Execute vi…' line) — incomplete or incorrect runtime instructions could cause unexpected behavior; (5) If you require transparency, ask the publisher to remove the 'keep technical details out of the chat' requirement or to provide an explicit, user-visible upload/authorization confirmation step; (6) Avoid using this skill for highly sensitive footage until the above are resolved. If the publisher cannot clarify these items, treat the skill as higher risk and do not install or grant your real credentials.

Getting Started

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

Try saying:

• "edit a 2-minute raw broadcast clip into a 1080p MP4"
• "trim the footage, add lower-third captions, and export as a broadcast-ready news segment"
• "editing raw news footage into publishable video segments for journalists and news producers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video News — Edit News Clips for Broadcast

Drop your raw news footage in the chat and tell me what you need. I'll handle the AI news video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw broadcast clip, ask for trim the footage, add lower-third captions, and export as a broadcast-ready news segment, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — keeping clips under 3 minutes speeds up processing significantly.

Matching Input to Actions

User prompts referencing video news, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-news, 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).

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

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

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute export workflow

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)

Common Workflows

Quick edit: Upload → "trim the footage, add lower-third captions, and export as a broadcast-ready news segment" → 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 "trim the footage, add lower-third captions, and export as a broadcast-ready news segment" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest web and broadcast compatibility.