Response Speed Test

Measures OpenClaw system response times by testing stages, providing millisecond precision metrics like TTFT, TPS, and total response time.

This skill appears to implement the described timing/benchmark functionality, but review before installing: 1) Note that it reads environment variables (OPENCLAW_GATEWAY_URL, LLM_API_URL, LLM_MODEL, SOUL_MEMORY_PATH, OPENCLAW_STATE_DIR) even though the registry declares none — set them intentionally or leave defaults. 2) It inspects local paths (defaulting to /root/.openclaw/...), including listing .md files and reading index.json; if those directories contain sensitive data, run the skill in a restricted/sandboxed environment or point SOUL_MEMORY_PATH/OPENCLAW_STATE_DIR to a safe location. 3) There are no network calls in the current code, but LLM/Gateway probes are written to be extended to call APIs — verify any modifications that add network I/O. 4) Prefer installing from a trusted source (the pyproject references a GitHub repo); check the repository URL and author before running 'clawhub install' or running code locally. If you want, I can list the exact lines that read environment variables and file paths so you can audit them.

Type: OpenClaw Skill Name: response-speed-test Version: 1.0.0 The 'response-speed-test' skill is a performance benchmarking tool designed to measure OpenClaw system latency across various stages, including Gateway processing, Memory loading, and LLM response times (TTFT/TPS). While the probes in 'probes/memory_probe.py' and 'probes/session_probe.py' access internal OpenClaw directories and environment variables, this behavior is consistent with the stated purpose of system-level performance monitoring. The code is transparent, lacks obfuscation, and contains no evidence of data exfiltration, unauthorized remote execution, or malicious prompt injection.