architecture
Use when navigating the codebase for the first time, adding a new client method, adding a new container handler/service, or understanding how a request flows from Worker through the Sandbox DO into the container. Covers the three-layer architecture, client pattern, container runtime structure, and monorepo layout. (project)
96
—
Does it follow best practices?
Impact
95%
1.97xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
97%
57%Disk Usage Monitoring Feature
New container control operation design
Service in services/
0%
100%
Container control-plane method
10%
100%
SDK container-control mirror
10%
100%
Unit tests both sides
62%
100%
E2E test for shell behavior
25%
100%
Shared error classes
80%
100%
No route handler for new capability
100%
100%
Control path explanation
40%
100%
Correct sequence order
50%
75%
Architecture layer awareness
25%
100%
100%
70%Network Interface Listing via HTTP Compatibility API
Route-based compatibility client scaffolding
Extends BaseHttpClient
0%
100%
Correct SDK client path
0%
100%
SandboxClient aggregator
25%
100%
Container handler in handlers/
0%
100%
No new control-plane capability
0%
100%
HTTP call implementation
60%
100%
TypeScript types
100%
100%
Compatibility rationale
75%
100%
90%
16%Adding Ruby Support to the Sandbox Container Image
Lean Dockerfile modification with version pinning
Correct Dockerfile path
0%
100%
Ruby version pinned
100%
100%
Bundler pinned
0%
0%
Cache cleanup present
100%
100%
Single RUN layer
66%
100%
Lean image rationale
100%
100%
Version pin rationale
100%
100%
No unnecessary packages
100%
100%
- Repository
- cloudflare/sandbox-sdk
- Commit
ebb7be9
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.