← Back to Skills Marketplace
Video Editing Ai Descript
by
vcarolxhberger
· GitHub ↗
· v1.0.0
· MIT-0
60
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install video-editing-ai-descript
Description
Get transcript-edited videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something...
Usage Guidance
This skill appears to call a remote video-processing API and will upload your footage to that service. Before installing: 1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and its privacy terms — uploaded media and transcripts will be sent there. 2) Ask the developer to clarify the NEMO_TOKEN requirement: the registry marks it as required but the skill can auto-generate an 'anonymous' token; decide whether you want the agent to create/store tokens automatically. 3) Request clarification about reading config paths / install-path detection — if you don't want the skill probing your filesystem or agent install path, get an explicit statement of what it reads and why. 4) If you require auditability, ask for logs or confirm that the skill will not hide API responses or tokens from administrators. If these questions aren't answered clearly, consider treating this skill as potentially risky for sensitive content.
Capability Analysis
Type: OpenClaw Skill
Name: video-editing-ai-descript
Version: 1.0.0
The skill is a functional integration for a cloud-based video editing service (nemovideo.ai). It provides the AI agent with specific instructions for authentication, session management, file uploads, and processing via Server-Sent Events (SSE). While it requires network access and handles user video files, these actions are directly aligned with its stated purpose. The instructions include security best practices, such as hiding API tokens from the user interface, and do not exhibit signs of data exfiltration, malicious execution, or harmful prompt injection.
Capability Assessment
Purpose & Capability
Name and description match a cloud video-editing service and the primary credential (NEMO_TOKEN) is consistent with that purpose. However, the registry metadata and the SKILL.md disagree: the top-level metadata reported no required config paths, but the SKILL.md frontmatter metadata lists configPaths (~/.config/nemovideo/). Also the registry lists NEMO_TOKEN as required, yet the SKILL.md instructs the agent to generate an anonymous token if NEMO_TOKEN is not present. These contradictions reduce trustworthiness.
Instruction Scope
Runtime instructions perform expected actions for a remote render pipeline (session creation, SSE messaging, uploads, polling exports). But they also direct the agent to automatically POST to an external API to obtain anonymous tokens (and store them), detect the agent's install path to set X-Skill-Platform, and read YAML frontmatter for version/source headers. The instructions also tell the agent not to display raw API responses or token values — which is reasonable for security but could hide sensitive details. The combination (auto-create/store tokens, probe install path, and suppress display) is scope-expanding compared with a simple ‘upload & render’ helper and should be understood.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest install risk because nothing is downloaded or written by a packaged installer.
Credentials
Only one credential (NEMO_TOKEN) is declared as primary, which is proportionate for a cloud API. However, SKILL.md both treats NEMO_TOKEN as required and simultaneously provides a flow to create an anonymous token if it's missing — a contradiction. The frontmatter's request to reference ~/.config/nemovideo/ (not declared in registry requirements) suggests the skill may read local config files. Those inconsistencies are unclear and warrant caution.
Persistence & Privilege
Skill does ask to 'store the returned session_id' and to reuse tokens for requests, but it does not request always: true, nor does it ask to modify other skills or system-wide settings. Persisting a session/token for the skill's own API calls is expected behavior for a remote-render integration.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install video-editing-ai-descript - After installation, invoke the skill by name or use
/video-editing-ai-descript - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release: AI-powered video editing by editing text transcripts, optimized for speed and simplicity.
- Upload raw footage (up to 500MB), describe edits (e.g. remove filler words, trim silences, add captions), and export 1080p MP4s automatically.
- Fast authentication using anonymous tokens; 100 free credits valid for 7 days on first use.
- Session-based editing: all actions mapped to API endpoints; progress and edit summaries provided in natural language.
- Supports batch uploads, iterative edits, and common post-production workflows.
- Clear error handling for file size, format, authentication, and usage limits.
Metadata
Frequently Asked Questions
What is Video Editing Ai Descript?
Get transcript-edited videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something... It is an AI Agent Skill for Claude Code / OpenClaw, with 60 downloads so far.
How do I install Video Editing Ai Descript?
Run "/install video-editing-ai-descript" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Video Editing Ai Descript free?
Yes, Video Editing Ai Descript is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Video Editing Ai Descript support?
Video Editing Ai Descript is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Video Editing Ai Descript?
It is built and maintained by vcarolxhberger (@vcarolxhberger); the current version is v1.0.0.
More Skills