Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
WonderDash
v1.0.0Create and manage widgets on the user's WonderDash mobile dashboard via GitHub
⭐ 0· 327·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
Name/description (manage widgets via GitHub) match the actions described (creating JSON files, committing, pushing). Declaring git+ssh as required binaries is appropriate. However, the runtime instructions explicitly require an SSH private key and a repo URL to be supplied by 'WonderDash', yet the skill metadata in the registry lists no primary credential or required env — a documentation/metadata mismatch that should be explained by the publisher.
Instruction Scope
The SKILL.md stays within the stated purpose: it instructs creating/updating widget JSON files, editing dashboard.json, and using git push/clone via SSH. It only references the user's ~/.ssh files and the target GitHub repo; it does not instruct reading other unrelated files or accessing external endpoints beyond GitHub.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal filesystem/installation risk. It relies on standard system binaries (git, ssh) which are reasonable for the task.
Credentials
Although no env vars are declared, the runtime setup explicitly requires an SSH private key (sensitive credential) and storing it under ~/.ssh/wonderdash_deploy. The skill does not declare this credential in registry metadata (primary credential/required env), so the requested secret is not visible ahead of install — that's a mismatch and a security concern because the key grants repo write access and could be misused if it has broad scope or is reused elsewhere.
Persistence & Privilege
The skill does not request 'always: true' and does not modify other skills or system-wide settings. Instructions tell the user to write a private key and an SSH config entry into the user's home directory (normal for GitHub deployment keys), which is expected for this functionality but should be done deliberately and with least privilege.
What to consider before installing
This skill's behavior (reading/writing widgets in a GitHub repo via SSH) is consistent with its description, but it requires you to supply and save an SSH private key — something the registry metadata does not declare. Before installing or using it: 1) Verify the publisher and the repository URL out-of-band; do not paste a reusable personal SSH key. 2) Prefer a dedicated, least-privilege credential: a repo-scoped deploy key or a machine account with only the minimum permissions needed (ideally read-only if you only need to pull, or a tightly-scoped write key only for this repo). 3) Audit widget HTML before committing (webview widgets can include JavaScript that may run in the app). 4) Avoid reusing the key elsewhere and rotate/delete the key when no longer needed. 5) If possible, prefer a workflow where changes go through pull requests and human review instead of allowing direct pushes by an automated agent. Finally, ask the skill publisher why the registry metadata omits the credential requirement — that inconsistency should be resolved.Like a lobster shell, security has layers — review code before you run it.
latestvk970nhbzw5vd1wm5tgsq906fgn82d6fk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis
OSmacOS · Linux
Binsgit, ssh