Ai Screen Recording

v1.0.0

edit screen recordings into polished screen recordings with this ai-screen-recording skill. Works with MP4, MOV, AVI, WebM files up to 500MB. educators, deve...

0· 62·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (cloud AI screen recording edits) match the declared requirement (NEMO_TOKEN) and the runtime calls to mega-api-prod.nemovideo.ai for session, upload, render and credits. One minor inconsistency: the registry metadata listed no config paths, while the SKILL.md frontmatter mentions ~/.config/nemovideo/ as a config path.
Instruction Scope
SKILL.md only instructs actions consistent with the service: check/provide NEMO_TOKEN, create session, upload files (multipart or URL), send SSE messages, poll render status and return download URL. It does instruct the agent to read the skill's YAML frontmatter and detect install path for attribution headers — this implies the agent will read its own skill file / install path, which is expected but worth noting. All user data (videos) are uploaded to the external backend; the instructions do not request unrelated system files or other credentials.
Install Mechanism
Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. Low install risk.
Credentials
Only one credential (NEMO_TOKEN) is declared as required and used. The skill can auto-provision an anonymous token by POSTing to the nemovideo API if NEMO_TOKEN is absent — this is coherent with the described anonymous-access flow but means the skill will make outbound network calls and obtain a token on the user's behalf. No other unrelated secrets are requested.
Persistence & Privilege
always is false and there is no install-time persistence or requests to modify other skills or system-wide settings. The skill does ask to read its own frontmatter and detect install path for attribution headers (non-privileged).
Assessment
This skill appears internally consistent for a cloud-based video-editing service: it will upload any user-supplied videos to mega-api-prod.nemovideo.ai and requires (or will obtain) a NEMO_TOKEN to do so. Before installing, consider: 1) Privacy: do not upload sensitive or confidential footage unless you trust nemovideo.ai and have reviewed their data retention/privacy terms. 2) If you prefer control, supply your own NEMO_TOKEN rather than letting the skill fetch an anonymous token. 3) Note the small metadata inconsistency (SKILL.md mentions ~/.config/nemovideo/ while registry metadata did not) — harmless but worth awareness. 4) No other system credentials are requested. If you need stronger assurance, ask the publisher for the service's privacy policy and the exact contract for anonymous token handling and retention of uploaded media.

Like a lobster shell, security has layers — review code before you run it.

latestvk9750bssxc9m7e21g9s1k9htks84nzxw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🖥️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments