Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Agent Benchmark
v0.1.0通过12个标准化任务自动评估AI Agent在文件操作、数据处理、系统操作、健壮性与代码质量五大维度的综合能力。
⭐ 0· 60·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 stated purpose (agent capability benchmark) aligns with the included tasks and scoring logic. However the SKILL.md emphasizes a PowerShell runner (src/benchmark-runner.ps1) while the repository contains a Node.js index.js that implements a runner and executes arbitrary language code (python/node/go). The package metadata declares no required binaries, yet index.js expects interpreters/runtimes (python, node, go). This mismatch is disproportionate to the documented purpose and should be clarified.
Instruction Scope
SKILL.md instructs users to run a PowerShell script (src/benchmark-runner.ps1) and includes PowerShell task scripts, but the actual executable logic is index.js (Node). index.js writes files, creates temp directories, writes and executes user-supplied code (from tasks.json/tasks) by spawning child processes, and includes behavior not documented in SKILL.md. The instructions in SKILL.md do not fully describe what will be executed on the host.
Install Mechanism
There is no install spec (instruction-only claimed), which is lower risk, but the package contains Node code that will be executed if you run it. The tool expects external runtimes (python/node/go) though no required-binaries are declared. No remote download or obscure URLs are present in the package, which reduces installer risk, but the lack of declared runtime requirements is an inconsistency.
Credentials
The skill does not declare required environment variables, which matches registry metadata. index.js spawns processes inheriting process.env and some benchmark tasks intentionally read environment variables (task-011). That's reasonable for 'system operations' tests, but reports capture task outputs (which may include env values) and the tool will persist those outputs—so running tasks that print sensitive environment values could leak them into local reports.
Persistence & Privilege
index.js generates reports and explicitly writes a report to a relative '../../memory/benchmark-results.md' (i.e., escapes the package directory). Writing into a 'memory' path outside the skill directory can place results into agent persistent storage; SKILL.md did not document this. The skill is not marked always:true, but this unexpected persistent write and the discrepancy between documented runner and shipped Node runner is a privilege/persistence concern and should be clarified.
What to consider before installing
What to consider before installing/running:
- Clarify the runner: SKILL.md describes a PowerShell runner, but the package includes index.js (Node) that actually runs tasks. Ask the author which runner is intended.
- Runtimes required: index.js may spawn python, node, and go; the registry metadata declares no required binaries. Ensure you want those interpreters available on the host and that you trust code executed by them.
- Arbitrary code execution: the benchmark executes task-provided code by writing files and spawning interpreters. If you (or untrusted third parties) add tasks, they can run arbitrary commands with your user permissions. Run only in an isolated/sandbox environment or inspect tasks before execution.
- Persistent writes: the tool writes reports into a '../../memory' path outside the skill directory—inspect where that resolves in your environment and whether you want benchmark outputs (which may include environment values) stored persistently.
- Review tasks and index.js: before running, open tasks/*.json and index.js to confirm no task prints secrets or calls external endpoints; the provided files show no external network calls, but tasks can be extended.
- Safe deployment recommendations: run in a disposable VM or container, or run with restricted user privileges and no sensitive env vars present; consider removing support for languages you don't want to allow (or run the runner in a capability-restricted sandbox).
If you want, I can (1) point out the exact lines in index.js that create temp dirs, spawn child processes, and write to '../../memory', or (2) propose a safer runner configuration (e.g., disable python/go, restrict to dry-run mode).index.js:89
Shell command execution detected (child_process).
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.
latestvk973yvvwywecphr61v1qhb9p5183m6zb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.