Agents Week was not a product launch. It was a confirmation. The four pillars skill builders have been quietly betting on for a year just got their own infrastructure category.
Cloudflare dropped Agents Week and the subtext was loud: agents need their own stack, not a retrofit of yesterday's cloud. Read past the product list and you can see the same four pillars showing up in every serious skill repo right now: security and MCP, agent memory, sandboxes, and artifacts. Today's issue maps each pillar to a concrete move you can make in your own skill files.
The four pillars Cloudflare just made official
Strip the marketing off Agents Week and the announcements cluster into four buckets: security and MCP (Mesh, Managed OAuth, non-human identity, the Enterprise MCP reference architecture), agent memory (the new managed Agent Memory service), sandboxes (Sandboxes GA plus Outbound Workers as a zero-trust egress proxy), and artifacts (git-compatible versioned storage for agent-generated code).
If those four words sound familiar, it is because the best SKILL.md files in the wild have been quietly organizing around the same shape. Cloudflare did not invent the stack. They named it and put a price on it.
Why this matters for skill builders, not just platform teams
When a hyperscaler ships a category, the half-life of every hand-rolled workaround drops fast. The skill files that age well from here are the ones that already separate the four pillars cleanly, so they can swap in a managed primitive when the math gets cheap enough.
The skill files that age badly are the ones with a static token in the YAML, a memory section that just means 'put it in the prompt', and a code-execution step that runs on the operator's laptop. Those still work today. They will look prehistoric in two quarters.
A GitHub-flavored skill block aligned to the four pillars
---
name: agent-stack-aligner
version: 0.1.0
description: Align a skill file to the agent-infra stack: security/MCP, memory, sandboxes, artifacts
---
# Agent Stack Aligner
Use this when a skill needs to plug into the modern agent infrastructure pattern (Cloudflare Agents Week-shaped).
## Pillars to satisfy
- security_mcp: scoped tokens, MCP gateway, no static service accounts
- memory: durable recall + selective forgetting, written outside the prompt window
- sandbox: untrusted/agent-generated code runs in an isolated env with egress proxy
- artifacts: every meaningful output is versioned (git-shaped) not just chat-logged
## Workflow
1. Inventory the skill: which pillars does it currently touch?
2. For each missing pillar, add the smallest reliable hook:
- security_mcp -> swap any long-lived key for a scoped, scannable token
- memory -> write durable notes to memory/YYYY-MM-DD.md before exit
- sandbox -> route code execution through a sandbox tool, not the host shell
- artifacts -> save outputs to a versioned path, return the path not the blob
3. Record drift: if a pillar is intentionally skipped, write WHY in the skill file
## Guardrails
- Never ship a skill with a static admin token
- Never let agent-generated code touch the host shell directly
- Never treat chat history as memory
- Never return an artifact inline when a versioned path will do
The pattern to copy this week
Pick one skill you actually run weekly. Walk it through the four pillars and write down which ones it satisfies and which it fakes. The fakes are your roadmap.
Most builders find the same gap on the first pass: memory is implicit and artifacts are ephemeral. Fixing just those two, with a memory/ write before exit and a versioned output path, gets a skill to roughly the shape Cloudflare is now selling as a managed product.
What to do today
Open your most-used skill, run it through the block above, and commit the version that names its missing pillars in plain text. You do not need to fix all four today. You need to stop pretending the gaps are not there.
Then read the source for yourself: https://blog.cloudflare.com/agents-week-in-review/. Look at it less as a Cloudflare release and more as a checklist for what serious agent infrastructure looks like in 2026. The skill files that match this shape are the ones that will still be running a year from now.
Agents Week was the moment the agent stack stopped being a vibe and started being a category. The skill builders who were already aligned to security/MCP, memory, sandboxes, and artifacts did not get disrupted today. They got validated. The rest of the field just got a very clear map of where to ship next.