workers-migration
Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.
94
93%
Does it follow best practices?
Impact
97%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
98%
33%Migrate Express REST API to Cloudflare Workers
Express to Hono migration with auth
Hono framework
100%
100%
No express import
100%
100%
ESM imports
100%
100%
env parameter for vars
100%
100%
Zod validation
0%
100%
jose for JWT
0%
77%
bcryptjs not bcrypt
0%
100%
Drizzle not Prisma
100%
100%
D1 database binding
100%
100%
nodejs_compat_v2 flag
0%
100%
Async request body
100%
100%
Hono response methods
100%
100%
94%
17%Migrate AWS Lambda Backend to Cloudflare Workers
Lambda to Workers migration
Workers fetch handler
100%
100%
Response object format
100%
100%
env for environment vars
100%
100%
D1 instead of DynamoDB
0%
100%
R2 instead of S3
100%
100%
Lambda adapter pattern
100%
100%
ctx.waitUntil for notifications
30%
40%
No AWS SDK imports
100%
100%
ESM imports
100%
100%
wrangler bindings
50%
100%
crypto.randomUUID for IDs
100%
100%
Migration notes
57%
100%
100%
10%Port a Node.js Data Processing Utility to Cloudflare Workers
Node.js compatibility analysis and migration
Analysis script run
100%
100%
nodejs_compat_v2 flag
0%
100%
node: prefix on imports
100%
100%
No fs module
100%
100%
KV for config storage
100%
100%
fetch instead of https
100%
100%
No http/https imports
100%
100%
env for API keys
100%
100%
ESM syntax
100%
100%
KV binding in wrangler
100%
100%
No require()
100%
100%
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.