Tiktok Image To Video
v1.0.0Skip the learning curve of professional editing software. Describe what you want — turn these photos into a TikTok video with music and transitions — and get...
⭐ 0· 56·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
The skill name/description match the runtime instructions: all API calls target a single third‑party service (mega-api-prod.nemovideo.ai) that plausibly performs AI video rendering, and the only credential in play is NEMO_TOKEN. This is consistent with the stated purpose.
Instruction Scope
Instructions stay within the video-rendering domain (create/get session, upload images, SSE for progress, export/poll for download URL). The skill also instructs the agent to read the YAML frontmatter and detect the agent's install path (to set X-Skill-Platform), which implies limited filesystem access; this is explainable but worth noting because it requires reading the agent runtime/install path. The skill also auto-generates an anonymous token when NEMO_TOKEN is absent and tells the agent to 'store' session_id — the exact storage location/mechanism is not specified.
Install Mechanism
No install spec and no code files are present (instruction-only). That minimizes disk-write/install risk.
Credentials
Only one credential (NEMO_TOKEN) is declared as required/primary, which is proportional for a cloud-rendering integration. However, the SKILL.md metadata also references a config path (~/.config/nemovideo/) whereas the registry summary listed no required config paths — this metadata mismatch and the unspecified persistence location for session tokens are things to confirm.
Persistence & Privilege
The skill is not always-on and uses normal autonomous invocation. It asks the agent to retain a session_id for subsequent requests, but it does not request privileged system changes or other skills' configs.
Assessment
This skill appears to do what it says: it talks to a single third‑party API (nemovideo.ai) and uses one credential (NEMO_TOKEN). Before installing, consider:
- Trust and privacy: You will be uploading images to a third‑party rendering service. Confirm the service's privacy/data-retention policy and whether sensitive images are acceptable to send.
- Token handling and persistence: The skill will auto-create an anonymous token if NEMO_TOKEN is not provided and asks the agent to 'store' session state. Ask where tokens and session IDs are stored (memory only, agent config, or a file under ~/.config/nemovideo/). If persistent storage is used, prefer a location you control and review file permissions.
- Metadata mismatch: The SKILL.md includes a configPaths entry (~/.config/nemovideo/) but the registry summary said none — ask the publisher to clarify whether the skill will read/write that path.
- Attribution headers: The skill requires adding X-Skill-* headers and derives X-Skill-Platform by inspecting install paths; this requires reading the agent environment. If you prefer a stricter isolation model, ask for an alternative that accepts the platform as an explicit parameter instead of autodetection.
- Least privilege: If you have concerns, run the skill in a restricted environment or sandbox, or provide a short‑lived NEMO_TOKEN and test with non-sensitive images first.
If the publisher/source is unknown (registry shows unknown/none), consider contacting them for clarification about token persistence and the configPath usage before granting it access to your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk974p7gtqtxn9je7yp9dnycjxs84pfav
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎵 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
