Reptile Pet Health Diagnosis Tool | 爬行类宠物健康诊断分析工具

Analyzes uploaded reptile or arachnid videos to identify scale, skin, and body issues, then generates a detailed health diagnosis report.

Key points to consider before installing or running this skill: - Mismatch: SKILL.md forbids reading local memory and instructs all history queries to come from the cloud, but the code (skills/smyx_common and dao) will load and may create YAML config files and stores/reads a local SQLite DB under a workspace data directory. Expect persistent files (attachments, DB) to be created. - Undeclared env vars: The code reads OPENCLAW_WORKSPACE, OPENCLAW_SENDER_OPEN_ID / OPENCLAW_SENDER_USERNAME, and FEISHU_OPEN_ID to populate defaults; these were not declared in the skill metadata. If you run this, be aware the skill can read those environment variables. - Data handling: Uploaded videos may be saved locally (attachments) and reports cached in a local DB. If you have privacy concerns about video files or report data being written locally, do not run this on a sensitive host or review/modify code first. - Verify endpoints and RequestUtil: The skill delegates HTTP calls to RequestUtil and uses configured base URLs (skills/smyx_common/scripts/config.yaml and config-prod/test/dev). Confirm the API base URLs (e.g., lifeemergence.com paths in provided config) are expected and safe, and inspect RequestUtil implementation to see how requests are authenticated and where data is sent. - Open-id behavior: SKILL.md requires a strict open-id retrieval flow (checking specific config files and asking the user if missing). But the code also accepts environment variables and command-line --open-id. Decide which method you trust, and do not supply sensitive identifiers if you don't want them stored or transmitted. - Run in sandbox first: If you want to test, run the skill in an isolated environment (container or throwaway VM) so you can observe what files it creates, what network endpoints it contacts, and whether it stores data locally. - If you need stricter guarantees: ask the author to clarify and reconcile SKILL.md rules with code (explicitly list env vars used, confirm that local DB will not be used for history queries, or remove local persistence), or strip/inspect the smyx_common components before use. Confidence note: The assessment is 'suspicious' with medium confidence because the repo contents clearly implement remote analysis but also contain local persistence/config behavior that conflicts with the written prohibitions; nothing in the inspected code is an explicit sign of intentional malicious behavior, but the inconsistencies and undeclared environmental/file access warrant caution.