Skill flagged — suspicious patterns detected

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

Free Text Generator

v1.0.0

generate text prompts into AI-written video scripts with this skill. Works with TXT, DOCX, PDF, MP4 files up to 200MB. content creators use it for generating...

0· 53·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 francemichaell-15/free-text-generator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Free Text Generator" (francemichaell-15/free-text-generator) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/free-text-generator
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-text-generator

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-text-generator
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description claim to generate video scripts and render MP4s and the instructions map directly to a cloud render API—NEMO_TOKEN as the primary credential is coherent. However the skill has no listed homepage or source and the registry metadata lacks provenance, which reduces trust.
!
Instruction Scope
Runtime instructions will upload user files (multipart uploads or URLs), create sessions, stream SSE, and poll render endpoints on an external service—these are consistent with the stated purpose. They also instruct the agent to read this file's YAML frontmatter and detect the local install path to set X-Skill-Platform; reading install paths/configs is broader system access than purely generating text and may expose local info.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. There is no archive download or third-party package install described.
!
Credentials
Only NEMO_TOKEN is declared as required, which is appropriate for a backend service. But the SKILL.md frontmatter also lists a configPaths entry (~/.config/nemovideo/) while the registry metadata showed none — an inconsistency. The skill will use any NEMO_TOKEN present or automatically obtain an anonymous token (i.e., it will contact the external auth endpoint even if you don't set a token), and user files are transmitted to the API—so credentials and uploaded content will leave the local environment.
Persistence & Privilege
always is false and the skill does not request persistent system-level changes or modify other skills. Autonomous invocation is allowed (default) but not combined here with any elevated privilege.
Scan Findings in Context
[no_code_files] expected: Scanner found no code files to analyze. This is expected for an instruction-only skill, so the SKILL.md content is the primary security surface to review.
What to consider before installing
This skill will send prompts and any files you upload to an external service (mega-api-prod.nemovideo.ai) and will use a NEMO_TOKEN from your environment if present—or automatically fetch an anonymous token if not. Before installing or using it: 1) Only upload non-sensitive files (do not send private keys, passwords, or proprietary data). 2) Do not set a reusable NEMO_TOKEN in your environment unless you trust the service; if you must test, use a disposable token. 3) Note the registry metadata lacks a homepage/source and SKILL.md and registry metadata disagree about config paths (~/.config/nemovideo/), so verify the skill publisher separately. 4) If you want to reduce local exposure, avoid granting the agent access to your home config directories and inspect ~/.config/nemovideo/ for any secrets. 5) Prefer skills with clear author/source information and a documented privacy policy for uploaded content.

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

Runtime requirements

✍️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97fkxpvwpbenk3vy8av1gv50d851r4q
53downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

  • "generate a one-line topic prompt like 'explain blockchain in 30 seconds' into a 1080p MP4"
  • "generate a script for a 60-second explainer video about climate change"
  • "generating video scripts or on-screen text from a simple prompt for content creators"

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.

Free Text Generator — Generate Scripts and Video Text

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

Say you have a one-line topic prompt like 'explain blockchain in 30 seconds' and want to generate a script for a 60-second explainer video about climate change — the backend processes it in about 10-30 seconds and hands you a 1080p MP4.

Tip: shorter, more specific prompts produce tighter and more usable text output.

Matching Input to Actions

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

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

  • X-Skill-Source: free-text-generator
  • X-Skill-Version: from frontmatter version
  • X-Skill-Platform: detect from install path (~/.clawhub/clawhub, ~/.cursor/skills/cursor, else 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 Codes

  • 0 — success, continue normally
  • 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
  • 1002 — session not found; create a new one
  • 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
  • 4001 — unsupported file type; show accepted formats
  • 4002 — file too large; suggest compressing or trimming
  • 400 — missing X-Client-Id; generate one and retry
  • 402 — free plan export blocked; not a credit issue, subscription tier
  • 429 — rate limited; wait 30s and retry once

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

  • "click" or "点击" → execute the action via the relevant endpoint
  • "open" or "打开" → query session state to get the data
  • "drag/drop" or "拖拽" → send the edit command through SSE
  • "preview in timeline" → show a text summary of current tracks
  • "Export" or "导出" → run the 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 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 "generate a script for a 60-second explainer video about climate change" — concrete instructions get better results.

Max file size is 200MB. Stick to TXT, DOCX, PDF, MP4 for the smoothest experience.

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a script for a 60-second explainer video about climate change" → 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.

Comments

Loading comments...