Pika Ai Video Generator

Cloud-based pika-ai-video-generator tool that handles generating short AI videos from text or image prompts. Upload JPG, PNG, MP4, MOV files (up to 200MB), d...

Security Scan

The skill mostly matches a cloud video-generator but contains inconsistencies and a few instruction choices (auto-generating/storing tokens, hiding responses, and fingerprinting install paths) that are disproportionate or unclear.

Purpose & Capability

The declared purpose (cloud AI video generation) aligns with the API endpoints and the single required credential (NEMO_TOKEN). However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — a minor inconsistency in what the skill claims it needs.

Instruction Scope

Runtime instructions include auto-creating anonymous tokens if NEMO_TOKEN is not present, storing a session_id for later use, and explicitly instruct the agent not to display raw API responses or token values. The skill also instructs uploading files by local path (multipart -F "files=@/path"), and adds headers that leak install-path-derived platform info. These behaviors broaden the agent's actions (creating credentials, storing session state, reading local file paths, and sending environment/hardware-fingerprint-like headers) beyond a minimal request/response workflow and are not fully justified or explained.

Install Mechanism

Instruction-only skill with no install spec or bundled code; nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is proportionate for a cloud API. But the SKILL.md instructs generating and storing anonymous tokens when the env var is absent and includes a configPaths entry in frontmatter — the storage location and lifetime of session/token are unspecified, and the automatic creation/storage behavior should be clarified before trust.

Persistence & Privilege

always:false and normal autonomous invocation. The skill instructs an automatic first-time backend connection and to 'store the returned session_id' but does not say where; this raises a small persistence/privilege question (where/how long session data is kept). No explicit requests to modify other skills or system-wide config were found.

What to consider before installing

This skill appears to be a legitimate cloud video generator, but there are some things to check before installing/using it: 1) The skill will auto-create an anonymous token if you don't provide NEMO_TOKEN — ask where that token and session_id are stored and how long they're valid. 2) The runtime tells the agent to hide raw API responses and token values; lack of visible responses can be used to obscure unexpected behavior. 3) The skill adds headers that reveal install-path-derived platform info and may request file uploads by local path — ensure you only upload intended media and not sensitive filesystem paths. 4) The source is unknown and homepage is missing; prefer skills from verified authors or ask the publisher for provenance and a privacy/data-retention policy. If you proceed, provide your own NEMO_TOKEN (ephemeral/scoped if possible), avoid uploading sensitive files, and ask the maintainer to clarify storage location for session tokens and the reason for the configPath/frontmatter discrepancy.

Getting Started

Got text prompts or images to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

• "generate a text prompt describing a sunset over mountains into a 1080p MP4"
• "generate a 5-second cinematic clip of a futuristic city at night"
• "generating short AI videos from text or image prompts for content creators and marketers"

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.

Pika AI Video Generator — Generate AI Videos from Prompts

Drop your text prompts or images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a text prompt describing a sunset over mountains, ask for generate a 5-second cinematic clip of a futuristic city at night, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, specific prompts produce more consistent and accurate results.

Matching Input to Actions

User prompts referencing pika ai video generator, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is pika-ai-video-generator, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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.

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.

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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 5-second cinematic clip of a futuristic city at night" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, MP4, MOV for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "generate a 5-second cinematic clip of a futuristic city at night" → 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.