claude-speed-test

Benchmark Claude Code startup and response times across CLAUDE_CONFIG_DIR locations.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/tankygranny05/agent-box --skill claude-speed-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-speed-test
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/claude-skills/claude-speed-test
Command: npx skills add https://github.com/tankygranny05/agent-box --skill claude-speed-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you identify the fastest configuration for Claude Code by benchmarking its startup and response times across different settings.

Core Features & Use Cases

  • Benchmark Configurations: Compares the performance of default Claude configurations against isolated, fresh ones.
  • Measure Latency: Provides detailed timing data for each trial, including mean, standard deviation, min, and max response times.
  • Use Case: When experiencing slow responses from Claude Code, use this Skill to pinpoint which configuration (e.g., default vs. a temporary directory) yields the quickest results.

Quick Start

Run the benchmark script to test Claude Code startup and response times.

Frequently Asked Questions about claude-speed-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I benchmark Claude Code startup and response times?

To benchmark Claude Code startup and response times, run Python scripts that execute timed trials across different CLAUDE_CONFIG_DIR locations, capturing detailed performance metrics including mean, standard deviation, min, and max elapsed times.

Why does Claude Code have slow response times on my machine?

Slow Claude Code response times may stem from your configuration. Benchmarking performance across different CLAUDE_CONFIG_DIR locations identifies whether a default or isolated fresh configuration yields reduced latency.

How do I test Claude Code latency across different configurations?

You test Claude Code latency by running benchmark scripts that compare performance across different CLAUDE_CONFIG_DIR locations, logging elapsed time, stdout, and stderr for each timed trial.

What is the best way to find the optimal configuration for Claude Code performance?

The best way to find the optimal configuration for Claude Code performance is benchmarking startup times across different CLAUDE_CONFIG_DIR settings to identify which configuration yields the quickest results.

Can I measure Claude Code latency using Python scripts?

Yes, you can measure Claude Code latency using Python scripts that execute timed trials, capture environment variables, and log detailed performance metrics including elapsed time for each run.

Does benchmarking Claude Code require any external dependencies?

Benchmarking Claude Code does not require external dependencies. It utilizes Python scripts to execute timed trials and capture environment variables, logging performance metrics without additional packages.