Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/content-delivery

@228d57d
Run it yourself

This skill should be used when the user asks about a "CDN", "edge caching", "static asset delivery", "media / video delivery", "geo distribution of content" or "edge POP selection", "push vs pull CDN", "cache-control headers" / "TTL for static assets", "origin offload", or "origin shield". It gives the recipe for serving bytes from the edge close to users. Use it whenever a design serves images, video, JS/CSS, or downloads to a wide geography, or the origin is saturated by repeat reads of the same files, even if the user doesn't say "CDN".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/content-delivery

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersgcp.md

≈463 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content delivery — GCP

Service mapping

  • Cloud CDN — the general CDN; caches at Google's edge in front of an external HTTPS load balancer (the LB is the front door), pulling from a backend bucket or backend service. Use for static/media and cacheable dynamic responses.
  • Media CDN — a separate product tuned for large-scale video/media delivery (built on YouTube's edge); choose it over Cloud CDN when streaming volume, segmented HLS/DASH, or huge file egress dominates.
  • Cloud Storage (GCS) — the usual static/media origin (backend bucket).
  • Cloud Load Balancing — Cloud CDN is enabled on the external HTTPS LB; global anycast routing comes from the LB (→ load-balancing).

When to pick which

Cloud CDN for web static assets and general caching tied to your HTTPS LB; Media CDN when the workload is video/large-file streaming at scale; GCS backend bucket as the simplest static origin.

Limits / things that bite (verify against current docs)

  • Cloud CDN requires (and is configured through) an external HTTPS load balancer — you don't point it at a raw origin; the LB defines backends.
  • Cache mode matters: CACHE_ALL_STATIC vs USE_ORIGIN_HEADERS vs FORCE_CACHE_ALL change what gets cached — pick deliberately.
  • Cache-key policy (include/exclude query strings, host, protocol) drives hit rate; default may over- or under-cache.
  • Invalidation propagation is not instant; prefer versioned URLs. Egress is the dominant cost and varies by region/tier.

Pitfalls

  • Expecting Cloud CDN without setting up the HTTPS LB + backend bucket/service.
  • Using Cloud CDN for heavy video when Media CDN is the fit (or vice versa).
  • Wrong cache mode → caching nothing, or caching personalized responses.
  • Lock-in via LB + CDN config and Media CDN-specific features.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill is a comprehensive architectural guide for designing Content Delivery Networks (CDNs). It consists solely of technical documentation and does not contain any executable code, external scripts, or malicious patterns.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/content-delivery