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.
Overall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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, provides 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-specific terminology makes it highly distinctive.
| 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' - good coverage of terms a user working with EC2 would naturally mention. | 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 AWS-specific 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 long for a skill file, including conceptual explanations Claude doesn't need and reference tables that could be externalized. The workflow guidance is present but lacks explicit validation checkpoints for multi-step operations.
Suggestions
Remove or drastically reduce the Core Concepts section - Claude knows what AMIs, security groups, and instance types are
Move the CLI Reference tables to a separate REFERENCE.md file and link to it
Add explicit validation steps to workflows, e.g., 'Verify security group was created: aws ec2 describe-security-groups --group-ids sg-xxx' before proceeding to launch
Add a confirmation/verification step before destructive operations like terminate-instances
| 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. The CLI Reference tables and Core Concepts could be separate reference files, with SKILL.md serving as a leaner overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.