← Back to Skills Marketplace
839
Downloads
2
Stars
4
Active Installs
2
Versions
Install in OpenClaw
/install cdn
Description
Configure, optimize, and troubleshoot CDN deployments with caching strategies, security hardening, and multi-provider management.
README (SKILL.md)
When to Use
User wants to set up, optimize, or debug a CDN. Covers provider selection, caching, security, and performance monitoring.
Quick Reference
| Topic | File |
|---|---|
| Provider comparison & CLIs | providers.md |
| Security hardening | security.md |
| Caching strategies | caching.md |
| Troubleshooting | troubleshooting.md |
Core Capabilities
- 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
Cache-Control Checklist
Before deploying, verify:
- Hashed assets (JS/CSS) →
Cache-Control: public, max-age=31536000, immutable - HTML pages → Short TTL or
no-cachewith revalidation - Images → Long TTL with content-based URLs or versioning
- API responses → Usually
no-storeunless explicitly cacheable - User-specific content →
privateorno-store
Security Checklist
- 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
Common Mistakes
- Caching user-specific responses (auth tokens, personalized content)
- Using
max-agewithoutimmutablefor versioned assets - Purging entire cache instead of targeted paths
- Ignoring
Varyheaders (cache poisoning risk) - Origin not rejecting direct access (bypassing CDN protections)
Decision: Do I Need a CDN?
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.
Usage Guidance
This skill is a coherent, text-only CDN playbook — it won't install code or request secrets by itself. Before using it: (1) don't paste API keys or secret tokens into public chats; the docs include example env vars (e.g., $CF_TOKEN, $BUNNY_API_KEY) that you must keep private and provide only to trusted tooling. (2) Many examples assume CLIs (curl, aws, fastly) and privileged actions (iptables); run those commands yourself on the appropriate host rather than letting an agent execute them autonomously. (3) The skill's firewall/iptables examples and origin-protection steps can block traffic if applied incorrectly — validate commands in a safe environment. If you plan to let an agent act with your provider credentials, limit its scope (least privilege) and audit any API calls.
Capability Analysis
Type: OpenClaw Skill
Name: cdn
Version: 1.0.1
The skill bundle provides comprehensive documentation and examples for CDN management, including `curl` commands interacting with CDN APIs using environment variables (e.g., `$CF_TOKEN`, `$BUNNY_API_KEY`) and `iptables` commands for firewall configuration in `providers.md` and `security.md`. While these commands are legitimate for system administration and security hardening, their direct execution by an AI agent without robust input validation, sandboxing, or explicit user confirmation presents a significant vulnerability risk. Specifically, `iptables` can cause denial of service or unintended network changes, and API calls with credentials could be misused if the agent's secret handling is insecure. There is no evidence of intentional malicious behavior, but the presence of these high-risk capabilities warrants a 'suspicious' classification due to potential for exploitation if the agent's execution environment is not adequately secured.
Capability Assessment
Purpose & Capability
The name/description align with the files (caching, providers, security, troubleshooting). Minor inconsistency: the registry metadata lists no required binaries or env vars, yet the docs include examples using provider CLIs and env vars (e.g., $CF_TOKEN, $BUNNY_API_KEY, aws CLI). This is expected for a CDN guide, but the skill does not declare those prerequisites.
Instruction Scope
SKILL.md and associated files stay within CDN setup, optimization, and debugging. They include executable examples (curl, aws CLI, iptables, openssl) and show how to use API tokens and secret headers. The docs do not instruct wide-ranging data collection or exfiltration, but several examples assume the agent or user will run privileged commands (iptables) or use API keys — actions that have side effects and require care.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is written to disk or downloaded by the skill itself, which is the lowest-risk install profile.
Credentials
The skill declares no required credentials, which is proportional. However example snippets reference provider tokens and CLI usage ($CF_TOKEN, $BUNNY_API_KEY, aws CLI). This is appropriate for real-world CDN tasks but means the user/agent will need to supply credentials externally if they follow those examples — the skill itself does not request or store them.
Persistence & Privilege
always is false and the skill is user-invocable. As an instruction-only skill it does not request persistent presence or modify other skills or global agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install cdn - After installation, invoke the skill by name or use
/cdn - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Add providers, security, caching, troubleshooting guides
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is CDN?
Configure, optimize, and troubleshoot CDN deployments with caching strategies, security hardening, and multi-provider management. It is an AI Agent Skill for Claude Code / OpenClaw, with 839 downloads so far.
How do I install CDN?
Run "/install cdn" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is CDN free?
Yes, CDN is completely free (open-source). You can download, install and use it at no cost.
Which platforms does CDN support?
CDN is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created CDN?
It is built and maintained by Iván (@ivangdavila); the current version is v1.0.1.
More Skills