Nutritionist Video
v1.0.0Creates tailored 60-90 second nutrition coaching videos combining dietitian credentials, client needs, and condition-specific education for effective client...
⭐ 0· 36·0 current·0 all-time
by@udnerc
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 match the SKILL.md instructions: gather practitioner credentials, specialization, client details, and produce a 60–90s script plus B-roll suggestions. Nothing requested (no binaries, no env vars, no installs) is unexpected for this purpose.
Instruction Scope
Instructions explicitly tell the agent to gather client demographic, lab work, food history, and outcome data — which is coherent for tailoring videos but involves sensitive health information (PHI). The SKILL.md does not specify constraints on collecting, anonymizing, storing, or transmitting that data, nor does it limit use to ephemeral, in-session context.
Install Mechanism
Instruction-only skill with no install spec and no code files. This minimizes code-execution and supply-chain risk.
Credentials
The skill requests no environment variables or credentials (proportionate). However, because it asks for potentially sensitive client data, operators should consider whether platform-level credentials or storage mechanisms (not declared here) would be used to save or publish videos; the skill provides no guidance about that.
Persistence & Privilege
always:false and no install or config writes. The skill can be invoked autonomously (platform default), which is expected for an agent skill; there is no request for permanent presence or cross-skill config changes.
Assessment
This skill appears coherent and low-risk from a platform/installation perspective, but it expects you to provide client health details (lab work, food history, outcomes). Before installing or using it: 1) Confirm your platform and workflow meet privacy requirements (e.g., HIPAA) and that you have client consent to use any PHI. 2) Prefer supplying de-identified or synthetic example data when testing. 3) Decide and document whether generated scripts/videos will be stored, published, or logged, and ensure storage/publishing channels are secure. 4) If you want stricter control, restrict autonomous invocation or require explicit user confirmation before the skill is allowed to collect or use client-specific details. 5) If clinical accuracy or legal disclaimers are important, add instruction-layer guards (e.g., include a required disclaimer in outputs and avoid making direct medical claims beyond the practitioner's scope).Like a lobster shell, security has layers — review code before you run it.
latestvk974rmzeq265zegj8mwk5hy6yd84190x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.