launch-with-aws

Migrates vibe-coded web applications to AWS. Handles the full workflow from analysis through migration to deployment, producing deployable AWS Blocks infrastructure code. Supports full-stack apps built with vibe-coding platforms (Lovable, Bolt.new, Replit) and frontend web applications and websites: React, Vue, Angular, Next.js, Nuxt, Astro, SvelteKit, Gatsby, Vite, Svelte, Solid, Docusaurus, and others (static sites, SPAs, and SSR frameworks with static export). Triggers on: launch with AWS, launch on AWS, deploy to AWS, migrate to AWS, host my app on AWS, move my app to AWS, transfer my app to AWS. Activates when the user wants to migrate a vibe-coded app or frontend web app to AWS, even if they don't say 'migrate' explicitly.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%

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

The content is a well-structured, executable runbook: concrete commands, explicit validation gates, and clean one-level-deep references to the bundled scripts and service model. It respects Claude's competence and externalizes detail appropriately, scoring at the top of every dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean for a 9-step migration workflow: it never explains concepts Claude already knows (no "what is S3/CloudFront") and every section — commands, status progression, confirmation gates, migration tables — earns its place. Minor redundancy between the frontmatter framework list and the body's support tables does not rise to padding.	3 / 3
Actionability	Fully executable guidance throughout: exact `python3 scripts/launch_with_aws.py <command>` invocations, documented JSON response shapes, plus copy-paste-ready curl/git/rsync commands for the post-migration merge — no pseudocode.	3 / 3
Workflow Clarity	Steps are explicitly numbered 1–9 with validation checkpoints: two confirmation gates ("Do NOT call create-launch... until the user explicitly confirms", same for start-launch-execution), poll-until-status guidance with a 30s sleep, a dirty-working-tree check before merge, and conflict-handling instructions for risky/batch operations.	3 / 3
Progressive Disclosure	SKILL.md is an orchestration overview that links to the real bundle — required scripts via markdown links and the one-level-deep service model at references/launchwithaws-2026-06-15.json (verified present) — keeping implementation detail externalized and navigation clear.	3 / 3
	Total	12 / 12 Passed

Description

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.

The description is third-person, concrete, and explicitly states both capabilities and activation triggers, hitting the top anchor on every dimension. Its only weakness is verbosity: the long framework enumeration could be trimmed without losing specificity, but no dimension is penalized for it since the rubric rewards concrete detail over padded fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Migrates vibe-coded web applications to AWS", "Handles the full workflow from analysis through migration to deployment, producing deployable AWS Blocks infrastructure code" — plus a specific enumeration of supported platforms and frameworks, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers both what (migrate/analyze/deploy vibe-coded and frontend web apps to AWS, producing Blocks infra code) and when via an explicit "Triggers on:" clause plus "Activates when the user wants to migrate...", satisfying the explicit-trigger requirement for a 3.	3 / 3
Trigger Term Quality	Explicit "Triggers on:" list gives natural phrases a user would say ("launch with AWS", "deploy to AWS", "host my app on AWS", "move my app to AWS"), with good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and clearly scoped — migrating vibe-coded/web apps to AWS via AWS Blocks — with distinct trigger phrases unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: plugins/aws-core/skills/launch-with-aws/SKILL.md
Commit: 222ce56

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.