Francais Editor Ai

v1.0.0

French-speaking content creators edit raw video footage into edited French videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud...

0· 102·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/francais-editor-ai.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Francais Editor Ai" (mory128/francais-editor-ai) from ClawHub.
Skill page: https://clawhub.ai/mory128/francais-editor-ai
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 francais-editor-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install francais-editor-ai
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims to perform cloud GPU video editing and its instructions require a NEMO_TOKEN and call nemovideo.ai endpoints to create sessions, upload files, run renders, and fetch results — all coherent for a cloud rendering service. Minor metadata mismatch: registry shows no required config paths but the SKILL.md frontmatter lists ~/.config/nemovideo/.
Instruction Scope
Instructions explicitly describe obtaining an anonymous token, creating a session, uploading user video files (via multipart or URL), driving renders via SSE, polling render status, and returning download URLs. These actions are within the declared purpose, but they involve sending user media and metadata to an external service and detecting the agent install path to set attribution headers.
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. Low install risk.
Credentials
Only one credential is required (NEMO_TOKEN), which is appropriate for a cloud API. The SKILL.md also instructs acquiring an anonymous token via the public auth endpoint if the env var isn't present. The frontmatter references a configPath (~/.config/nemovideo/) not declared in the registry metadata — a small inconsistency to be aware of.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It permits autonomous invocation (the platform default), which combined with external API access increases blast radius but is expected for a cloud service integration.
Scan Findings in Context
[no_regex_findings] expected: The static scanner found no code to analyze (instruction-only SKILL.md). Lack of findings is expected for a text-only skill, but does not mean the remote endpoints are trustworthy.
Assessment
This skill will upload any video you give it to an external service (mega-api-prod.nemovideo.ai) and will obtain or use a NEMO_TOKEN to do renders. That behavior is consistent with its description, but the skill's source/homepage is unknown. Before using it: (1) do not upload sensitive or private footage you wouldn't share with a third party, (2) prefer providing your own API token rather than letting the skill obtain an anonymous token if you want auditability, (3) verify the service owner or privacy policy if possible, and (4) note the small metadata inconsistency (a config path appears in SKILL.md but not in registry metadata). If you need stronger assurance, request a published homepage, owner contact, or review of the remote API's terms and security practices before proceeding.

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

Runtime requirements

🇫🇷 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97byfet1z9ga0qkq8de71tays84kcaw
102downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

Send me your raw video footage and I'll handle the AI French editing. Or just describe what you're after.

Try saying:

  • "edit a 2-minute unedited French vlog recording into a 1080p MP4"
  • "edit my French video with cuts, transitions, and French subtitles"
  • "editing French-language videos with AI-generated French subtitles and cuts for French-speaking content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

  • Generate a UUID as client identifier
  • POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
  • Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Français Editor AI — Edit and Export French Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI French editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute unedited French vlog recording, ask for edit my French video with cuts, transitions, and French subtitles, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 3 minutes process significantly faster and give cleaner French transcription results.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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)

Common Workflows

Quick edit: Upload → "edit my French video with cuts, transitions, and French subtitles" → Download MP4. Takes 1-2 minutes 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 "edit my French video with cuts, transitions, and French subtitles" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest compatibility across French streaming platforms.

Comments

Loading comments...