cloudflare-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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and well-structured with real one-level-deep references and copy-paste before/after patterns. Its main gap is the migration checklist lacks an explicit validation feedback loop for destructive cutover operations.

Suggestions

Add an explicit feedback loop to the Migration Checklist: after 'Test Locally', state 'If tests fail → fix the issue → re-run wrangler dev until passing' before proceeding to deployment.

Insert a pre-cutover validation checkpoint (e.g., 'Verify parity: confirm all endpoints respond correctly in wrangler dev before deploying to production') to guard the destructive migration step.

Add a brief verification step confirming the deployed Worker matches expected behavior post-cutover, so the workflow closes the loop on the risky operation.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense: tables for comparison/errors, before/after code pairs with no padding, and no explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides fully executable before/after TypeScript, a concrete wrangler.jsonc config with exact compatibility flags, and specific error-to-solution mappings that are copy-paste ready for the common migration cases.	5 / 5
Workflow Clarity	A numbered 7-step checklist and a decision tree provide a clear sequence with verification steps ('Test Locally', 'Performance Test'), but there is no explicit validate-then-fix-then-retry feedback loop or pre-cutover validation checkpoint for what is effectively a batch/destructive migration.	3 / 5
Progressive Disclosure	The body is a concise overview pointing to four real one-level-deep reference files via a 'When to Load References' table, plus a script, all of which exist in the bundle; navigation is easy and content is appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, concise, and clearly answers both what the skill does and when to use it, with named source platforms and natural trigger phrases. Its only weakness is that the trigger clause omits the specific platform names that appear in the capability clause.

Dimension	Reasoning	Score
Specificity	Names the Cloudflare Workers migration domain and enumerates four concrete source platforms (AWS Lambda, Vercel, Express, Node.js) with multiple action verbs, but the actions are variations of a single migrate theme rather than a fully comprehensive multi-action list.	4 / 5
Completeness	Explicitly answers both what ('Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js') and when ('Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause includes natural phrases users would say ('porting existing applications to the edge', 'adapting serverless functions', 'Node.js API compatibility'), but the specific source-platform names appear only in the 'what' clause rather than the trigger.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Cloudflare Workers migration) with named source platforms and distinct triggers, making it unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/cloudflare-workers/skills/cloudflare-workers-migration/SKILL.md
Commit: 84802a4

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.