Zen Creator

mindfulness creators create raw video footage into focused edited clips using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPUs at 1...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-editing service: it needs a single API token, uploads user video to nemovideo's API, and has no install step — but it will send your video and session data off-platform, so review privacy before use.

Purpose & Capability

Name/description (cloud GPU video editing) align with the declared requirement (NEMO_TOKEN) and the SKILL.md which calls nemovideo.ai endpoints. No unrelated credentials or binaries are requested.

Instruction Scope

SKILL.md instructs the agent to obtain/use NEMO_TOKEN (env or anonymous-token endpoint), create sessions, upload user video files, stream SSE chat, poll export status, and return download URLs. These actions are within the skill's stated purpose but do involve uploading user media and metadata to https://mega-api-prod.nemovideo.ai and making repeated network calls; the agent will also add skill-specific attribution headers to every request.

Install Mechanism

Instruction-only skill with no install spec and no code files — minimal disk footprint and no arbitrary archive downloads. Low install risk.

Credentials

Only NEMO_TOKEN is required (declared primary credential) which is appropriate. Minor inconsistency: registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That could indicate the skill expects to read/write session or config data locally; it's not malicious but worth clarifying.

Persistence & Privilege

always:false and no install means the skill does not demand permanent presence or elevated privileges. The skill can be invoked autonomously (default), which is normal; consider this if you want to restrict autonomous network uploads of user media.

Assessment

This skill will upload any video you send to mega-api-prod.nemovideo.ai and requires an API token (NEMO_TOKEN). It can generate a short-lived anonymous token for you automatically. Before using: (1) confirm you are comfortable with your videos and metadata leaving your device and being processed by nemovideo.ai; (2) avoid sending sensitive footage; (3) consider using a throwaway/anonymous token if you want to limit linkage to your account; (4) note the SKILL.md lists a local config path (~/.config/nemovideo/) even though the registry didn't — ask the publisher where session data is stored; (5) if you need higher assurance, request the skill's source/homepage or test with a small non-sensitive clip first. If you want help drafting a privacy-check question to ask the skill author or testing steps, tell me what you'd like to verify.

Getting Started

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

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "remove background noise, add smooth transitions,"

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.

Zen Creator — Create Calm Focused Videos

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

Here's a typical use: you send a a 3-minute vlog recorded on a smartphone, ask for remove background noise, add smooth transitions, and keep only the calm focused moments, 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 — shorter clips under 2 minutes process noticeably faster and keep the zen feel intact.

Matching Input to Actions

User prompts referencing zen creator, 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	zen-creator
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 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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "remove background noise, add smooth transitions, and keep only the calm focused moments" — 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 YouTube, Instagram, and meditation platforms.

Common Workflows

Quick edit: Upload → "remove background noise, add smooth transitions, and keep only the calm focused moments" → 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.