Higgsfield Free Video Generation

generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating shor...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-generation integration: it needs a NEMO_TOKEN (or will fetch an anonymous token), talks to nemovideo.ai endpoints, and has no install steps or unrelated credential asks.

Purpose & Capability

Name/description (AI video generation) maps to the declared primaryEnv (NEMO_TOKEN) and the SKILL.md endpoints (nemovideo.ai). The network calls, session creation, upload, SSE, and export flows are all coherent with a remote render service. One minor inconsistency: the registry summary listed no required config paths, but the SKILL.md frontmatter metadata includes configPaths: ["~/.config/nemovideo/"]. This is inconsequential for core functionality but is an inconsistency to note.

Instruction Scope

SKILL.md explicitly instructs the agent to check for NEMO_TOKEN, or otherwise generate an anonymous token via POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token, create sessions, upload files, poll render status, and use SSE for edits. Those instructions stay within the stated purpose. The skill requires attribution headers and platform-detection for requests; that is implementation-specific but not out-of-scope. The instructions do not direct reading unrelated system files or broad data exfiltration.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. No downloads or archive extraction are prescribed.

Credentials

Only NEMO_TOKEN is declared as required and is appropriate for the backend API. The skill also documents how to obtain an anonymous token automatically if NEMO_TOKEN is absent; this network action is consistent with providing a frictionless demo flow. No unrelated secrets or multiple credential requests are present.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. However, the SKILL.md frontmatter's configPaths entry (~/.config/nemovideo/) (present in the skill text but absent from the registry summary) suggests a capability to reference a local config file. The runtime instructions do not mandate arbitrary system changes, but if the agent were to read that path it could surface stored tokens or settings — verify whether the agent will actually access that directory before installing.

Assessment

This skill appears internally consistent for a cloud AI-video integration. Before installing, consider: (1) Confirm you trust the external service domain (mega-api-prod.nemovideo.ai) since uploads and generated videos are sent there; (2) Understand the skill will use or obtain a NEMO_TOKEN (it can generate an anonymous token via the public endpoint) — anonymous tokens have limited credits and can be consumed; (3) Ask the publisher why the SKILL.md frontmatter lists a local config path (~/.config/nemovideo/) while the registry summary shows none — if you are uncomfortable, ensure the agent is not permitted to read your home config dirs; (4) Check privacy/terms for any sensitive media you upload. If you want a tighter audit, request the exact network request/response examples and whether the agent will read local config files at runtime.

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

• "generate a short text description of a scene into a 1080p MP4"
• "generate a cinematic video clip of a sunset over the ocean from a text prompt"
• "generating short videos from text prompts without a paid Higgsfield subscription for content creators"

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.

Higgsfield Free Video Generation — Generate AI Videos From Text

Send me your text prompts 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 short text description of a scene, type "generate a cinematic video clip of a sunset over the ocean from a text prompt", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: shorter, more specific prompts tend to produce more accurate and usable video results.

Matching Input to Actions

User prompts referencing higgsfield free video generation, 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	higgsfield-free-video-generation
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 → "generate a cinematic video clip of a sunset over the ocean from a text prompt" → Download MP4. Takes 1-3 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 "generate a cinematic video clip of a sunset over the ocean from a text prompt" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and editors.