cdn-caching-specialist

Diagnose and resolve CDN caching issues for web applications and static sites.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill cdn-caching-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cdn-caching-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/cdn-caching-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill cdn-caching-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve slow static asset delivery, stale or misconfigured CDN caches, high bandwidth usage from unoptimized assets, and cache invalidation failures that cause users to receive outdated content.

Core Features & Use Cases

  • Verify CDN health and configuration: check DNS, SSL, cache headers, and CDN dashboard signals to confirm assets are being served from the edge.
  • Cache header and TTL strategy: define Cache-Control rules by file type, set long TTLs for hashed assets, and short revalidation for HTML/APIs.
  • Versioning and invalidation: implement content hashing, purge via CDN APIs or invalidations, and establish safe purge policies for deployments.
  • Asset optimization: enable compression, modern image formats, lazy loading, and delivery optimizations to reduce bandwidth and improve cache hit ratios.
  • Monitoring and remediation: measure cache hit ratio, regional response times, bandwidth saved, and set alerts for cache misses or elevated error rates.

Quick Start

Configure CDN caching for yourdomain.com to serve hashed static assets with a one-year immutable TTL, bypass caching for /api/*, and set up automated cache purges on deploy.

Frequently Asked Questions about cdn-caching-specialist

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

FAQPage Schema
How do I configure Cloudflare cache-control headers for static assets?▼

Configure Cloudflare cache-control headers by setting long TTLs for hashed static assets and short revalidation TTLs for HTML or API routes. This ensures immutable files are served from the edge while dynamic content remains fresh.

What is the best way to automate CDN cache invalidation during deployments?▼

Automate CDN cache invalidation by implementing asset content hashing and triggering purges via CDN APIs or invalidation hooks during your deployment scripts. This safely updates cached files without manually clearing the cache.

Why are users seeing outdated content after a web application deploy?▼

Users see outdated content when cache invalidation fails to purge old assets. Resolve this by verifying CDN dashboard signals, establishing safe purge policies, and ensuring deployment scripts properly trigger API invalidations.

How do I set up CloudFront cache rules for different file types?▼

Set up CloudFront cache rules by defining Cache-Control policies based on file type, applying immutable one-year TTLs for versioned assets, and bypassing cache for API endpoints to optimize asset delivery.

Can I use this CDN caching approach for reverse proxies and static sites?▼

Yes, this CDN caching approach applies to configuring reverse proxies and static sites. You can modify origin server headers, monitor cache hit ratios, and enable delivery optimizations like compression and lazy loading.

What are the limitations of manual cache purges for web applications?▼

Manual cache purges risk serving stale content and high bandwidth usage during deployments due to human error. Implementing automated purge policies and content hashing mitigates these cache invalidation failures.