Video Trimmer Canva

v1.0.0

Turn a 3-minute Canva-exported MP4 presentation into 1080p trimmed video clips just by typing what you need. Whether it's trimming and cutting Canva-exported...

⭐ 0· 70·0 current·0 all-time

by@whitejohnk-26

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for whitejohnk-26/video-trimmer-canva.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Video Trimmer Canva" (whitejohnk-26/video-trimmer-canva) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/video-trimmer-canva
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install video-trimmer-canva

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-trimmer-canva

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

The name/description (trim Canva-exported videos, server-side rendering) match the declared requirements: a single API token (NEMO_TOKEN) and an optional config path for nemovideo settings. No unrelated services, binaries, or odd dependencies are requested.

ℹ

Instruction Scope

The SKILL.md instructs the agent to read NEMO_TOKEN from the environment (or obtain an anonymous token by POSTing to the nemovideo API), create a session, upload files, stream SSE responses, and poll render status. It also requires reading the skill's YAML frontmatter to set attribution headers and references a config path (~/.config/nemovideo/) in metadata. These actions are expected for a cloud render service, but they do involve sending user media and session metadata to a third-party API.

✓

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk or downloaded by the skill itself, which minimizes install-time risk.

✓

Credentials

Only a single token (NEMO_TOKEN) is required as the primary credential; the skill falls back to requesting an anonymous short-lived token if none is present. The declared config path (~/.config/nemovideo/) is consistent with storing service credentials/caches. No unrelated secrets or multiple unrelated credentials are requested.

✓

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistent privileges. It reads its own frontmatter and may read a service config directory; it does not claim to modify other skills or global agent configuration.

Assessment

This skill will upload any video files you give it to https://mega-api-prod.nemovideo.ai for remote trimming and rendering. Before installing or using it: (1) confirm you are comfortable with that network transfer and the privacy policy of nemovideo.ai, (2) only provide an API token (NEMO_TOKEN) if that token is scoped for this service and not a broad or highly privileged credential, and (3) avoid uploading sensitive content unless you trust the remote service. If you prefer not to store a token in your environment, the skill will obtain a temporary anonymous token for short-term use, but uploaded media will still be transmitted to the remote API.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

✂️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97bkp08kmrz5h8mn8xep36vs184wdgh

70downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

"trim a 3-minute Canva-exported MP4 presentation into a 1080p MP4"
"trim the intro and outro, cut dead air between slides"
"trimming and cutting Canva-exported videos to remove unwanted sections for Canva users and social media creators"

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 Trimmer for Canva — Trim and Export Canva Videos

Send me your video clips and describe the result you want. The AI video trimming runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute Canva-exported MP4 presentation, type "trim the intro and outro, cut dead air between slides", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter source clips process faster — split long videos before uploading.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

X-Skill-Source: video-trimmer-canva
X-Skill-Version: from frontmatter version
X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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

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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro and outro, cut dead air between slides" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "trim the intro and outro, cut dead air between slides" → Download MP4. Takes 20-40 seconds 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.

Comments

Loading comments...