Skill flagged — suspicious patterns detected

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

Best Data Format Converter

v1.0.0

Turn a 2-minute AVI file from an old camera into 1080p converted MP4 files just by typing what you need. Whether it's converting legacy or incompatible video...

0· 64·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/best-data-format-converter.

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

ClawHub CLI

Package manager switcher

npx clawhub@latest install best-data-format-converter
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill's name and description (video -> MP4 conversion) align with the API calls in SKILL.md (upload, render, export endpoints on mega-api-prod.nemovideo.ai) and the declared primary env var NEMO_TOKEN. However, SKILL.md frontmatter references a config path (~/.config/nemovideo/) that the registry metadata did not list in 'Required config paths' — a mismatch worth noting but plausibly benign (minor metadata drift).
Instruction Scope
Runtime instructions are limited to authenticating (NEMO_TOKEN or anonymous-token generation), creating a session, uploading video files or URLs, streaming SSE messages, and polling for render status on the nemo API. The endpoints are all within the same domain and the instructions do not ask the agent to read unrelated system files or unrelated credentials. One small note: instructions describe deriving an X-Skill-Platform header from install paths (e.g., ~/.clawhub/), which implies the agent may consult its install location — not a broad filesystem sweep, but worth being aware of.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is the lowest-risk install mechanism.
Credentials
The skill requests a single credential (NEMO_TOKEN), which is appropriate for a remote API. It also documents a fallback flow to obtain an anonymous token via the service's anonymous-token endpoint. Aside from the earlier metadata mismatch about config paths in frontmatter, there are no unrelated or extra credentials requested.
Persistence & Privilege
The skill is not force-included (always: false) and does not request elevated or persistent platform-wide privileges. Autonomous invocation is allowed by default (disable-model-invocation: false) but that is the platform norm and not, by itself, a red flag here.
Assessment
This skill appears to do what it says: it uploads files to nemovideo.ai and requests a session token to run server-side conversions. Before installing, consider: (1) Trust the service and the domain mega-api-prod.nemovideo.ai — there is no homepage or source URL provided, so provenance is unknown. (2) Only provide a dedicated NEMO_TOKEN (or use the anonymous token flow) — don't supply any broader cloud or system credentials. (3) Avoid uploading sensitive or private video content unless you trust the service's privacy policy. (4) Note the minor metadata mismatch (SKILL.md lists a config path not shown in registry metadata) and the header that uses install-path detection; ask the publisher to clarify if you need strict guarantees. If you want higher assurance, ask for the publisher/source URL or an official privacy/terms link before use.

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

Runtime requirements

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

Getting Started

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

Try saying:

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

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Best Data Format Converter — Convert Video Files to MP4

Send me your video files and describe the result you want. The AI format conversion runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute AVI file from an old camera, type "convert this AVI to MP4 at 1080p", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter clips convert faster and use fewer processing credits.

Matching Input to Actions

User prompts referencing best data format converter, 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.

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-data-format-converter, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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 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

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

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 at 1080p" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and file size.

Common Workflows

Quick edit: Upload → "convert this AVI to MP4 at 1080p" → 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...