launching-ec2-instance-with-best-practices

Launches an EC2 instance with secure, cost-efficient defaults including AMI selection, burstable instance sizing, least-privilege IAM roles, hardened security groups, encrypted EBS volumes, and comprehensive tagging. Use when deploying new EC2 instances following AWS best practices for security and cost optimization.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/ec2-skills/launching-ec2-instance-with-best-practices/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is well-structured with excellent progressive disclosure and good conciseness, but the core launch procedure is delegated to a reference without inline executable steps or validation checkpoints, weakening actionability and workflow clarity in-body.

Suggestions

Add a brief inline launch sequence with one or two key commands and an explicit post-launch validation checkpoint (e.g. verifying instance state with `aws ec2 describe-instances`) so the body is actionable without requiring the reference.

De-duplicate the Overview and the 'procedure handles' bullet list so the same capabilities are not enumerated twice.

Surface at least one explicit validate-then-proceed feedback loop in the launch section to satisfy the validation requirement for infra/batch operations.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the Overview and the 'procedure handles' bullet list overlap (both enumerate AMI, IAM, security groups, storage, tagging), which is minor redundancy that could be tightened.	4 / 5
Actionability	Troubleshooting gives executable commands (`aws ec2 get-console-output`, key permissions `400`), but the primary launch task is only a pointer to the reference file with no inline executable steps, leaving the core action incomplete in-body.	3 / 5
Workflow Clarity	The launch workflow is delegated to the reference without inline sequenced steps or explicit validation checkpoints in the body; because launching EC2 is an infra/batch operation, the missing in-body validation cap applies despite troubleshooting covering some error recovery.	3 / 5
Progressive Disclosure	A clear overview points to a single, well-signaled one-level-deep reference (references/launch-ec2-instance-with-best-practices.md, which exists) while keeping short troubleshooting inline, making navigation easy.	5 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capabilities and trigger conditions with concrete, specific actions. It is concise yet comprehensive, with only minor room for additional natural synonyms.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'AMI selection, burstable instance sizing, least-privilege IAM roles, hardened security groups, encrypted EBS volumes, and comprehensive tagging' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	It explicitly answers both 'what' (launches an EC2 instance with the listed secure/cost-efficient defaults) and 'when' ('Use when deploying new EC2 instances following AWS best practices for security and cost optimization') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural terms like 'EC2 instance', 'deploying new EC2 instances', and 'AWS best practices' match what a user would say, but a few common synonyms (e.g. 'provision', 'virtual machine') are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to launching EC2 instances with best-practice security and cost defaults, with distinct triggers that minimize overlap with other AWS skills.	5 / 5
	Total	19 / 20 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: skills/specialized-skills/ec2-skills/launching-ec2-instance-with-best-practices/SKILL.md
Commit: 8ea26bd

Reviewed: 1 day 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.