ℹ
Purpose & Capability
The declared purpose (detect infant blanket-kicking from video and alert parents) aligns with the core scripts (infant_blanket_kick_monitoring_analysis.py and skill wrapper). However the package also bundles a large 'smyx_common' utility layer and an unrelated 'face_analysis' skill (traditional Chinese medicine face diagnosis) and a heavy requirements list. Including a general-purpose DAO/SQLite layer, extensive API enum/config management, and an unrelated face-analysis skill is broader than necessary for a narrowly scoped blanket-kick detector and suggests the bundle contains more functionality and surface area than the description implies.
⚠
Instruction Scope
SKILL.md forbids reading local 'memory' and long-term LanceDB memory, but the runtime instructions explicitly demand reading local config files (skills/smyx_common/scripts/config.yaml and workspace config) to get open-id and API keys. The skill also instructs saving uploaded video attachments into an attachments directory and the codebase includes a DAO that writes a local SQLite DB under the workspace/data path. The instructions therefore both mandate and perform local filesystem reads/writes and network calls: they may store sensitive video files locally and will upload them to external APIs. The prohibition against reading memory files is contradictory with other local file usage requirements, increasing risk of accidental data leakage or persistent storage of PII.
✓
Install Mechanism
This is instruction- and code-bundle only (no external download/install spec). Nothing in the metadata triggers an external arbitrary download during install. However the repository includes a large requirements list (skills/smyx_common/requirements.txt and face_analysis requirements) that, if installed in a runtime, would pull many packages — the absence of an install spec reduces immediate install-time risk but the code expects third-party packages (requests etc.) at runtime.
⚠
Credentials
The registry metadata lists no required env vars or credentials, but the code and SKILL.md expect API keys/open-id to appear in local config files or environment (ConstantEnum.init reads OPENCLAW_SENDER_OPEN_ID, OPENCLAW_WORKSPACE is consulted by DAO). The skill will use API_KEY/API URL settings from skills/smyx_common config or workspace configs and accepts an --api-key parameter. This mismatch (no declared secrets but clear implicit reliance on API keys, open-id, and workspace environment) is disproportionate and obscures what secrets are needed and where they go.
⚠
Persistence & Privilege
always:false and model invocation allowed (normal). But the skill explicitly saves uploaded attachments to the skill directory and the included DAO creates/uses a local SQLite DB under a workspace data directory. That means user videos and records may be persisted on disk by the skill. The skill does not request elevated platform privileges, nor does it modify other skills, but the persistent storage of sensitive video/metadata by default increases privacy risk and persistence beyond a single session.