Video To Text Extract Free

Get plain text transcript ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "ex...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video→text transcription tool, but there are a few minor metadata mismatches and privacy/storage details you should confirm before installing.

Purpose & Capability

Name/description (video→text transcription) align with the declared primary credential (NEMO_TOKEN) and the SKILL.md instructions, which call a nemovideo.ai cloud API for upload, SSE chat, session management and export. No unrelated credentials or binaries are requested.

Instruction Scope

Runtime instructions stay within the stated purpose (creating sessions, uploading video, polling for render results, reading SSE). The skill explicitly instructs how to obtain an anonymous token if NEMO_TOKEN is not present, how to set headers, and to store the session_id. It also tells the agent not to display raw token/API responses. This is expected, but the instructions implicitly require uploading the user's video files to an external service (mega-api-prod.nemovideo.ai) — a clear privacy implication the user should be aware of.

Install Mechanism

No install spec and no code files (instruction-only). Lowest-risk installation surface — nothing is written to disk by an installer step. All runtime network actions are described in SKILL.md.

Credentials

Only NEMO_TOKEN is declared as the primary credential, which is appropriate for a hosted transcription service. SKILL.md describes auto-obtaining a short-lived anonymous token if none is present. There is an inconsistency: registry metadata (provided earlier) lists no required config paths, but the SKILL.md frontmatter mentions configPaths (~/.config/nemovideo/). That mismatch should be clarified. Storing tokens or session IDs in environment or config directories is sensitive and should be documented.

Persistence & Privilege

always:false (not force-enabled). The skill asks only to store a session_id (and possibly token) for use with the service; it does not request system-wide privileges or to modify other skills. No evidence it modifies other agent settings.

Assessment

This skill behaves like a normal cloud transcription tool: it will upload any video you provide to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or create a short-lived anonymous token) to process it. Before installing, confirm: (1) you are comfortable with your video content being sent to that external service and have reviewed its privacy/terms; (2) where and how the skill will persist the anonymous token or session_id (environment variable vs ~/.config/nemovideo/) — there is a metadata mismatch in the registry vs SKILL.md that should be clarified; (3) whether the skill will read the agent install path when setting X-Skill-Platform (this may require minimal filesystem queries). If you need to handle sensitive or regulated data, do not use this skill until you have explicit documentation from the skill author about storage, retention, and data handling policies.

Getting Started

Share your video files and I'll get started on AI text extraction. Or just tell me what you're thinking.

Try saying:

• "extract my video files"
• "export 1080p MP4"
• "extract all spoken words from this"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video To Text Extract Free — Extract Text From Any Video

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

Say you have a 10-minute lecture recording in MP4 and want to extract all spoken words from this video as a text transcript — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes produce the most accurate transcripts.

Matching Input to Actions

User prompts referencing video to text extract 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	video-to-text-extract-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

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 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 "extract all spoken words from this video as a text transcript" — concrete instructions get better results.

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

MP4 files with clear audio yield the best transcription results.

Common Workflows

Quick edit: Upload → "extract all spoken words from this video as a text transcript" → Download MP4. Takes 30-90 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.