Individual skill
aws-transform
Migrate, modernize, and upgrade codebases to AWS. Run analysis on repos for tech debt, security vulnerabilities, and modernization opportunities. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. Use when the user says "migrate .NET to AWS", "upgrade Java to 17/21", "modernize COBOL", "modernize mainframe", "move VMware to EC2", "convert SQL Server to Aurora", "upgrade Python version", "migrate AWS SDK", "transform this codebase", "analyze for issues", "find tech debt", "what tech debt", "security vulnerabilities", "CVEs", "what's wrong with my code", "assess my repos", "where do I start", "find what's outdated", "analyze my repos", "AWS Transform - continuous modernization", "continuous modernization" or "continuous-modernization". Don't use for infrastructure provisioning, CI/CD pipelines, or general coding tasks.
plugins/aws-transform/skills/aws-transform/SKILL.md
Source commit fbefb3764e67558fe10ac834dd85db49734aa9b6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 937
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agents Repository topic
- coding-agent-skills Repository topic
- coding-agents Repository topic
- agent-plugins Repository topic
- aws Repository topic
- devops Derived category
- engineering Derived category
- data Derived category
- security Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesSKILL.mdcore · 36,268 bytesreferences/AWSTransformInfrastructureExecutorAccessEC2.jsonasset · 5,796 bytesreferences/AWSTransformSecurityAgentExecutorAccess.jsonasset · 1,829 bytesreferences/auth.mddoc · 4,120 bytesreferences/continuous-modernization-analysis.mddoc · 21,394 bytesreferences/continuous-modernization-aws-managed-execution.mddoc · 10,046 bytesreferences/continuous-modernization-batch-execution.mddoc · 11,383 bytesreferences/continuous-modernization-discovery.mddoc · 2,662 bytesreferences/continuous-modernization-ec2-execution.mddoc · 13,375 bytesreferences/continuous-modernization-findings.mddoc · 7,882 bytesreferences/continuous-modernization-guide.mddoc · 16,808 bytesreferences/continuous-modernization-remediation.mddoc · 15,162 bytesreferences/continuous-modernization-reporting.mddoc · 18,177 bytesreferences/continuous-modernization-schedule.mddoc · 22,071 bytesreferences/continuous-modernization-security-agent.mddoc · 8,715 bytesreferences/continuous-modernization-setup.mddoc · 5,030 bytesreferences/continuous-modernization-source.mddoc · 12,775 bytesreferences/continuous-modernization-status.mddoc · 1,999 bytesreferences/continuous-modernization-troubleshooting.mddoc · 10,518 bytesreferences/continuous-modernization.mddoc · 15,669 bytesreferences/custom-cli-reference.mddoc · 9,609 bytesreferences/custom-multi-transformation.mddoc · 10,593 bytesreferences/custom-remote-execution.mddoc · 23,941 bytesreferences/custom-repo-analysis.mddoc · 7,443 bytesreferences/custom-results-synthesis.mddoc · 1,610 bytesreferences/custom-single-transformation.mddoc · 15,701 bytesreferences/custom-troubleshooting.mddoc · 9,379 bytesreferences/custom.mddoc · 38,009 bytesreferences/dotnet-bulk.mddoc · 17,510 bytesreferences/dotnet.mddoc · 38,590 bytesreferences/mainframe-reimagine-analysis.mddoc · 23,278 bytesreferences/mainframe-reimagine-ddd.mddoc · 13,493 bytesreferences/mainframe-reimagine-modern-traceability.mddoc · 19,878 bytesreferences/mainframe-reimagine-specgen.mddoc · 21,941 bytesreferences/mainframe-reimagine-verify.mddoc · 9,937 bytesreferences/mainframe-reimagine.mddoc · 13,114 bytesreferences/mainframe.mddoc · 11,505 bytesreferences/sql.mddoc · 50,442 bytesreferences/tools.mddoc · 11,058 bytesreferences/vmware-containerization.mddoc · 7,027 bytesreferences/vmware-landing-zone.mddoc · 8,287 bytesreferences/vmware-network.mddoc · 32,250 bytesreferences/vmware-server.mddoc · 9,122 bytesreferences/vmware.mddoc · 14,843 bytesreferences/workflow.mddoc · 27,128 bytesscripts/verify-traceability.pyruns · 26,639 bytes
Read excerpt
# AWS Transform
## CRITICAL: Route Before Anything Else
**STOP. Before reading files, analyzing code, or starting any workflow, identify the workload first, then route.**
### Step A: Identify the workload
Look for an explicit workload signal in the user's request — a named technology (`.NET`, `VMware`, `SQL Server`/`Aurora`/`Oracle`/`MySQL`, `mainframe`/`COBOL`), workload-specific terminology (Hyper-V, EC2 rehost, stored procs, CICS, JCL), or file/project signals already in the conversation. If no signal is present, treat the request as **workload-unspecified**.
### Step B: Apply workload-specific routing
Workload-specific rules ALWAYS win over the keyword list in Step C. Do not let "analysis" or "tech debt" phrasing override these.
