Influencer Video Skill

Get polished influencer clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say somethin...

Security Scan

The skill's instructions match its stated video-editing purpose and only require a single service token, but there are small metadata inconsistencies and a potential config-path reading that deserve caution before installing.

Purpose & Capability

Name/description, runtime instructions, and required credential (NEMO_TOKEN) align with a cloud video-editing service. However, SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry summary; that mismatch should be resolved (either the skill will read a user config dir or it will not).

Instruction Scope

Instructions are specific to the described cloud render workflow (token check/creation, session creation, upload, SSE chat, export polling). They do not instruct the agent to read unrelated system files or to exfiltrate data unrelated to uploaded media. They do require the agent to detect an 'install path' for the X-Skill-Platform header, which implies some minimal filesystem/installation-path inspection but nothing else arbitrary.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by the skill itself, which is the lower-risk model.

Credentials

The skill declares a single required secret (NEMO_TOKEN), which is proportionate for a cloud editing service. Caveat: SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) which could contain credentials or settings; the registry metadata shown earlier listed no config paths. If the skill will read that path it increases sensitivity and should be explicitly documented. Also, anonymous-token creation via the service endpoint is allowed by the instructions — that will create a short-lived token on behalf of the agent if no NEMO_TOKEN is provided.

Persistence & Privilege

The skill is not always-enabled and uses default model-invocation behavior. It does not request permanent system presence or permission to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says: it uploads media to a third‑party cloud service and returns edited video files. Before installing, consider: - Trust and privacy: uploads (raw footage) will be sent to mega-api-prod.nemovideo.ai — verify you trust that domain and review its privacy/terms if your footage is sensitive. - Credential scope: NEMO_TOKEN is the only credential requested. Prefer using an anonymous or limited account rather than a personal account with broad permissions. The skill will auto-create a short-lived anonymous token if none is provided. - Metadata mismatch: SKILL.md references ~/.config/nemovideo/ in frontmatter but registry metadata did not list config paths — confirm whether the skill will read that directory (it could contain tokens or config). - Minimal filesystem access: the skill asks you to auto-detect an install path for the X-Skill-Platform header — that may involve checking where the agent is installed; ensure no other local files are accessed. If you cannot confirm the service/domain and the config-path behavior, treat this as untrusted and avoid uploading sensitive video until you verify the vendor and token scope.

Getting Started

Share your raw video footage and I'll get started on AI content editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the pauses, add captions, and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Influencer Video Skill — Edit and Export Creator Videos

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

Say you have a 60-second unedited phone recording and want to cut the pauses, add captions, and overlay background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: vertical 9:16 video works perfectly for Reels and TikTok exports.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	influencer-video-skill
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 pauses, add captions, and overlay background music" → 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 pauses, add captions, and overlay background music" — 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 all social platforms.