Skill flagged — suspicious patterns detected

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

Instagram Editor

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — crop to 9:16, add trending captions, and trim to under 60 seconds for Inst...

0· 43·0 current·0 all-time
bypeandrover adam@peand-rover

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for peand-rover/instagram-editor.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Instagram Editor" (peand-rover/instagram-editor) from ClawHub.
Skill page: https://clawhub.ai/peand-rover/instagram-editor
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 instagram-editor

ClawHub CLI

Package manager switcher

npx clawhub@latest install instagram-editor
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill claims to perform cloud-based Instagram-format video edits and the SKILL.md shows exactly that (session creation, upload, render). Requesting a single service token (NEMO_TOKEN) is proportionate. However the registry summary lists no config paths while the skill's own YAML frontmatter declares a config path (~/.config/nemovideo/), an inconsistency in metadata/provenance.
Instruction Scope
Instructions direct the agent to call an external API (mega-api-prod.nemovideo.ai), create anonymous tokens, upload large media (up to 500MB), open SSE streams, poll render status, and derive an X-Skill-Platform header from the agent's install path. All of these are coherent with a cloud render pipeline, but they involve network I/O and (potentially) reading install/config paths — verify you are comfortable sending content and that the agent will not leak other local data.
Install Mechanism
Instruction-only skill with no install spec or code files — minimal install risk (nothing written to disk by an installer).
Credentials
Only NEMO_TOKEN is required which fits a remote API service. Still: the skill will use that token as a Bearer credential for all requests to the third-party API and may request/regenerate anonymous tokens. Confirm that NEMO_TOKEN is scoped appropriately and that you trust the remote service before providing it. Also note the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) that was not listed in the top-level summary — unclear whether the skill will read or write that directory.
Persistence & Privilege
always:false and normal model invocation; the skill instructs saving session_id but does not request permanent system-wide privileges or modifications. No evidence it alters other skills or global agent settings.
What to consider before installing
This skill appears to be a thin wrapper around a third-party cloud video-editing API (mega-api-prod.nemovideo.ai). Before installing or supplying credentials: 1) Confirm the service/provider (there's no homepage or owner info) and review its privacy/terms — uploaded videos will be sent to that API. 2) Use a limited or anonymous token where possible and revoke it after use; don't set long-lived high-privilege credentials as NEMO_TOKEN unless you trust the provider. 3) Note the SKILL.md references ~/.config/nemovideo/ and reads the agent install path for X-Skill-Platform headers — make sure you are comfortable with those filesystem reads. 4) If provenance is unclear, test with non-sensitive sample videos first and monitor network calls; ask the publisher for a homepage or docs if you need stronger assurance.

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

Runtime requirements

📸 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972f9r5cg4h3mkpkhn8se9h3d85qgyh
43downloads
0stars
1versions
Updated 19h ago
v1.0.0
MIT-0

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI Instagram formatting.

Try saying:

  • "edit a 2-minute landscape video recorded on a phone into a 1080p MP4"
  • "crop to 9:16, add trending captions, and trim to under 60 seconds for Instagram Reels"
  • "reformatting and editing videos to fit Instagram Reels or Stories for Instagram creators"

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.

Instagram Editor — Edit and Export Instagram Videos

This tool takes your video clips and runs AI Instagram formatting through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute landscape video recorded on a phone and want to crop to 9:16, add trending captions, and trim to under 60 seconds for Instagram Reels — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 video works best for Reels and Stories without any cropping needed.

Matching Input to Actions

User prompts referencing instagram editor, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is instagram-editor, 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).

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

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 "crop to 9:16, add trending captions, and trim to under 60 seconds for Instagram Reels" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Instagram and other platforms.

Common Workflows

Quick edit: Upload → "crop to 9:16, add trending captions, and trim to under 60 seconds for Instagram Reels" → 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.

Comments

Loading comments...