T09 · Insecure Skill Coding Practices
- Location
SKILL.md:161- Finding
Body Videos Are Submitted Without an Explicit Consent Requirement
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill needs Review because it handles sensitive body-scan videos through an external scan workflow while omitting consent checks and requesting broad local command and file permissions.
Only install this after confirming the skill will be used with explicit consent from the depicted person, with clear disclosure of where videos and measurements are sent, how long they are retained, and how they can be deleted. Prefer a version with narrowly scoped scan tools instead of broad read/write/exec authority.
SKILL.md:161Body Videos Are Submitted Without an Explicit Consent Requirement
SKILL.md:17Skill Requests General Command Execution and Filesystem Access Beyond Its Documented Needs
The skill positively promotes the absence of an explicit consent process as a convenience feature for privacy-sensitive real-person video handling. Because the content involves body scans and biometric-like measurements, encouraging operation without consent directly creates severe privacy, legal, and abuse risks, including unauthorized processing of another person's intimate data.
The top-level trigger/use description is broad enough to activate the skill for loosely related AnthroVision/Telegram requests without a sharply bounded task definition. Over-broad trigger criteria are dangerous because they can cause the skill to engage in contexts where sensitive media or personal data should not be handled automatically.
The skill explicitly documents that it does not provide an explicit consent process while handling real-person body videos, which are highly sensitive biometric/privacy-related inputs. In this context, omitting a mandatory consent gate materially increases the risk of unauthorized collection, processing, and disclosure of intimate user data through an external service.
The Chinese trigger statement says the skill auto-activates for generic 'Productivity' tasks, which is far broader than Telegram-based body measurement. This can unintentionally route unrelated content or files into a privacy-sensitive skill that also advertises external processing and powerful tools.
The skill asks users to submit body videos but does not provide an upfront warning that those videos and derived measurements are transmitted to an external service for processing. In a privacy-sensitive workflow, lack of prominent disclosure undermines informed consent and increases the risk of users sharing intimate data without understanding where it goes.
By normalizing a workflow that processes real-person body videos without an explicit consent step, the documentation creates a natural-language pathway for privacy-invasive use. The surrounding context makes this more dangerous because the skill is specifically about extracting body measurements from video, which is sensitive personal data.
The documentation advertises weight, body-fat percentage, and health-assessment style use cases even though the earlier scope says the free version only returns basic body measurements such as chest, waist, and hip. This overclaim can mislead users into relying on unprovided or unvalidated outputs in health-related contexts, which is risky given the sensitive nature of biometric data.
Framing privacy-sensitive video collection as simpler because consent is not required encourages insecure and potentially abusive handling of sensitive user data. This is especially risky in a body-scanning skill because operators may interpret the text as approval to upload intimate videos without verifying consent or legal basis.
The skill manifest presents a narrow Telegram body-scan function, but later text claims unrelated generic productivity, batch processing, and automation behavior. This mismatch can cause over-broad invocation and unsafe operator assumptions about what the skill is allowed to do, increasing the chance that sensitive data is routed through unintended flows.
Claiming generic file processing and system command execution for a Telegram body-measurement skill expands the perceived authority of the skill beyond its stated purpose. In a skill ecosystem, such unjustified capability claims can encourage unsafe use of powerful tools like exec or write in contexts unrelated to scanning, increasing misuse risk.
No suspicious patterns detected.