ClawHub

Medical Device Explainer Video

v1.0.0

Your medical device has cleared FDA 510(k), your clinical data shows a 34% reduction in procedure time, and your sales team has twelve hospital meetings next...

⭐ 0· 28·0 current·0 all-time
by@siddylcon
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (create explainer/training videos) matches the declared credential (NEMO_TOKEN) and the SKILL.md curl call to mega-api-prod.nemovideo.ai. Requiring an API token for a third‑party video generation service is expected.
ℹ
Instruction Scope
The runtime instructions are narrowly scoped: they POST user-supplied device and audience data to the Nemo API using $NEMO_TOKEN and do not instruct reading other files or unrelated env vars. Minor inconsistency: metadata declares a config path (~/.config/nemovideo/) that the SKILL.md does not reference; this could be benign (optional local config) but is worth checking.
✓
Install Mechanism
No install step or downloaded artifacts are declared (instruction-only). This is the lowest-risk install profile.
✓
Credentials
Only one credential (NEMO_TOKEN) is required, which is proportionate for an API-backed video-generation skill. Consider verifying the token's scope/permissions and the service's data handling practices before providing it.
✓
Persistence & Privilege
Skill is not forced-always, and does not request system-wide changes or elevated privileges. Autonomous invocation is allowed (platform default) but not combined with other concerning flags.
Assessment
This skill appears internally consistent: it calls a single external Nemo Video API and needs only an API token. Before installing, verify the Nemo service is trustworthy and contractually suitable for clinical data (HIPAA/PHI handling, BAA if applicable), confirm what the NEMO_TOKEN can access and how long uploaded data/videos are stored, and avoid including identifiable patient data in requests. Also check whether the optional local config path (~/.config/nemovideo/) will be used by your environment and whether the token is stored/rotated securely.

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

latestvk971jxjtrakbs3qx4erkkq1s41848nj8

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🏥 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN

Comments