Skill flagged — suspicious patterns detected

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

Free Image Creator

v1.0.0

Get AI generated images ready to post, without touching a single slider. Upload your text prompts (JPG, PNG, WEBP, MP4, up to 200MB), say something like "gen...

0· 99·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 mory128/free-image-creator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Free Image Creator" (mory128/free-image-creator) from ClawHub.
Skill page: https://clawhub.ai/mory128/free-image-creator
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 free-image-creator

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-image-creator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name/description (AI image/video generation) aligns with the API endpoints and actions described in SKILL.md (session creation, SSE, upload, render/export). However there is an internal inconsistency: the registry summary lists no required config paths, but the SKILL.md frontmatter declares a configPath (~/.config/nemovideo/). That mismatch should be explained by the author.
Instruction Scope
SKILL.md stays focused on image/video generation: it directs the agent to create/refresh tokens, create sessions, upload media (including large user files), poll renders, and return download URLs. It does not instruct the agent to read unrelated system files or secrets. Two points to watch: (1) it tells the agent to 'auto-detect' platform from an install path (no install present) which may require filesystem inspection, and (2) it explicitly advises not to display raw API responses or token values to the user — this is reasonable for security but also reduces transparency for auditing.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, which minimizes on-disk risk. There is no downloader or executable install to review.
!
Credentials
The skill declares a single primary credential NEMO_TOKEN which is appropriate for a third-party rendering API. However: (a) SKILL.md describes a full anonymous-token flow that creates a token itself if NEMO_TOKEN is not set, making the 'required env var' claim inconsistent; (b) the frontmatter requests a user config path (~/.config/nemovideo/) that wasn't listed in the registry manifest — this suggests the skill may attempt to access local config files; and (c) because the skill uploads user files to a third-party API, sending any sensitive files would expose them externally. These points increase the privilege surface and deserve clarification.
Persistence & Privilege
The skill is not always-enabled, has no install, and does not request elevated system-wide privileges. It stores session IDs/tokens for API interaction (normal for this type of integration).
What to consider before installing
This skill mostly does what it says — it calls a third-party API to render images/videos — but there are several things to verify before installing or using it: - Confirm the discrepancy about config paths: SKILL.md's frontmatter mentions ~/.config/nemovideo/ but the registry metadata did not. Ask the publisher whether the skill will read that directory and why. - Understand the NEMO_TOKEN behavior: the registry marks NEMO_TOKEN as required, yet SKILL.md explains an anonymous-token flow (the skill can obtain a short-lived token itself). If you do provide a NEMO_TOKEN via environment, ask how long it will be stored and where. Prefer not to place long-lived credentials in env unless necessary. - Treat uploads as external: any file you upload (images, video, or other files) will be sent to mega-api-prod.nemovideo.ai. Do not upload sensitive personal or corporate files unless you trust that service and have confirmed retention/deletion policies. - Ask for provenance: there is no homepage or source repo listed. Request the author's identity/source code or at least a privacy/security statement for the backend (where files and tokens are sent/stored). - If uncomfortable, decline to set a permanent NEMO_TOKEN and, if you try the skill, prefer the anonymous flow or a disposable account. Request explicit answers about where tokens/session IDs are stored, whether anything is written to disk, and how long rendered outputs and uploaded files are retained. What would change this assessment: presence of a verified homepage/source repo and a clear manifest (matching SKILL.md), or explicit confirmation that the skill does not read arbitrary local config files and that tokens are ephemeral. If the author clarifies those points, confidence could be raised to high and the classification could become benign.

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

Runtime requirements

🖼️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97c1amq87e3e0rspec4w3xmfn855n2b
99downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "generate my text prompts"
  • "export 1080p MP4"
  • "generate a realistic photo of a"

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.

Free Image Creator — Generate Images from Text Prompts

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

Say you have a short text description like 'sunset over a mountain lake' and want to generate a realistic photo of a coffee shop interior with warm lighting — the backend processes it in about 10-30 seconds and hands you a 1080p MP4.

Tip: more specific prompts produce more accurate and usable results.

Matching Input to Actions

User prompts referencing free image creator, 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.

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.

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

HeaderValue
X-Skill-Sourcefree-image-creator
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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)

Common Workflows

Quick edit: Upload → "generate a realistic photo of a coffee shop interior with warm lighting" → Download MP4. Takes 10-30 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 realistic photo of a coffee shop interior with warm lighting" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, WEBP, MP4 for the smoothest experience.

Export as MP4 for widest compatibility when embedding images into video timelines.

Comments

Loading comments...