skill-perf
v1.0.1测量 OpenClaw 环境中 Skill 的 token 消耗和性能开销（仅适用于 OpenClaw Agent 环境）。当用户提到「测量」「测试」「性能」「token 消耗」「多少 token」「开销」「成本」「效率」或想要评估、对比、优化某个 skill 的资源使用时，立即使用此 skill。也适用于 sk...
⭐ 0· 62·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (measure token consumption and performance of OpenClaw skills) align with the SKILL.md content. The skill does not request unrelated binaries, env vars, credentials, or config paths.
Instruction Scope
SKILL.md instructs the agent to use OpenClaw's sessions_spawn to create dual subagents to perform concurrent measurements, subtract system baseline noise, and generate HTML reports with confidence ratings. This behavior is coherent for a benchmarking tool, but it requires the platform's session-spawn capability and will create ephemeral subagents that run code/requests — ensure those subagents are isolated and not given access to sensitive data.
Install Mechanism
No install spec and no code files — instruction-only reduces installation risk. Nothing is downloaded or written to disk by an installer.
Credentials
Skill declares no required environment variables, credentials, or config paths. There are no disproportionate or unexplained secret requests.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not request permanent presence or system-wide configuration changes.
Assessment
This skill appears coherent and low-risk in terms of declared requirements, but it relies on the agent runtime to spawn subagents (sessions_spawn). Before installing or invoking it: 1) Confirm your OpenClaw runtime safely isolates spawned subagents and that subagents cannot access unrelated secrets or privileged resources. 2) Run the skill in a sandbox or with non-sensitive test data first to verify reports do not leak confidential information. 3) Review platform audit logs for spawned sessions when running benchmarks. 4) Avoid granting this or other benchmarking steps access to production credentials; provide only the minimal test environment needed.Like a lobster shell, security has layers — review code before you run it.
latestvk978agz69tmg6623zh3t27zsnx8409h4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📊 Clawdis