Home Inspection Video Maker
v1.0.0Your home inspection report is 47 pages of checkboxes and technical language that the buyer will skim for ten minutes before calling you with questions you a...
⭐ 0· 30·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 and description claim to generate inspection summary videos from footage and findings; the skill only requires a single service token (NEMO_TOKEN) and references a NemoVideo API endpoint — these requirements match the stated purpose.
Instruction Scope
SKILL.md instructs posting inspection data to https://mega-api-prod.nemovideo.ai/api/v1/generate with Authorization: Bearer $NEMO_TOKEN, which is appropriate for a remote video-generation service. However, the instructions are incomplete about how to upload binary video files (example shows JSON only), do not address data retention/privacy/redaction of sensitive content, and will result in potentially sensitive video data leaving the local environment.
Install Mechanism
Instruction-only skill with no install spec or code files — nothing is written to disk by the skill itself. This is the lowest install risk.
Credentials
Only NEMO_TOKEN is required (declared as primaryEnv) and a Nemo config path is referenced in metadata; that is proportionate for an external API. Caveat: the token grants the remote service authorization to accept uploads, so ensure the token is scoped to this service and not a broader credential used elsewhere.
Persistence & Privilege
The skill is not always-on and does not request elevated agent privileges or modifications to other skills. Model invocation is allowed (normal default); if you do not trust the external service, avoid enabling autonomous invocation.
Assessment
This skill appears to do what it says: send inspection findings (and presumably footage) to a NemoVideo API using NEMO_TOKEN. Before installing or using it: (1) confirm who runs 'nemovideo.ai' (no homepage provided) and read their privacy/retention policy; (2) ensure NEMO_TOKEN is dedicated to this service and not a shared/privileged secret; (3) test with non-sensitive sample footage to verify how files must be uploaded and where they are stored; (4) ask the publisher how long videos are retained, who can access them, and whether PII is protected; (5) avoid enabling autonomous invocation if you do not want the agent to send files without manual approval. If you cannot verify the service operator or token scope, treat the risk to privacy as significant.Like a lobster shell, security has layers — review code before you run it.
latestvk97dkc7cwf8ze84hz64c1jja89849s6q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🏠 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN