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
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It uses third person voice, specifies concrete migration paths with named platforms, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche that won't conflict with general deployment or serverless skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js' and mentions specific tasks like 'porting existing applications', 'adapting serverless functions', and 'resolving Node.js API compatibility issues'. | 3 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Cloudflare Workers', 'AWS Lambda', 'Vercel', 'Express', 'Node.js', 'edge', 'serverless functions', 'porting', 'migrate'. These are all terms developers naturally use when discussing migration tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Cloudflare Workers migration from named platforms. The combination of source platforms (AWS Lambda, Vercel, Express, Node.js) and target (Cloudflare Workers) creates distinct triggers unlikely to conflict with general serverless or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality migration skill that efficiently covers multiple source platforms with concrete code examples and clear navigation. The decision tree and error tables are particularly effective for quick reference. The main weakness is the migration checklist lacks explicit validation/verification steps between stages, which is important for potentially breaking migration operations.
Suggestions
Add validation checkpoints to the migration checklist (e.g., 'After step 3, verify imports resolve with wrangler dev before proceeding')
Include a rollback or verification step after 'Test Locally' to confirm functionality matches the original before deployment
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens with decision trees, tables, and code examples. No unnecessary explanations of concepts Claude already knows - jumps straight to actionable migration patterns. | 3 / 3 |
Actionability | Provides fully executable before/after code examples for Lambda, Express, and environment variables. The error table gives specific solutions, and the migration checklist provides concrete steps. | 3 / 3 |
Workflow Clarity | The migration checklist provides a clear sequence, but lacks explicit validation checkpoints or feedback loops. For migrations involving potential breaking changes, there should be verify/rollback steps between stages. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, decision tree for navigation, and well-signaled one-level-deep references to platform-specific migration guides. The 'When to Load References' table clearly directs to detailed materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- Reviewed
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.