Pika Ai

v1.0.0

generate text or images into AI generated clips with this pika-ai skill. Works with MP4, PNG, JPG, WebM files up to 200MB. content creators use it for genera...

0· 101·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dsewell-583h0/pika-ai.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pika Ai" (dsewell-583h0/pika-ai) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/pika-ai
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 pika-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install pika-ai
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description, endpoints, and the required NEMO_TOKEN align: the skill talks to nemovideo.ai to create sessions, upload media, and render videos. One minor inconsistency: the registry metadata lists no required config paths, but the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/). This is likely non-critical but should be reconciled.
Instruction Scope
SKILL.md stays on-topic: it only describes creating/refreshing a session token, posting uploads, streaming SSE, polling job state, and returning download URLs. It instructs the agent to generate a UUID for anonymous auth and to avoid exposing tokens. The skill also asks to derive an X-Skill-Platform header by detecting install path (reads install path conventions) — this requires some local path inspection but is limited in scope and understandable for attribution headers.
Install Mechanism
There is no install spec and no code files — instruction-only. This minimizes disk-write/execution risk.
Credentials
The only credential required is NEMO_TOKEN (primaryEnv). The SKILL.md also documents obtaining an anonymous token from the provider if the env var is absent. No unrelated secrets or multiple credentials are requested.
Persistence & Privilege
always is false and the skill does not request system-wide changes or access to other skills' configs. It keeps session_id/token for its own operations (normal). Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears to do what it says: it sends images/text to a remote backend (mega-api-prod.nemovideo.ai) to generate 1080p MP4s and needs a NEMO_TOKEN (it can also obtain a short-lived anonymous token). Before installing, consider: 1) you will be uploading media (up to 200MB) to an external service—do not upload sensitive content you wouldn't want sent off-system; 2) the skill may inspect the agent install path to set an attribution header (reads local path conventions) — this is low-risk but note it reads local path information; 3) the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while registry metadata omitted it — ask the publisher to clarify whether the skill will read or write that directory; 4) anonymous tokens expire after ~7 days and exports may be blocked by subscription/credit rules described in the doc. If you do not trust nemovideo.ai or cannot accept uploading your media, do not enable the skill. If you need higher assurance, request a homepage, privacy policy, or publisher verification (owner identity) before proceeding.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk974y440g8pmk7das8a99e6j6984kkca
101downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "generate my text or images"
  • "export 1080p MP4"
  • "animate this image into a 3-second"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

  • Generate a UUID as client identifier
  • POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
  • Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Pika AI — Generate Videos from Images

Send me your text or images and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a still photo of a city street, type "animate this image into a 3-second cinematic video clip", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: shorter, specific text prompts produce more predictable and usable results.

Matching Input to Actions

User prompts referencing pika ai, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is pika-ai, 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).

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

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate 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.

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

Common Workflows

Quick edit: Upload → "animate this image into a 3-second cinematic video clip" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "animate this image into a 3-second cinematic video clip" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Comments

Loading comments...