Cache Performance Optimizer Skill for Hit-Rate Comparisons
Compare cache outcomes under the same request sequence and verify whether origin reads and latency change.
中文Install in Claude Code
Use your test app and cache metrics. Use the same synthetic keys and record the starting cache state for each window.
- Get the complete `plugins/performance/cache-performance-optimizer/skills/optimizing-cache-performance` directory from the pinned GitHub commit.
- Copy it into the target project's `.claude/skills/`. Check `.claude/skills/optimizing-cache-performance/SKILL.md`, start Claude Code at the project root, and call `/optimizing-cache-performance`.
Example task
Collect two sets of counters from the same 100 requests. Start with 60 hits and compare with 75 hits, recording origin reads as well.What to check
Hit rate rises from 60% to 75%, or 15 percentage points. Origin-read counts remain independently reviewable.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does a higher hit rate mean every request is faster?
Also inspect latency distribution, cache overhead, and miss behavior. Hit rate covers only one part of performance.