Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Play Any Game - AI游戏伴侣助手
v1.4.1AI游戏伴侣助手 - 当你在游戏中遇到困难、卡关、不知道怎么操作时，AI可以帮你分析游戏画面、解答问题、甚至简单操作界面帮你解决问题。不是全自动代肝，而是你的游戏伙伴，在你需要的时候伸出援手。当用户提到"帮我看下这个怎么过"、"这个怎么操作"、"卡关了"、"不知道怎么弄"时使用此技能。支持原神、崩坏星穹铁道等各类游戏。
⭐ 0· 167·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description match what the code implements (screenshot analysis, UI recognition, mouse/keyboard control). However the registry metadata declares no required environment variables or primary credential while SKILL.md and the code require an API key (DASHSCOPE_API_KEY) for a cloud GUI model. That mismatch (declared no env vs runtime instructions requiring a secret) is an incoherence and should be clarified.
Instruction Scope
Runtime instructions request capturing screenshots, saving them under screenshots/, and sending them to a cloud GUI-Plus model (Aliyun) for multimodal recognition; they also direct local mouse/keyboard and background window message clicks. These actions are consistent with the stated purpose but involve collecting and uploading user screenshots and controlling the local input subsystem — both are privacy- and security-sensitive and should be explicitly disclosed to users.
Install Mechanism
No opaque remote download/install spec is present; installation is via pip installing requirements.txt (pywin32, Pillow, opencv-python, numpy, openai). This is a typical and traceable mechanism. There is no evidence of arbitrary binary downloads from untrusted URLs in the provided files.
Credentials
Although registry metadata lists no required env vars, SKILL.md instructs storing an API key (DASHSCOPE_API_KEY) in config.json or as an env var and uses it to call a cloud model. Requesting a cloud API key is proportionate to the image-recognition feature, but the metadata omission is inconsistent. Also the skill persists the API key to config.json (albeit .gitignored), which raises risk if the file is not handled correctly. The use of the 'openai' client (per requirements) to call Aliyun GUI-Plus is unusual and should be audited to confirm endpoints.
Persistence & Privilege
The skill does not request 'always: true' or system-wide privileges. It writes config.json and stores screenshots under its screenshots/ directory, which is expected for this functionality. It performs local mouse/keyboard actions and may run in background mode; those are necessary for its purpose but are privileged actions on the host and should be allowed only by users who understand the risk.
What to consider before installing
Before installing, note these points:
- Metadata mismatch: The skill's registry entry says no environment variables are required, but the documentation and code require an API key (DASHSCOPE_API_KEY). Confirm with the author why the registry omitted this requirement.
- Privacy: The skill captures screenshots of your game window and (per docs) sends them to a cloud service (Aliyun GUI-Plus) for analysis. Do not use this skill if those screenshots might contain sensitive information you do not want uploaded.
- API key handling: The skill stores the API key in a local config.json by default. Ensure that file is stored securely and not committed or shared. Consider using temporary keys or scoped accounts if possible.
- Local control risk: The skill can move your mouse, send keystrokes, and perform background PostMessage clicks. That capability is necessary for automation but can affect other applications. Only run it on a machine/account where you accept this level of control.
- Implementation oddities: The project uses the 'openai' Python client in requirements but documents Aliyun GUI-Plus as the provider. Review scripts/gui_agent/aliyun.py (network endpoints, upload behavior) to confirm where images and keys are actually sent. Also scan the code for TODOs or obvious bugs (there are at least some small code issues) before running.
- Mitigations: Run initially in a controlled environment (non-critical account, VM, or sandboxed Windows user), inspect network traffic (to see which endpoints are used), and rotate API keys if you test the skill. If you need assurance, ask the maintainer to (1) update registry metadata to declare the API key requirement, (2) document exact endpoints used and whether images are persisted server-side, and (3) provide an option to run the recognition model locally or with a self-hosted endpoint.scripts/recognition.py:54
Dynamic code execution detected.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk977sbencbe492a8yskxt0n7fx84gctx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.