Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Data Format Converter Online

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — convert this AVI to MP4 so I can upload it to YouTube — and get converted...

0· 63·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for susan4731-wilfordf/data-format-converter-online.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Data Format Converter Online" (susan4731-wilfordf/data-format-converter-online) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/data-format-converter-online
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 data-format-converter-online

ClawHub CLI

Package manager switcher

npx clawhub@latest install data-format-converter-online
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (cloud video conversion) match the instructions (upload files to a nemo-video API, create sessions, request renders). Requiring a service token (NEMO_TOKEN) is expected. Declared config path (~/.config/nemovideo/) is plausible for persisting session/token state.
Instruction Scope
SKILL.md limits actions to obtaining an anonymous token (if not provided), creating sessions, uploading user files, reading SSE render status, and polling render state. It does not instruct reading arbitrary system files or unrelated credentials. It does instruct automatically obtaining/storing a token and session_id — consistent with its function, but implementers should ensure tokens are stored only in the declared config path.
Install Mechanism
No install spec and no code files (instruction-only) — lowest-risk installation model. Nothing is downloaded or written by an installer step beyond what the agent's runtime would do.
Credentials
Only one environment variable (NEMO_TOKEN) is required and is the primary credential for the API described. No unrelated credentials or broad secrets are requested. The declared config path is reasonable for saving session/token information.
Persistence & Privilege
Skill is not force-included (always:false). Autonomous invocation is allowed (platform default) but not excessive in this context. The skill does not request elevated or cross-skill configuration access.
Assessment
This skill appears coherent for a cloud video-conversion service. Before installing or using it, be aware that: (1) any video files you drop into the chat will be uploaded to mega-api-prod.nemovideo.ai — do not upload sensitive or confidential footage; (2) the skill will create or use a NEMO_TOKEN (either from your environment or by obtaining an anonymous token) and may persist session/token data under ~/.config/nemovideo/; (3) anonymous tokens grant limited credits and expire after 7 days; and (4) autonomous agent invocation is allowed by default — if you prefer to review actions, disable autonomous invocation or avoid granting the skill write access to config locations. If you want stronger assurance, ask the publisher for a privacy/terms URL or an official homepage and review how long tokens/outputs are retained on the remote service.

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

Runtime requirements

🔄 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk977svpjxtqcg3n9nsxwtr87j584qjdx
63downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

Share your video files and I'll get started on video format conversion. Or just tell me what you're thinking.

Try saying:

  • "convert my video files"
  • "export 1080p MP4"
  • "convert this AVI to MP4 so"

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.

Data Format Converter Online — Convert Video Files to MP4

Drop your video files in the chat and tell me what you need. I'll handle the video format conversion on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute AVI file from an old camera, ask for convert this AVI to MP4 so I can upload it to YouTube, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips convert faster and reduce the chance of timeout errors.

Matching Input to Actions

User prompts referencing data format converter online, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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:

HeaderValue
X-Skill-Sourcedata-format-converter-online
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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 Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate 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 saysYou 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "convert this AVI to MP4 so I can upload it to YouTube" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "convert this AVI to MP4 so I can upload it to YouTube" → 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.

Comments

Loading comments...