Facebook Video Editor

v1.3.0

Edit videos for Facebook using AI — create and optimize video content for Facebook Reels, News Feed, Stories, and Ads with platform-specific formatting, auto...

0· 107·0 current·0 all-time
bypeandrover adam@peand-rover
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill's name/description match its runtime instructions: it uploads source video(s) to a NemoVideo API and requests edited outputs for Facebook placements. Requesting a NemoVideo token (NEMO_TOKEN) is coherent for that purpose.
Instruction Scope
SKILL.md instructs the agent to POST video content to https://mega-api-prod.nemovideo.ai with Authorization: Bearer $NEMO_TOKEN — this is consistent with an external editing service. However, there is a registry/manifest mismatch: the registry summary listed no required config paths or env vars while the SKILL.md metadata includes a config path (~/.config/nemovideo/) and a primaryEnv (NEMO_TOKEN). That inconsistency should be clarified.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes risk because nothing is written to disk by the skill itself.
Credentials
Only one credential (NEMO_TOKEN) is indicated as the primary credential, which is proportionate for an external API. The minor concern is the metadata mismatch: the top-level registry data said 'Required env vars: none' while SKILL.md declares primaryEnv NEMO_TOKEN and a config path. Verify whether the skill actually requires the token and/or local config.
Persistence & Privilege
always is false and the skill does not request system-wide configuration changes or elevated privileges. Autonomous invocation is allowed by platform default but is not combined with other alarming privileges.
Assessment
This skill is coherent: it sends your raw video to a NemoVideo API for editing and requires a NemoVideo token. Before installing, do the following: (1) Verify the NemoVideo service and the api host (mega-api-prod.nemovideo.ai) are legitimate and trustworthy — there is no homepage or source listed. (2) Confirm whether you must supply a long-lived NEMO_TOKEN; prefer short-lived or scoped tokens and avoid reusing high-privilege credentials. (3) Understand that uploading videos sends your content to a third party — don’t upload sensitive or private material unless you’re comfortable with their data handling/retention. (4) Ask the publisher to clarify the metadata inconsistency (registry says no required env/config, SKILL.md lists ~/.config/nemovideo/ and primaryEnv). If you cannot verify the service or token handling, avoid installing or restrict the token’s scope and lifetime.

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

latestvk97fa1avs7sc7758sx1h7330dh83r250

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📘 Clawdis
Primary envNEMO_TOKEN

Comments