Minecraft Parkour Video Maker Free

Skip the learning curve of professional editing software. Describe what you want — cut failed jumps, add speed ramps on clean runs, and sync cuts to the beat...

Security Scan

The skill's behavior mostly matches an online video-editing service, but metadata inconsistencies and an unknown source make it worth caution before installing.

Purpose & Capability

The skill claims to perform cloud AI video editing and only requests a single API credential (NEMO_TOKEN), which is coherent with a cloud service. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — that's an internal inconsistency that could affect what the agent will try to read.

Instruction Scope

The instructions are focused on uploading video files and driving a remote rendering API (session, upload, SSE, export). They do not instruct reading arbitrary local files or unrelated environment variables. They do require adding custom attribution headers on every request and ask to 'auto-detect' install platform from the install path (this could cause the agent to examine its install path), which is out-of-band of simple upload/edit flows and worth noting.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes disk-write and supply-chain risk.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv), which fits a cloud API. But the SKILL.md frontmatter also references a config path (~/.config/nemovideo/) that could contain credentials; the registry stated 'Required config paths: none' — this mismatch is concerning. If the agent were to access that config path it could read stored tokens. Also the skill instructs how to mint an anonymous token via the service; ensure you use the short-lived anonymous token rather than a long-lived personal secret.

Persistence & Privilege

always is false and the skill is user-invocable; autonomous invocation is allowed (platform default). The skill does not request persistent/always-on presence or system-wide configuration changes.

What to consider before installing

This skill appears to be a front-end for a cloud video-editing API and largely behaves as described, but exercise caution: the publisher is unknown and the SKILL.md frontmatter conflicts with registry metadata about config paths. Before installing: (1) verify the skill's origin or prefer a published/homepage-backed alternative; (2) do not set a highly privileged or long-lived personal token as NEMO_TOKEN — prefer the anonymous, short-lived token flow described; (3) avoid uploading sensitive or private footage until you've verified the service's privacy/TOS; (4) check whether the agent will read ~/.config/nemovideo/ (if present) and remove or audit any secrets there; (5) consider running the skill in a sandboxed environment or limiting the agent's network access if possible. If you want more confidence, ask the publisher for a homepage, source repository, or a privacy/TOS link and confirm why the frontmatter configPaths differ from registry metadata.

Getting Started

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

Try saying:

• "edit my gameplay video clips"
• "export 1080p MP4"
• "cut failed jumps, add speed ramps"

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.

Minecraft Parkour Video Maker Free — Edit and Export Parkour Videos

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

Say you have a 2-minute Minecraft parkour screen recording and want to cut failed jumps, add speed ramps on clean runs, and sync cuts to the beat — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: trim your clip to the best runs before uploading so the AI focuses on your highlights.

Matching Input to Actions

User prompts referencing minecraft parkour video maker free, 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	minecraft-parkour-video-maker-free
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.

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

Common Workflows

Quick edit: Upload → "cut failed jumps, add speed ramps on clean runs, and sync cuts to the beat" → 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 failed jumps, add speed ramps on clean runs, and sync cuts to the beat" — 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, TikTok, and Discord.