ec2
AWS EC2 virtual machine management for instances, AMIs, and networking. Use when launching instances, configuring security groups, managing key pairs, troubleshooting connectivity, or automating instance lifecycle.
88
82%
Does it follow best practices?
Impact
100%
1.21xAverage score across 3 eval scenarios
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 well-crafted skill description that follows best practices. It uses third person voice, lists specific concrete actions, includes natural trigger terms users would say, and explicitly states both what the skill does and when to use it. The AWS EC2 focus creates a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'launching instances, configuring security groups, managing key pairs, troubleshooting connectivity, automating instance lifecycle' - these are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('AWS EC2 virtual machine management for instances, AMIs, and networking') AND when ('Use when launching instances, configuring security groups, managing key pairs, troubleshooting connectivity, or automating instance lifecycle'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AWS', 'EC2', 'instances', 'AMIs', 'security groups', 'key pairs', 'connectivity'. These cover common terminology users would naturally use when working with EC2. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on AWS EC2 with distinct triggers like 'EC2', 'AMIs', 'security groups', 'key pairs'. Unlikely to conflict with other cloud or infrastructure skills due to specific AWS EC2 terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive EC2 reference with excellent actionable code examples in both CLI and Python. However, it's overly verbose for a skill file, including conceptual explanations Claude doesn't need and lacking the progressive disclosure structure that would make it more token-efficient. The workflow clarity could be improved with explicit validation steps for multi-step operations.
Suggestions
Remove or drastically reduce the Core Concepts section - Claude knows what AMIs, security groups, and instance types are. Keep only project-specific conventions if any.
Split the CLI Reference tables and detailed troubleshooting into separate reference files (e.g., CLI_REFERENCE.md, TROUBLESHOOTING.md) and link to them from the main skill.
Add explicit validation checkpoints to multi-step workflows, e.g., 'Verify security group created: aws ec2 describe-security-groups --group-ids sg-xxx' before proceeding to launch.
Add a verification step after instance launch showing how to confirm the instance is accessible before considering the task complete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content like the Core Concepts section explaining what AMIs and Security Groups are, which Claude already knows. The tables for instance types and purchasing options add bulk without being directly actionable. | 2 / 3 |
Actionability | Excellent executable code examples throughout - both AWS CLI and boto3 snippets are copy-paste ready with realistic parameters. Commands include all necessary flags and the troubleshooting section provides concrete diagnostic commands. | 3 / 3 |
Workflow Clarity | The 'Launch an Instance' section shows a clear sequence (create key pair → create security group → add rules → launch), but lacks explicit validation checkpoints. For destructive operations like terminate-instances, there's no verification workflow or confirmation steps mentioned. | 2 / 3 |
Progressive Disclosure | The document has good structure with a table of contents and clear sections, but it's monolithic - all content is inline rather than appropriately split into separate reference files. The CLI Reference tables and Best Practices could be separate files with links from the main skill. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- itsmostafa/aws-agent-skills
- Commit
5df6da7
- 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.