Podcast Video Free

Skip the learning curve of professional editing software. Describe what you want — turn my podcast audio into a video with waveform animation and captions —...

Security Scan

The skill generally matches a cloud-based podcast-to-video service (it asks for one API token and instructs uploading media), but there are small inconsistencies and unclear declarations that deserve caution before installing or using it.

Purpose & Capability

The stated purpose (convert podcast audio to video via cloud rendering) aligns with the declared primary credential (NEMO_TOKEN) and the SKILL.md instructions to call nemovideo.ai endpoints. However, the skill frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch is unexplained.

Instruction Scope

Runtime instructions are narrowly focused on (1) obtaining/using a NEMO_TOKEN, (2) creating a session, (3) uploading user media, (4) polling export status and returning download URLs. The skill explicitly instructs not to print tokens/raw JSON. It does perform file upload to an external API (expected for this purpose) and asks the agent to persist session IDs. It does not instruct reading unrelated system files or other credentials.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk install surface; nothing will be written to disk by an installer as part of skill installation.

Credentials

Only one credential (NEMO_TOKEN) is requested, which is proportional to a cloud conversion service. The concern is the unexplained inclusion of a config path (~/.config/nemovideo/) in the skill frontmatter metadata while the registry says 'no required config paths' — that suggests either stale metadata or an implicit expectation that the agent will read or write that directory (e.g., to persist tokens or sessions). The SKILL.md does tell the agent to 'save session_id' but doesn't specify where; this ambiguity could lead to persistent storage of tokens/sessions in an unexpected location.

Persistence & Privilege

always:false (no forced always-on) and model-invocation is permitted (platform default). The skill asks the agent to save session IDs and reuse or refresh tokens; that is normal for a cloud API client. There is no request to modify other skills or system-wide settings.

What to consider before installing

This skill appears to be a straightforward cloud-based podcast→video integration that needs a single API token and uploads your media to nemovideo.ai. Before installing or using it: (1) Confirm you trust the nemovideo.ai domain and its privacy policy because your audio files will be uploaded to that external service; (2) Use a throwaway/test NEMO_TOKEN or anonymous token for sensitive or private recordings; (3) Ask the skill author to clarify the config path behavior (~/.config/nemovideo/) and where session tokens will be stored, or expect tokens/sessions may be persisted locally; (4) Avoid supplying other unrelated credentials (AWS, Google, etc.); (5) If you need full assurance, request the author provide a minimal reproducible example or an official homepage/source so you can verify the backend and data-handling practices.

Getting Started

Share your audio or video files and I'll get started on AI podcast video creation. Or just tell me what you're thinking.

Try saying:

• "convert my audio or video files"
• "export 1080p MP4"
• "turn my podcast audio into a"

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.

Podcast Video Free — Convert Podcast Audio to Video

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

Say you have a 30-minute podcast audio recording in MP3 and want to turn my podcast audio into a video with waveform animation and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: trimming your audio to key highlights before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing podcast video 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Header	Value
X-Skill-Source	podcast-video-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "turn my podcast audio into a video with waveform animation and captions" → 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 "turn my podcast audio into a video with waveform animation and captions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across YouTube, Spotify Video, and social platforms.