Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Configure, optimize, and troubleshoot CDN deployments with caching strategies, security hardening, and multi-provider management.
Configure, optimize, and troubleshoot CDN deployments with caching strategies, security hardening, and multi-provider management.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User wants to set up, optimize, or debug a CDN. Covers provider selection, caching, security, and performance monitoring.
TopicFileProvider comparison & CLIsproviders.mdSecurity hardeningsecurity.mdCaching strategiescaching.mdTroubleshootingtroubleshooting.md
Provider selection โ Compare Cloudflare, CloudFront, Bunny, Fastly based on use case, traffic, budget Cache configuration โ Set optimal cache-control headers, TTLs, cache keys Security setup โ SSL/TLS, WAF rules, DDoS protection, origin shielding Performance monitoring โ Cache hit ratios, TTFB, regional latency Invalidation โ Purge strategies, CI/CD integration, tagged invalidation Cost optimization โ Bandwidth analysis, tier recommendations, multi-CDN strategies Troubleshooting โ Debug cache misses, stale content, origin overload
Before deploying, verify: Hashed assets (JS/CSS) โ Cache-Control: public, max-age=31536000, immutable HTML pages โ Short TTL or no-cache with revalidation Images โ Long TTL with content-based URLs or versioning API responses โ Usually no-store unless explicitly cacheable User-specific content โ private or no-store
TLS 1.2+ enforced, weak ciphers disabled HSTS enabled with appropriate max-age Origin IPs hidden, authenticated origin pulls configured Rate limiting on sensitive endpoints (login, API) Security headers: CSP, X-Frame-Options, X-Content-Type-Options
Caching user-specific responses (auth tokens, personalized content) Using max-age without immutable for versioned assets Purging entire cache instead of targeted paths Ignoring Vary headers (cache poisoning risk) Origin not rejecting direct access (bypassing CDN protections)
Ask about: Geographic distribution of users Current page load times and Core Web Vitals Static vs dynamic content ratio Traffic volume and patterns If users are mostly local and traffic is low โ CDN may add complexity without benefit. If global users OR heavy static assets OR need DDoS protection โ CDN adds value.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.