Containers
Decide when to use Cloudflare Containers instead of Workers and design container-backed workloads, native binaries, long-running processes, image processing, larger runtime shapes, and Worker frontends. Use as an escape hatch when Workers constraints do not fit.
Install
npx skills add zllovesuki/cloudflare-agent-skills --skill containersgit clone --depth 1 https://github.com/zllovesuki/cloudflare-agent-skills.git /tmp/cloudflare-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/cloudflare-agent-skills/skills/containers ~/.claude/skills/containersPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Containers Use this skill when evaluating or implementing Cloudflare Containers. Containers are an escape hatch for workloads that do not fit the Worker runtime shape. ## Use Containers when - The code requires native binaries or a runtime that cannot reasonably run in Workers. - The workload needs a process model unavailable in Workers. - The task is CPU/memory/runtime-shape heavy and cannot be solved by streaming, chunking, R2, Queues, or Workflows. - You are bringing an existing service to Cloudflare while incrementally refactoring. ## Prefer Workers when - The workload is HTTP request/response logic. - It mostly orchestrates I/O through bindings. - It can be implemented with Web APIs and small compute slices. - The primary need is global low-latency routing, not a persistent process. ## Design pattern Put a Worker at the edge as the public interface and use Containers only for the specialized work. ```text Client -> Worker: auth, validation, routing, rate limiting -> Queue/Workflow: durable background orchestration when needed -> Container: native/heavy execution -> R2/D1: results and metadata ``` ## Implementation guidance - Make the container API narrow and explicit. - Store inputs/outputs in R2 for large artifacts; pass keys, not blobs. - Add idempotency keys for long-running work. - Use Queues or Workflows for durable scheduling and retries. - Keep authentication and tenant authorization in the Worker boundary.
Details
- Skill name
containers- Repository
- zllovesuki/cloudflare-agent-skills
- Path
skills/containers/SKILL.md- Repo updated
- 28 April 2026
FAQ
What does the Containers skill do?
Decide when to use Cloudflare Containers instead of Workers and design container-backed workloads, native binaries, long-running processes, image processing, larger runtime shapes, and Worker frontends. Use as an escape hatch when Workers constraints do not fit.
How do I install the Containers skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add zllovesuki/cloudflare-agent-skills --skill containers. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Containers popular?
It lives in zllovesuki/cloudflare-agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Agents
9zllovesuki/cloudflare-agent-skills
Build Cloudflare Agents SDK applications for autonomous multi-step tool use, AIChatAgent chat agents, Durable Object-backed state, tools, scheduling, callable methods, WebSockets, SQL state, and constrained agent behavior. Use when RAG or Workflows are not enough.
Cloudflare Architecture
9zllovesuki/cloudflare-agent-skills
Choose Cloudflare Developer Platform primitives and architecture shapes before writing code. Use for Cloudflare Workers, Durable Objects, D1, R2, Queues, Workflows, Containers, Realtime, Workers AI, Vectorize, AI Search, Agents, cost, limits, and migration decisions.
Cost Optimization
9zllovesuki/cloudflare-agent-skills
Optimize Cloudflare Developer Platform costs for Workers CPU vs wall time, D1 operations, KV reads/writes, R2 storage/egress, Durable Object hotspots, Queues, Workflows, Workers AI tokens, and architecture-level trade-offs. Use during design and production reviews.
Full Stack Apps
9zllovesuki/cloudflare-agent-skills
Build full-stack Cloudflare apps with Workers, static assets, SSR, API routes, SPA/hybrid rendering, cache headers, and binding-backed data. Use when implementing frontend-plus-backend applications on Cloudflare Workers.
Appdeploy
3AppDeploy-AI/skills
Deploy web apps with backend APIs, database, file storage, AI operations, authentication, realtime, and cron jobs to a public URL. Use when the user asks to deploy, publish, or host a website or web app. No account required. Uses HTTP API via curl.
Migration
9zllovesuki/cloudflare-agent-skills
Plan incremental migrations to Cloudflare from AWS, Azure, GCP, server-based apps, or existing databases using strangler patterns, service boundaries, R2 offload, Workers frontdoors, Hyperdrive, queues, workflows, shadow reads, rollback, and observability.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.