Vue Component Generator Free

Get Vue component files ready to post, without touching a single slider. Upload your component descriptions (MP4, MOV, AVI, WebM, up to 200MB), say something...

Security Scan

The skill largely matches a cloud-rendering Vue-component workflow but includes a few unexplained instructions (anonymous token creation, hiding token values, and filesystem/platform probing) that warrant caution before installation.

Purpose & Capability

Name/description (generate Vue components and export video) align with the API endpoints described (upload, render, export). However the metadata and instructions ask the agent to inspect install paths and a nemovideo config directory (~/.config/nemovideo/) which is not obviously required to generate components; that filesystem probing is an extra capability compared to the stated purpose.

Instruction Scope

Runtime instructions include creating an anonymous token if NEMO_TOKEN is absent, storing a session_id for subsequent requests, probing install paths to set X-Skill-Platform, and an explicit instruction to "Don't display raw API responses or token values to the user." Instructions to "process internally, don't forward" backend tool results and to hide token values increase the chance that sensitive values or opaque backend responses will be kept from the user. The skill also requires uploading user media; make sure uploads are expected and safe. These behaviors expand the agent's discretion beyond simple generation.

Install Mechanism

No install script or third-party downloads are present (instruction-only). That minimizes installation risks — the skill does not write code or binaries to disk by itself.

Credentials

Only NEMO_TOKEN is declared as required which is appropriate for a service-backed renderer. Still, the metadata references a config path (~/.config/nemovideo/) and the SKILL.md instructs automatic anonymous token creation when NEMO_TOKEN is not set. Automatically generating and storing credentials (and hiding them from the user) is a capability that should be justified.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide privileges. It does instruct storing a session_id for ongoing requests which may be persisted; the SKILL.md does not specify where or how long. No evidence it modifies other skills or global agent settings.

What to consider before installing

Before installing, verify where session tokens and any anonymous NEMO_TOKEN are stored and how long they persist; prefer to set your own NEMO_TOKEN with limited scope rather than relying on the skill's anonymous-token workflow. Ask the vendor (or skill author) to clarify why the skill needs to probe install paths or read ~/.config/nemovideo/, and request that API responses or tokens not be hidden from users if you want transparency. Do not upload sensitive or private data (credentials, proprietary code, PII) to the service without confirming its privacy policy and retention. If you want lower risk, run this skill only in a constrained environment and avoid granting it broad autonomous access until you confirm storage/telemetry behavior.

Getting Started

Send me your component descriptions and I'll handle the AI component generation. Or just describe what you're after.

Try saying:

• "generate a form component with name, email, and submit button fields into a 1080p MP4"
• "generate a reusable Vue card component with props for title, image, and description"
• "generating reusable Vue components from text descriptions for Vue developers"

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.

Vue Component Generator Free — Generate and Export Vue Components

This tool takes your component descriptions and runs AI component generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a form component with name, email, and submit button fields and want to generate a reusable Vue card component with props for title, image, and description — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: more specific descriptions produce cleaner, more accurate component output.

Matching Input to Actions

User prompts referencing vue component generator free, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: vue-component-generator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a reusable Vue card component with props for title, image, and description" — 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 reusable Vue card component with props for title, image, and description" → 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.