aws-skills
AWS development with infrastructure automation and cloud architecture patterns
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill aws-skills46
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/skillEvaluation — 98%
↑ 1.01xAgent success when using this skill
Validation for skill structure
Discovery
22%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 description is too vague and abstract to effectively guide skill selection. It lacks concrete actions, specific AWS services or tools, and provides no explicit trigger guidance for when Claude should select this skill. The presence of 'AWS' is helpful but insufficient without more detail.
Suggestions
Add specific concrete actions like 'Deploy Lambda functions, configure S3 buckets, create CloudFormation/CDK templates, set up IAM policies'
Add a 'Use when...' clause with explicit triggers such as 'Use when the user mentions AWS, Lambda, EC2, S3, CloudFormation, CDK, or needs to deploy to Amazon cloud services'
Include common AWS service names and tools (Lambda, EC2, S3, RDS, Terraform, CDK, SAM) as natural trigger terms users would mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'infrastructure automation' and 'cloud architecture patterns' without listing any concrete actions. It doesn't specify what operations can be performed (e.g., deploy Lambda functions, configure S3 buckets, create CloudFormation templates). | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (AWS development, infrastructure automation) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains 'AWS' which is a strong natural keyword users would say, plus 'cloud' and 'infrastructure'. However, it's missing common variations like specific AWS services (EC2, S3, Lambda), 'terraform', 'CDK', 'serverless', or 'deploy'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'AWS' provides some specificity, 'infrastructure automation' and 'cloud architecture' are broad enough to potentially overlap with other cloud provider skills (GCP, Azure) or general DevOps/IaC skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It repeats its description multiple times but provides zero concrete guidance on AWS development, infrastructure automation, or cloud architecture patterns. The skill fails to teach Claude anything useful and merely points to an external repository.
Suggestions
Add concrete, executable code examples for common AWS operations (e.g., boto3 snippets for EC2, S3, Lambda)
Include specific infrastructure-as-code patterns with Terraform or CloudFormation templates
Define clear workflows for common tasks like deploying infrastructure, with validation checkpoints
Create separate reference files for different AWS services and link to them with clear descriptions of what each contains
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but provides almost no substance - it's concise by virtue of being empty rather than efficient. The repetition of the description in multiple places is unnecessary padding. | 2 / 3 |
Actionability | No concrete guidance, code, commands, or examples are provided. The skill merely describes what it's about and points to an external repository without any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. There's no guidance on how to actually perform any AWS-related tasks or what sequence of actions to take. | 1 / 3 |
Progressive Disclosure | The only reference is to an external GitHub repository with no context about what's there. No internal structure, no signposted sections for different topics, and no clear navigation to detailed materials. | 1 / 3 |
Total | 5 / 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 | |
- 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.