Agent skill · DevOps & Cloud

migration-readiness

Assess a workload's readiness to migrate to AWS by analyzing existing code, dependencies, configurations, and infrastructure to produce evidence-backed findings covering the 7 Rs, risks, and a migration plan.

AWS Samples169★ · 1 repos on radarProfile →
claude-codeclinecodexcursorcopilotwindsurfMIT-0
Install
npx skills add aws-samples/sample-well-architected-skills-and-steering --skill migration-readiness --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Version: 2.0.0
Path: skills/migration-readiness/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 233
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Migration Readiness Assessment ## Step 1: Gather context Ask the user: > What workload are you planning to migrate? Please share: > - **Workload name** and code packages/directories to analyze > - **Current environment** (on-premises, other cloud, colocation) > - **Business drivers** (cost, agility, compliance, end-of-life hardware, etc.) > - **Timeline constraints** (optional) If context is already provided or you are in a codebase, proceed directly. ## Step 2: Application Stack Discovery Analyze the codebase to understand the current application stack. You MUST examine: - Programming languages and runtimes (versions, compatibility with AWS services) - Frameworks and libraries (web frameworks, ORM, messaging) - Database technologies (relational, NoSQL, search, caching) - Middleware and message brokers - External service dependencies (APIs, SaaS integrations) - Configuration management (config files, environment variables, secrets) - Operating system dependencies and system-level requirements - Build and packaging systems (Maven, npm, pip, Docker) For each component, document: - File path and line numbers - Technology and version - AWS equivalent or migration path - Migration com

What's inside
Steps it walks through
  1. Step 1: Gather context
  2. Step 2: Application Stack Discovery
  3. Step 3: Infrastructure Discovery
  4. Step 4: Dependency Mapping
  5. Step 5: Determine migration strategy (7 Rs)
  6. Step 6: Assess readiness by pillar
  7. Operational Excellence Readiness
  8. Security Readiness
  9. Reliability Readiness
  10. Performance Efficiency Readiness
  11. Cost Optimization Readiness
  12. Sustainability Readiness
  13. Step 7: Risk Assessment
  14. Step 8: Produce the assessment
Ships with 3 files
  • evals/evals.json
  • evals/triggering.json
  • metadata.json
More from sample-well-architected-skills-and-steering
All skills →
About this skill
What does the migration-readiness skill do?

Assess a workload's readiness to migrate to AWS by analyzing existing code, dependencies, configurations, and infrastructure to produce evidence-backed findings covering the 7 Rs, risks, and a migration plan.

How do I install it?

Run `npx skills add aws-samples/sample-well-architected-skills-and-steering --skill migration-readiness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aws-samples/sample-well-architected-skills-and-steering, a repository with 233 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going