← Back to Skills Marketplace
Ugc Video
by
peandrover adam
· GitHub ↗
· v1.0.0
· MIT-0
96
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install ugc-video
Description
content creators and marketers create raw phone footage into authentic UGC clips using this skill. Accepts MP4, MOV, WebM, AVI up to 500MB, renders on cloud...
Usage Guidance
This skill will upload whatever video you provide to an external service (mega-api-prod.nemovideo.ai) and use a bearer token (NEMO_TOKEN) to operate; if NEMO_TOKEN is missing it will attempt to create an anonymous token via the API. Before installing or using it: (1) Do not upload private or proprietary footage until you confirm the service operator, privacy/data retention policy, and whether uploaded files are stored or shared. (2) Ask the publisher why the registry requires NEMO_TOKEN but the skill auto-creates an anonymous token, and whether the anonymous token is persisted on disk (and where). (3) Confirm what the quoted 'credits' and expiry mean and whether operations could incur charges. (4) If you need to test, do so with non-sensitive content only. (5) Prefer skills with a verifiable homepage/source and documented privacy/security posture; consider an offline tool if you cannot accept sending media to a third party.
Capability Analysis
Type: OpenClaw Skill
Name: ugc-video
Version: 1.0.0
The skill is a well-documented integration for a UGC video creation service (nemovideo.ai). It provides clear instructions for the agent to handle authentication via anonymous tokens, manage video processing sessions, and perform file uploads and cloud rendering. While it includes platform fingerprinting for attribution and requires network and file access, these behaviors are directly aligned with its stated purpose and lack any indicators of malicious intent, data exfiltration, or unauthorized execution. The instructions even include security-conscious directives such as hiding raw tokens and API outputs from the user.
Capability Assessment
Purpose & Capability
The declared purpose (cloud UGC video rendering) matches the API calls and upload/upload+render workflow described in SKILL.md. However the registry requires NEMO_TOKEN while the runtime instructions explicitly support obtaining an anonymous token via the nemovideo.ai API if NEMO_TOKEN is missing — this mismatch between declared requirements and actual behavior is incoherent and should be clarified.
Instruction Scope
SKILL.md instructs the agent to upload user-provided video files to https://mega-api-prod.nemovideo.ai, use SSE endpoints, poll render status, and handle multipart file uploads. It also instructs auto-creation of tokens and to 'auto-detect' platform from install path (which implies reading agent filesystem). These are within the skill's editing/rendering purpose, but they involve network exfiltration of user-supplied media and reading local install/config locations — both are sensitive operations and not fully justified in the manifest.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so it does not write executables to disk. That lowers install-time risk.
Credentials
Registry lists a single required env var (NEMO_TOKEN), which is appropriate for a cloud API. But SKILL.md both reads/will use NEMO_TOKEN if present and will POST to an anonymous-token endpoint to obtain a token if it isn't present — an inconsistency. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) that the registry did not list. These mismatches raise questions about what credentials/config the skill will read or write and where any auto-created tokens are stored.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide privileges. It does ask to keep session_id in memory for operations, which is normal for a session-based API. There is no install-time persistence declared.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ugc-video - After installation, invoke the skill by name or use
/ugc-video - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of UGC Video — Create Authentic UGC Creator Clips:
- Accepts raw phone video (MP4, MOV, WebM, AVI) up to 500MB and turns it into polished UGC clips on cloud GPUs.
- Supports 1080p MP4 output in 1–2 minutes; works best with vertical 9:16 footage for TikTok and Reels.
- Automatic setup: manages tokens, session, and cloud back-end connection with clear user feedback.
- User-driven workflow: upload footage and give editing instructions (trim, overlay text, etc.), then receive ready-to-download video links.
- Exposes simple chat commands for export, upload, status, and credits; robust error-handling and file support details provided.
Metadata
Frequently Asked Questions
What is Ugc Video?
content creators and marketers create raw phone footage into authentic UGC clips using this skill. Accepts MP4, MOV, WebM, AVI up to 500MB, renders on cloud... It is an AI Agent Skill for Claude Code / OpenClaw, with 96 downloads so far.
How do I install Ugc Video?
Run "/install ugc-video" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Ugc Video free?
Yes, Ugc Video is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Ugc Video support?
Ugc Video is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Ugc Video?
It is built and maintained by peandrover adam (@peand-rover); the current version is v1.0.0.
More Skills