performance-benchmark

v1.0.2

Measure performance baselines, detect regressions, and compare stack alternatives before/after changes. Modes: page performance (Core Web Vitals), API latenc...

0· 108·0 current·0 all-time
byDeonte Cooper@djc00p
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the SKILL.md describes page, API, and build benchmarking and expects external benchmark tools. It does not request unrelated credentials or binaries.
Instruction Scope
Instructions are coherent but high-level: they assume a 'benchmark' CLI and third-party tools (k6, autocannon, hyperfine) are present but do not provide or install them. The skill warns about load-testing production. Because it's an instruction-only skill, there is no hidden file I/O or unexpected external endpoints, but the lack of implementation means the agent or user must supply tooling.
Install Mechanism
No install spec and no code files — lowest-risk model. Nothing is downloaded or written by the skill itself.
Credentials
No environment variables, credentials, or config paths are requested. Requested storage location (.benchmarks/) is reasonable for baselines but should be reviewed for sensitive content.
Persistence & Privilege
Skill is not always-enabled and does not request elevated or persistent agent privileges. It does not modify other skills or system configuration.
Assessment
This skill is a coherent, instruction-only benchmarking guide — it does not install code or ask for credentials. Before using it: (1) ensure you have the benchmark tools it references (k6, autocannon, hyperfine, or a 'benchmark' CLI) or provide your own implementations; (2) never run load tests against production without explicit authorization — the SKILL.md includes the same warning; (3) review what you store in .benchmarks/ before committing (it may contain timing data or URLs you don't want public); (4) if you plan to run benchmarks from CI, ensure your runners and secrets are properly scoped; and (5) if you expect the skill to provide a runnable CLI, note it doesn't — you must map the documented commands to real tools or scripts. Overall this is internally consistent and does what it says.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ddw49qtp8fsq6zp65qmh65h84b4by

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

⏱️ Clawdis
OSLinux · macOS · Windows

Comments