aws-skills
AWS development with infrastructure automation and cloud architecture patterns
22
11%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aws-skills/SKILL.mdQuality
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 names the domain (AWS) but fails to list concrete actions, specific AWS services, or any trigger guidance. Without a 'Use when...' clause and specific capabilities, Claude would struggle to reliably select this skill over other cloud or infrastructure-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about AWS services, CloudFormation templates, CDK stacks, Lambda functions, or deploying to AWS.'
List specific concrete actions such as 'Creates CloudFormation/CDK templates, configures IAM policies, sets up VPCs, deploys Lambda functions, manages S3 buckets.'
Include natural trigger terms users would say, such as 'AWS', 'EC2', 'S3', 'Lambda', 'serverless', 'deploy to cloud', 'IAM', 'CloudFormation', 'CDK'.
| 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 the skill actually does (e.g., deploy CloudFormation stacks, configure Lambda functions, set up VPCs). | 1 / 3 |
Completeness | The description partially addresses 'what' (AWS development, infrastructure automation) but in very vague terms, and completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | 'AWS' is a strong natural keyword users would say, and 'infrastructure automation' and 'cloud architecture' are somewhat relevant. However, it's missing common variations like 'CloudFormation', 'CDK', 'Terraform', 'Lambda', 'S3', 'EC2', 'serverless', or 'deploy'. | 2 / 3 |
Distinctiveness Conflict Risk | 'AWS' provides some specificity that distinguishes it from generic coding or DevOps skills, but 'infrastructure automation' and 'cloud architecture patterns' are broad enough to overlap with Terraform, Kubernetes, or general DevOps skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%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 substantive content. It repeats its own description multiple times without providing any actual AWS guidance, code examples, architecture patterns, or infrastructure automation instructions. The limitations section is generic boilerplate that could apply to any skill.
Suggestions
Add concrete, executable examples for core AWS tasks (e.g., CDK/CloudFormation templates, CLI commands for common operations, IAM policy patterns).
Define clear multi-step workflows for key scenarios like deploying infrastructure, with validation checkpoints (e.g., 'cdk diff' before 'cdk deploy', checking CloudFormation stack status).
Replace the repeated description with actual architectural patterns and decision guidance (e.g., when to use Lambda vs ECS, VPC design patterns, cost optimization strategies).
If detailed content exists in the linked repository, extract key reference materials into bundle files and link to them from the SKILL.md with clear section headers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler. It repeats the same description ('aws development with infrastructure automation and cloud architecture patterns') four times and provides no actual technical content. The 'When to Use' and 'Instructions' sections add zero information beyond the overview. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, architecture patterns, or any executable guidance whatsoever. The skill describes what it is about but never actually teaches anything. It simply links to an external repository. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. For a skill about infrastructure automation and cloud architecture, there should be clear multi-step workflows (e.g., deploying infrastructure, configuring services), but none are present. | 1 / 3 |
Progressive Disclosure | There are no bundle files, no referenced supporting documents, and the only external reference is a GitHub link with no indication of what it contains. The content is a monolithic placeholder with no meaningful structure or navigation. | 1 / 3 |
Total | 4 / 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
- sickn33/antigravity-awesome-skills
- Commit
76aea27
- 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.