Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Passive Vital Signs Monitoring Tool | 无感生命体征监测分析工具
v1.0.0Non-contact detection of heart rate, respiration, blood oxygen, and heart rate variability. No wearable devices are required; monitoring is achieved solely t...
⭐ 0· 36·0 current·0 all-time
bysmyx-skills@18072937735
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The main scripts implement contactless vital-sign analysis and call an external API — this matches the stated purpose. However, the bundle also includes a large shared 'smyx_common' library and a separate 'face_analysis' skill with many unrelated utilities and a large dependency list, which is broader than what a minimal vital-sign monitor would need. The skill does not declare any required credentials or config in its top-level metadata even though its runtime expects API keys/open-id and remote endpoints configured via local yaml files.
Instruction Scope
SKILL.md instructs the agent to (a) read local config files under skills/smyx_common/scripts/config.yaml and possibly workspace-level configs to obtain open-id/api-key, (b) automatically save uploaded attachments to an attachments directory, and (c) always fetch historical reports from the cloud API. Those instructions require reading and writing workspace files and contacting external services; the file-level persistence and workspace config reads are privacy-sensitive and broader than the description emphasizes. The skill also forbids reading certain local memory stores, but the code still reads other local config and may create files/DBs.
Install Mechanism
There is no install spec (instruction-only), which reduces automatic-install risk. However the package includes many Python modules and requirements.txt files (a large third-party dependency list) that a user would likely need to install manually; that is heavier than expected for a simple video-to-API wrapper. No remote download URLs or extract/install steps were found.
Credentials
Metadata lists no required env vars or credentials, yet runtime code expects open-id and may use API keys configured in local YAMLs; ConstantEnum also reads OPENCLAW_SENDER_OPEN_ID, OPENCLAW_SENDER_USERNAME, and FEISHU_OPEN_ID environment variables if present. The skill therefore relies on credentials/config not declared in the registry metadata — a mismatch that can hide where sensitive values are used or stored.
Persistence & Privilege
The code writes files: uploaded attachments are saved under the skill directory, YAML config loader will create config files if missing, and Dao creates an SQLite DB under the workspace/data path. These are persistent filesystem changes in the user's workspace and thus increase blast radius and privacy impact. 'always' is false, but autonomous invocation is allowed (default) which combined with persistent writes is noteworthy.
What to consider before installing
Key points before installing or enabling this skill:
- It contacts external APIs (configured via skills/smyx_common config) and will upload/process face videos — these are highly sensitive personal data (face + health metrics). Only use if you trust the remote service/domain (config yaml points to lifeemergence/open.lifeemergence URLs in this package).
- The skill will read workspace-local config files and environment variables to obtain open-id / API keys, but the registry metadata does not declare those required credentials. Inspect skills/smyx_common/scripts/config.yaml and any workspace config before use to see where keys or endpoints are set.
- Uploaded videos are saved to the skill's attachments directory and an SQLite DB under workspace/data may be created; if you want no local persistence, run the skill in an isolated/sandboxed workspace or ephemeral container.
- The repository includes broad shared libraries and many dependencies. If you plan to run the included Python code, review the code (RequestUtil, dao, and api_service) and the endpoints they call; consider running in a controlled environment and restrict network access until you confirm behavior.
- If you only want the concept (advice about how to use a camera for vital signs) and not the remote service, avoid handing over videos or workspace credentials. If you proceed, ask the skill author which endpoints will receive raw video and whether data is stored/retained server-side, and prefer explicit API keys that you control.
If you want, I can (a) list the exact files that read/write configs or the DB, (b) extract the external base URLs found in the config YAMLs, or (c) suggest a minimal, safer runtime checklist for sandboxing this skill.skills/smyx_common/scripts/config-dev.yaml:2
Install source points to URL shortener or raw IP.
About static analysis
These patterns were detected by automated regex scanning. They may be normal for skills that integrate with external APIs. Check the VirusTotal and OpenClaw results above for context-aware analysis.Like a lobster shell, security has layers — review code before you run it.
latestvk978t754s8bdngkbs6w3pan2x584tah1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.