Stop Motion Video Maker
v1.0.0Turn a sequence of photos or video frames into a fluid stop-motion-video-maker animation in minutes. Upload your images or footage in mp4, mov, avi, webm, or...
⭐ 0· 42·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 (stop-motion video maker) matches what the instructions do: upload images/video, call a NemoVideo cloud API, create sessions, upload files, render exports. Declared config path (~/.config/nemovideo/) and a single service token (NEMO_TOKEN) are expected for a cloud backend.
Instruction Scope
Instructions stay within the expected scope: check or generate a client_id in ~/.config/nemovideo/, obtain an anonymous token, create sessions, upload files, poll renders and check credits/state. One point to watch: the runtime describes constructing a workspace claim URL that could include tokens in query parameters — the doc says 'Don't expose tokens', but care must be taken to avoid leaking NEMO_TOKEN in generated links or logs. The skill also reads its own YAML frontmatter and detects install paths for attribution, which is reasonable but requires local file/path reads.
Install Mechanism
Instruction-only skill with no install steps or downloaded code. That minimizes disk-write/exec risk.
Credentials
Only a single service credential (NEMO_TOKEN) and a per-user client_id stored under ~/.config/nemovideo/ are used — appropriate for a cloud API client. Minor metadata inconsistency: the frontmatter/registry shows an empty requires.env list but also declares NEMO_TOKEN as primary credential; this is a bookkeeping mismatch but not a functional red flag.
Persistence & Privilege
always:false (not force-included). The skill requests permission to store a client_id under ~/.config/nemovideo/ and to persist the obtained token for session use — this is ordinary for a cloud-backed skill and does not modify other skills or system-wide settings.
Assessment
This skill appears to be what it says: a cloud-backed stop-motion uploader/renderer that needs a NemoVideo token and will save a small client_id file under ~/.config/nemovideo/. Before installing: 1) Confirm you trust nemovideo.com / mega-api-prod.nemovideo.ai as your files and images will be uploaded to their service. 2) Verify how shared workspace links are constructed — ensure the token is never embedded in public URLs or logs. 3) Note the metadata mismatch (NEMO_TOKEN listed as primaryEnv but not in requires.env); ask the publisher to clarify which env var is required and how tokens are stored. 4) If you want to avoid cloud uploads, do not use this skill — it intentionally sends media to a remote API. If any of the above are unacceptable, do not install or use the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97de74bk8xpdhwkabh8dd1r4n83wn1c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎞️ Clawdis
Primary envNEMO_TOKEN
