React Component Generator Online

Get coded component videos ready to post, without touching a single slider. Upload your component description text (MP4, MOV, AVI, WebM, up to 200MB), say so...

Security Scan

The skill is internally consistent with its description: it connects to a nemovideo cloud API and requires a single NEMO_TOKEN (it can obtain an anonymous one), and there are no surprising installs or unrelated credential requests.

Purpose & Capability

The skill's name/description (generate React-component preview videos) aligns with the actions in SKILL.md: creating a session, uploading media, driving SSE-based generation, and exporting MP4s. The required environment variable (NEMO_TOKEN) is appropriate. Minor inconsistency: the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata reported no required config paths; this is likely benign but is a mismatch you may want clarified.

Instruction Scope

Instructions are scoped to the service: token acquisition (anonymous or provided), session creation, upload, SSE streaming, polling for render status, and returning download URLs. The skill does require reading/generating a client ID and may inspect install path to set the X-Skill-Platform header, which is reasonable for attribution but worth noting.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or fetched at install time. This is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is required and declared as primaryEnv, which matches the API usage. The SKILL.md also references a local config path (~/.config/nemovideo/) in its frontmatter — the registry said none — so the skill might read that path if present; this should be confirmed. No unrelated secrets (AWS, GitHub, etc.) are requested.

Persistence & Privilege

always is false and the skill does not request elevated, persistent platform-wide privileges or modify other skills. Autonomous invocation is allowed (default) but that is expected for skills that interact with a remote API.

Assessment

This skill appears to do what it says: it talks to a nemovideo backend, uploads media, and returns rendered MP4s. Before installing or using it, consider: (1) only the NEMO_TOKEN is needed — you can provide one or the skill will request an anonymous token — but avoid supplying any sensitive long-lived credentials; (2) your uploaded files will be sent to https://mega-api-prod.nemovideo.ai (check that you are comfortable sharing the content and review the service’s privacy/terms); (3) clarify the small metadata mismatch: SKILL.md mentions ~/.config/nemovideo/ (the registry did not), so ask whether the skill will read that local config directory; (4) revoke or rotate tokens after use if you suspect exposure. If you need higher assurance, ask the publisher for a privacy policy, a homepage, or a code release you can audit.

Getting Started

Share your component description text and I'll get started on AI code generation. Or just tell me what you're thinking.

Try saying:

• "generate my component description text"
• "export 1080p MP4"
• "generate a React button component with"

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.

React Component Generator Online — Generate React Components From Text

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

A quick example: upload a form component with email and password fields, type "generate a React button component with hover states and TypeScript props", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter, specific component descriptions produce cleaner and more accurate output.

Matching Input to Actions

User prompts referencing react component generator online, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send 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>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start 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.

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

Header	Value
X-Skill-Source	react-component-generator-online
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a React button component with hover states and TypeScript props" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a React button component with hover states and TypeScript props" → Download MP4. Takes 20-40 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.