Video Editing With Canva Ai

Get polished edited videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, AVI, WebM, up to 500MB), say somethi...

Security Scan

The skill's instructions mostly match a cloud-based video-editing integration but there are inconsistencies (branding, metadata, and a hidden config path) you should understand before installing or using it.

Purpose & Capability

The skill is named and marketed as "Canva AI" editing, but all runtime instructions target a different backend (mega-api-prod.nemovideo.ai / Nemo). That brand/endpoint mismatch is misleading. The SKILL.md frontmatter also declares a config path (~/.config/nemovideo/) that is not listed in the registry requirements shown to you, which is an inconsistency between declared metadata and the runtime instructions.

Instruction Scope

The instructions are explicit about network calls (session creation, SSE for edits, uploads, render polling) and only require an API token or an anonymous-token flow. These actions are coherent for a cloud video-editing service. Two items to note: (1) the skill tells the agent to include attribution headers and auto-detect an install path (may require reading environment/install path), and (2) uploads are done via multipart referencing local file paths — the agent will send whatever files the user supplies to the external service, so users should expect their video/audio files to leave the machine.

Install Mechanism

There is no install spec and no code files — this is an instruction-only skill. That minimizes on-disk code risk because nothing is downloaded or written by the skill package itself.

Credentials

Only a single credential is required (NEMO_TOKEN), which matches the API usage. However, SKILL.md also lists a config path (~/.config/nemovideo/) in its frontmatter; the registry metadata you were shown did not require config paths. If the agent reads that config path it could access local stored credentials or settings, so the discrepancy should be clarified.

Persistence & Privilege

The skill is not 'always' enabled and allows user invocation; it does not request elevated or persistent platform privileges. Autonomous invocation is allowed (platform default) but not combined with other high-privilege indicators.

What to consider before installing

This skill appears to route video editing to a Nemo backend, not Canva, so verify you are comfortable uploading your media to https://mega-api-prod.nemovideo.ai before using it. Confirm whether the "Canva AI" branding is accurate or misleading. Ask the publisher to explain the config-path entry in the SKILL.md frontmatter (~/.config/nemovideo/) and why that path was omitted from the registry requirements shown to you. If you proceed: (1) only provide media you are willing to upload to a third-party cloud service, (2) prefer using an anonymous token for short tests (it grants limited credits), and (3) do not install or expose any unrelated credentials—NEMO_TOKEN is sufficient for this skill. If you need higher assurance, request the publisher's source or an official integration reference that ties the branding to the actual backend.

Getting Started

Share your video clips or images and I'll get started on AI-assisted video editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips or images"
• "export 1080p MP4"
• "add text overlays, transitions, and background"

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 Editing with Canva AI — Edit and Export Canva AI Videos

This tool takes your video clips or images and runs AI-assisted video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second product clip recorded on a smartphone and want to add text overlays, transitions, and background music in Canva AI style — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and yield cleaner AI edits.

Matching Input to Actions

User prompts referencing video editing with canva ai, 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.

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

Header	Value
X-Skill-Source	video-editing-with-canva-ai
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add text overlays, transitions, and background music in Canva AI style" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest compatibility across platforms.

Common Workflows

Quick edit: Upload → "add text overlays, transitions, and background music in Canva AI style" → 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.