Human Pose Recognition Skill | 人体姿态识别技能

Recognizes various poses such as standing, sitting, lying down, bending, raising hands, running, and falling. Supports abnormal pose recognition and fall war...

Key things to check before installing or invoking this skill: - Confirm endpoints and credentials: The skill calls external API endpoints configured under skills/smyx_common/scripts/config.yaml (base-url-open-api/base-url-health). Make sure those URLs are trusted and that you intend to send video (or URLs) to them. API key fields are present but empty in the provided config — do not provide real production credentials until you verify the service. - Clarify open-id handling: The SKILL.md mandates retrieving an open-id from specific config files or user input and forbids generating one. The code also reads environment variables (OPENCLAW_SENDER_OPEN_ID, FEISHU_OPEN_ID) as fallbacks. Decide whether you will provide a real user identifier; avoid using sensitive user IDs or credentials until you trust the backend service. - Watch for local writes: The shared smyx_common utilities will create config YAMLs and can create a local SQLite DB under the workspace data directory. If you need a no-persistence runtime, run the skill in an isolated container or sandbox and verify file-write behavior. - Note mismatches in documentation vs code: SKILL.md says 100MB max video; the code enforces ConstantEnum.MAX_FILE_SIZE_MB which defaults to 10MB. Adjust whichever is authoritative and test with expected file sizes. - Dependency scope: There is no automatic installer, but the included requirements files list many packages. If you install dependencies, be aware of the broad dependency surface and install into a controlled virtual environment. - Confirm attachment behavior: SKILL.md says uploaded attachments will be saved into an attachments folder — search the codebase for explicit save behavior or prefer to supply local file paths yourself. Do not assume automatic attachment handling without verifying. - Run in an isolated environment and review runtime network calls: Because the skill sends video (or video URLs) to remote services, test within a controlled environment (network monitor/proxy) to confirm what is transmitted. If you cannot verify the remote service, avoid sending real personal videos. If you want, I can: - List exact files/functions that create or write local config/DB files - Highlight each place where the code uses environment variables or constructs external URLs - Suggest minimal hardening steps or a safe invocation checklist (sandboxing, dummy open-id, limited test files).