Editor Ai Linkedin
v1.0.0professionals and marketers edit raw video footage into LinkedIn-ready videos using this skill. Accepts MP4, MOV, AVI, WebM up to 500MB, renders on cloud GPU...
⭐ 0· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (LinkedIn video editing) align with runtime instructions: the SKILL.md describes uploading video files, creating a session, using render/export endpoints, and returning download URLs. Requesting a single API token (NEMO_TOKEN) is appropriate for this purpose.
Instruction Scope
Instructions explicitly direct the agent to POST video files and metadata to https://mega-api-prod.nemovideo.ai, create sessions, poll renders, and handle SSE streams — all expected for a cloud editor. The SKILL.md also instructs the agent to read this file's YAML frontmatter at runtime and to detect install path (~/.clawhub, ~/.cursor/skills) to set an attribution header; that requires read access to the skill file and possibly the agent's install paths. This is plausible but broader than strictly necessary for basic editing and is worth noting for privacy/least-privilege concerns.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing is downloaded or written by an installer in the provided manifest.
Credentials
The skill declares a single required credential (NEMO_TOKEN), which matches the API calls in SKILL.md. However, SKILL.md metadata also references a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths — this is an inconsistency. The single token is proportionate, but the skill will upload user media to an external service (privacy/data exfiltration risk inherent to the described function).
Persistence & Privilege
always is false and the skill does not request permanent platform inclusion. It does instruct saving a session_id and the token for session use, which is normal for API-driven workflows and not an elevated privilege.
Scan Findings in Context
[no-code-files-scanned] expected: The static scanner found no code files to analyze because this is an instruction-only skill. That is expected for a SKILL.md-only integration; absence of findings is not proof of safety. Manual review of SKILL.md was used instead.
Assessment
This skill appears to do what it says: it uploads your video files to a nemovideo.ai API and returns edited exports, and it needs a single API token (NEMO_TOKEN). Before installing, confirm: (1) you trust the external domain (mega-api-prod.nemovideo.ai) to handle your videos and any PII — uploads occur off-device; (2) whether you’re comfortable the agent may read the skill file and detect install paths to set attribution headers; (3) the registry metadata mismatch about config paths (~/.config/nemovideo/) — ask the publisher why that path is referenced and whether any local files will be read. If any of these points are unacceptable, do not install or ask the publisher for documentation/security/privacy details and a verified homepage/source before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97anjm6pnpmvm70md9zya6b9h84kkm0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
💼 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN