cache-audit

Audit Claude Code prompt caching configurations and generate scored fix reports.

31|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Pouzor/pilotarr --skill cache-audit-pouzor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cache-audit
Source: https://github.com/Pouzor/pilotarr/tree/main/.claude/skills/cache
Command: npx skills add https://github.com/Pouzor/pilotarr --skill cache-audit-pouzor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and rectifies common misconfigurations in Claude Code prompt caching, ensuring optimal performance and cost-efficiency.

Core Features & Use Cases

  • Comprehensive Auditing: Analyzes system prompt ordering, dynamic content injection, tool stability, model switching, and data size.
  • Actionable Reporting: Provides a scored report with specific, prioritized fixes.
  • Use Case: Ensure your Claude Code setup adheres to Anthropic's best practices for prompt caching to prevent unexpected costs and improve response reliability.

Quick Start

Run the cache-audit skill to check your current Claude Code prompt caching configuration.

Frequently Asked Questions about cache-audit

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

FAQPage Schema
How do I audit Claude Code prompt caching configurations?

Auditing Claude Code prompt caching involves analyzing system prompt ordering, tool stability, dynamic content handling, and hook injection patterns against best practices. This skill generates a scored report with actionable fixes to optimize performance and cost.

Why does prompt caching increase costs in Claude Code?

Prompt caching costs in Claude Code often increase due to misconfigurations like unstable system prompts, dynamic content injection, or model switching. Auditing these configurations against best practices identifies specific areas causing unexpected costs.

What are the best practices for ordering system prompts for caching?

Best practices for ordering system prompts for caching involve placing stable content first and dynamic content last. This skill audits your configuration to ensure optimal ordering, tool stability, and hook injection patterns for reliable response generation.

Can I check if my Claude Code setup supports prompt caching correctly?

Yes, you can check if your Claude Code setup supports prompt caching correctly by running an audit. This skill analyzes your configuration's data size, model switching behavior, and dynamic content handling to provide a scored report.

How do I fix prompt caching misconfigurations in Claude Code?

Fixing prompt caching misconfigurations in Claude Code requires identifying issues in system prompt ordering and tool stability. This skill provides an actionable, prioritized report to rectify common misconfigurations and improve performance.

What is the best way to optimize Claude Code prompt caching?

The best way to optimize Claude Code prompt caching is to audit configurations for ordering, dynamic content, and hook injection patterns. This skill provides a scored report with actionable fixes to ensure optimal performance and cost-efficiency.