Skill Dashboard

像管手机 APP 一样管你的 AI 技能——分页显示、一键巡查、轻松管理

This skill is plausibly what it says (a local dashboard) but there are red flags you should consider before installing: - Metadata mismatch: SKILL.md says it requires 'jq' but the package metadata and code do not—ask the maintainer to clarify and provide an updated package manifest. - Command execution risk: the code uses shell exec (clawhub inspect/update/uninstall, open) with parameters that can come from parsed text or user input. If an attacker can cause a crafted skill name to be processed, it could lead to shell injection. Ask the developer to sanitize inputs or use execFile/spawn with argument arrays. - File/path assumptions: dev-dashboard reads a sibling skill-state file via a relative path; confirm install layout so it doesn't accidentally read unrelated files. - Operational impact: the skill will call clawhub update/uninstall, which can modify or remove other skills. Confirm you trust the skill and the clawhub CLI on your system. Recommended actions before installing: 1. Review the source (the included JS files) yourself or ask the author to explain the jq metadata and the relative path usage. 2. Verify clawhub CLI is legitimate and required; consider running the code in a sandbox or review/modify it to use safer child_process APIs (pass arguments as arrays, validate slugs against a strict pattern). 3. If you plan to use it, ensure backups for your skills, and only allow confirmed update/uninstall actions. If the maintainer can address input sanitization and fix the manifest inconsistencies, this would lower my concern.

Type: OpenClaw Skill Name: skill-dashboard Version: 2.0.4 The skill bundle contains a critical shell injection vulnerability (Remote Code Execution risk) in `dashboard.js`, `commands/uninstall.js`, and `commands/update.js`. User-provided skill names, parsed by `pagination.js`, are directly interpolated into `child_process.exec` calls (e.g., `clawhub update ${skillSlug}` or `clawhub uninstall ${skillSlug}`) without proper sanitization. This allows an attacker to inject arbitrary shell commands by crafting a malicious skill name. While there is no evidence of intentional malicious behavior (e.g., data exfiltration, persistence), this severe vulnerability makes the skill suspicious.