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.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 strong skill description that clearly identifies the specific migration targets (Cloudflare Workers) and sources (AWS Lambda, Vercel, Express, Node.js), uses natural trigger terms, and includes an explicit 'Use when' clause with relevant scenarios. It is concise, uses third-person voice, and is highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrating from specific platforms (AWS Lambda, Vercel, Express, Node.js), porting applications to the edge, 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' (explicit 'Use when' clause covering porting existing applications, adapting serverless functions, or resolving Node.js API compatibility issues). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Cloudflare Workers', 'AWS Lambda', 'Vercel', 'Express', 'Node.js', 'edge', 'serverless functions', 'compatibility issues', and 'migrate'/'porting'. These cover the main terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Cloudflare Workers migration specifically from named platforms. The combination of 'Cloudflare Workers' + migration source platforms creates a very specific trigger profile unlikely to conflict with other 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 before/after code examples and a well-organized decision tree. The error table is particularly valuable for quick troubleshooting. The main weakness is the migration checklist lacking explicit validation checkpoints and error recovery loops, which is important for migration workflows.
Suggestions
Enhance the Migration Checklist with explicit validation checkpoints after key steps (e.g., after converting to ESM, run `wrangler dev` to verify; if errors, check the Top 10 Migration Errors table and fix before proceeding).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. No unnecessary explanations of what Lambda, Express, or Workers are. Tables and decision trees convey maximum information in minimal space. Every section earns its place. | 3 / 3 |
Actionability | Provides fully executable before/after code examples for Lambda, Express, and env variable migrations. The error table gives specific solutions. The wrangler.jsonc config is copy-paste ready. Concrete and specific throughout. | 3 / 3 |
Workflow Clarity | The migration checklist provides a clear sequence of steps, but lacks explicit validation checkpoints and feedback loops. For a migration involving potentially destructive changes, there's no 'validate -> fix -> retry' pattern — just 'Test Locally' as step 6 without guidance on what to do if tests fail. | 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 based on context. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.