← Back to Skills Marketplace
djc00p

performance-benchmark

by Deonte Cooper · GitHub ↗ · v1.0.2 · MIT-0
linuxdarwinwin32 ✓ Security Clean
180
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install performance-benchmark
Description
Measure performance baselines, detect regressions, and compare stack alternatives before/after changes. Modes: page performance (Core Web Vitals), API latenc...
Usage Guidance
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.
Capability Assessment
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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install performance-benchmark
  3. After installation, invoke the skill by name or use /performance-benchmark
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Fixed metadata: clarified benchmark tool requirement with examples (k6, autocannon, hyperfine); standardized benchmark storage path to .benchmarks/; added production safety warning
v1.0.1
Fix: replace bare code blocks with ```text for consistent rendering
v1.0.0
Initial release. Performance benchmarking for Web Vitals, API latency, and build speed. Adapted from everything-claude-code by @affaan-m (MIT)
Metadata
Slug performance-benchmark
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is performance-benchmark?

Measure performance baselines, detect regressions, and compare stack alternatives before/after changes. Modes: page performance (Core Web Vitals), API latenc... It is an AI Agent Skill for Claude Code / OpenClaw, with 180 downloads so far.

How do I install performance-benchmark?

Run "/install performance-benchmark" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is performance-benchmark free?

Yes, performance-benchmark is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does performance-benchmark support?

performance-benchmark is cross-platform and runs anywhere OpenClaw / Claude Code is available (linux, darwin, win32).

Who created performance-benchmark?

It is built and maintained by Deonte Cooper (@djc00p); the current version is v1.0.2.

💬 Comments