cdn-engineering

Audit and optimize CDN configurations for cache efficiency, security, and egress costs.

Updated May 11, 2026
One-click install
npx skills add https://github.com/resultakak/argos --skill cdn-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdn-engineering
Source: https://github.com/resultakak/argos/tree/main/skills/cdn-engineering
Command: npx skills add https://github.com/resultakak/argos --skill cdn-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CDN configuration chaos leads to poor cache efficiency, security gaps, and escalating egress costs. This skill provides disciplined practices for cache key design, TTL strategy, origin shielding, purge workflows, private content access via signed URLs, edge image optimization, and robust multi-CDN and edge compute patterns to improve performance and reliability.

Core Features & Use Cases

  • Cache key explicit design to maximize cache hits while avoiding privacy or personalization leaks.
  • TTL and purge strategy guidance including versioned URLs and tag-based purges for eventual consistency.
  • Signed URL management, origin shield enablement, TLS termination hardening, and WAF/DDoS considerations.
  • Image optimization at edge (AVIF/WebP) and HLS/DASH edge caching strategies.
  • Multi-CDN failover planning and RUM-based routing to route traffic to the healthiest origin.
  • Edge compute patterns for at-edge logic and experiments (A/B tests), with cost and performance visibility.
  • RUM integration and cost dashboards to monitor performance and egress trends.

Quick Start

Run a CDN review on your site to identify misconfigurations and apply recommended caching, security, and failover settings.

Frequently Asked Questions about cdn-engineering

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

FAQPage Schema
How do I fix CDN cache misses and improve cache hit ratios?

Fix CDN cache misses by applying explicit cache key design and structured TTL matrices to maximize cache efficiency. This prevents personalization leaks while ensuring high cache hits across your distributed content delivery network.

What is the best way to purge CDN cache without breaking eventual consistency?

The best way to purge CDN cache safely is using versioned URLs and tag-based purges. This approach maintains eventual consistency during content updates while avoiding sudden traffic surges to your origin servers.

How do I secure private content delivery with signed URLs at the edge?

Secure private content delivery with signed URLs to enforce access controls at the edge. Combine this with TLS termination hardening and WAF/DDoS considerations to protect against unauthorized access and malicious traffic.

Does edge compute work for A/B testing and image optimization?

Edge compute supports at-edge logic for A/B tests and AVIF/WebP image optimization. This reduces origin load and minimizes egress costs while delivering optimized content directly from the CDN edge nodes.

When do I need an origin shield in my multi-CDN failover strategy?

You need an origin shield when consolidating multi-CDN failover traffic to protect your backend. RUM-based routing directs users to the healthiest origin, while the shield reduces redundant requests and controls egress costs.

Why are CDN egress costs escalating and how can I monitor them?

CDN egress costs escalate from poor cache efficiency and unoptimized image delivery. Implement RUM integration and cost dashboards to monitor performance trends, visualize egress metrics, and identify configuration gaps.