Generator Chrome Extension

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — generate a short promotional video from this webpage content — and get gen...

⭐ 0· 30·0 current·0 all-time

by@mory128

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mory128/generator-chrome-extension.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Generator Chrome Extension" (mory128/generator-chrome-extension) from ClawHub.
Skill page: https://clawhub.ai/mory128/generator-chrome-extension
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 generator-chrome-extension

ClawHub CLI

Package manager switcher

npx clawhub@latest install generator-chrome-extension

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

The name/description match the runtime instructions: the skill uploads browser content and calls a cloud video-render API (mega-api-prod.nemovideo.ai). Requesting a service token (NEMO_TOKEN) and allowing file uploads up to 500MB is proportionate to the stated purpose. However, SKILL.md frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths; also the skill declares NEMO_TOKEN as required but documents an anonymous-token fallback — these are inconsistent with the registry declarations.

Instruction Scope

Instructions tell the agent to obtain/use a bearer token, create sessions, upload user files, stream SSE responses, and include attribution headers. Those actions are coherent for video generation, but the doc also instructs to "Keep the technical details out of the chat," which could enable the agent to hide network activity (token acquisition, uploads) from the user. The anonymous-token flow (generate UUID → POST to /api/auth/anonymous-token) means the skill will reach out to an external service and automatically obtain credentials if none are supplied; this is functional but should be made explicit to users before uploads occur.

✓

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes local install risk; nothing will be written to disk by an installer as part of installation.

ℹ

Credentials

Requesting a single service token (NEMO_TOKEN) is appropriate for a cloud-rendering integration. Two issues: (1) SKILL.md frontmatter references a config path (~/.config/nemovideo/) suggesting the skill might read local config (the registry listing showed no config paths), and (2) the skill declares NEMO_TOKEN as required but describes an anonymous-token fallback — contradictory. Both should be clarified before trusting the skill with secrets or local config.

✓

Persistence & Privilege

The skill does not request always:true and has no install hooks; it does network requests but does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed by default (normal), so consider this in combination with the other noted concerns.

What to consider before installing

Before installing, consider the following: - This skill uploads user files (videos, images, audio) and sends them to https://mega-api-prod.nemovideo.ai for cloud rendering. Don’t upload sensitive or private files unless you trust that domain/service. - The skill declares NEMO_TOKEN as the primary credential but also documents an anonymous-token fallback flow (it will generate a UUID and POST to obtain a temporary token). That means the agent may obtain credentials and contact the remote API automatically if you don’t provide a token — be aware of automatic network requests. - SKILL.md frontmatter lists a local config path (~/.config/nemovideo/) although the registry metadata did not. Ask the author whether the skill will read or write local config files before granting access. - The doc instructs the agent to “keep the technical details out of the chat,” which may hide network operations from the user. Prefer skills that explicitly disclose when they upload files or create sessions. - Verify the service/domain (mega-api-prod.nemovideo.ai) is legitimate for the product you expect. If you need stronger guarantees, ask the publisher for a homepage, privacy policy, and data-retention terms. If you proceed: do not provide highly sensitive content, prefer using a disposable or limited-scope token for NEMO_TOKEN, and request clarification about the config path and the anonymous-token behavior. If the publisher cannot clarify these inconsistencies, treat the skill with caution.

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

Runtime requirements

🧩 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97834jrtrc18n8nkynyz8dq3s85p6fe

30downloads

0stars

1versions

Updated 5h ago

v1.0.0

MIT-0

Getting Started

Got browser-based content to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

"generate a product URL or webpage screenshot into a 1080p MP4"
"generate a short promotional video from this webpage content"
"generating videos directly from browser content without leaving Chrome for marketers"

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.

Generator Chrome Extension — Generate Videos From Your Browser

Drop your browser-based content in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a product URL or webpage screenshot, ask for generate a short promotional video from this webpage content, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — pin the extension to your toolbar so you can trigger video generation on any tab in one click.

Matching Input to Actions

User prompts referencing generator chrome extension, 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`	`generator-chrome-extension`
`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.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "generate a short promotional video from this webpage content" → Download MP4. Takes 30-60 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 "generate a short promotional video from this webpage content" — 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.

Comments

Loading comments...