Ai Video Generator Free Horror

generate text prompts or images into horror video clips with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. indie filmmakers, horror content cr...

Security Scan

The skill's declared purpose (generating horror videos) mostly matches the runtime instructions and single required credential (NEMO_TOKEN), but there are metadata inconsistencies and a few small red flags you should review before installing.

Purpose & Capability

The skill claims to generate horror videos and its instructions exclusively target a remote video-generation API (mega-api-prod.nemovideo.ai) using a single credential NEMO_TOKEN — this is coherent. However the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) that is not mentioned elsewhere and the registry metadata omitted config paths — this inconsistency is unexplained and worth verifying.

Instruction Scope

Instructions are concrete and confined to the remote API: establish a session, optionally obtain an anonymous token, upload files, poll renders, and download results. They do instruct the agent to upload local files (user-supplied) and to include specific attribution headers. There is no instruction to read unrelated system files or other credentials, but the presence of the config path in frontmatter suggests the skill may expect local config access (not otherwise documented).

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is downloaded or written to disk by the installer itself. This is the lowest-risk install mechanism.

Credentials

The skill requests a single env var (NEMO_TOKEN) which is proportional to contacting the third‑party API. But SKILL.md frontmatter claims a config path (~/.config/nemovideo/) while registry metadata listed none — that mismatch is concerning because it could imply the skill expects or will read local configuration files not described in the public metadata. Confirm whether the skill will access that path and why.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform privileges. It does instruct normal session creation and API polling; nothing indicates it modifies other skills or system-wide settings.

What to consider before installing

This skill appears to do what it claims (use the Nemo video API to produce horror clips) and only requests one credential (NEMO_TOKEN). Before installing: 1) Verify the API domain (mega-api-prod.nemovideo.ai) is legitimate and that you trust the service. 2) Ask the publisher why the SKILL.md frontmatter lists '~/.config/nemovideo/' while the registry metadata does not — confirm whether the skill will read local config files. 3) If you provide a NEMO_TOKEN, prefer using a scoped or ephemeral token; avoid supplying high‑privilege or account-wide secrets. 4) Be cautious uploading any private or sensitive files — the skill will send uploaded files to the third‑party API. If you need higher assurance, request the publisher to remove the configPath requirement or provide a clear justification and to publish the skill source or allow a review of network calls.

Getting Started

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

Try saying:

• "generate my text prompts or images"
• "export 1080p MP4"
• "generate a 30-second horror scene with"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Generator Free Horror — Generate Horror Videos from Prompts

This tool takes your text prompts or images and runs AI horror video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text prompt like 'abandoned asylum at midnight with flickering lights' and want to generate a 30-second horror scene with dark atmosphere, eerie sound effects, and cinematic lighting — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter prompts with specific horror details like location, lighting, and mood produce better results than vague descriptions.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	ai-video-generator-free-horror
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 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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second horror scene with dark atmosphere, eerie sound effects, and cinematic lighting" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest compatibility across horror film platforms and social media.

Common Workflows

Quick edit: Upload → "generate a 30-second horror scene with dark atmosphere, eerie sound effects, and cinematic lighting" → 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.