aws-skills
AWS development with infrastructure automation and cloud architecture patterns
42
11%
Does it follow best practices?
Impact
98%
1.01xAverage score across 3 eval scenarios
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 high-level to effectively guide skill selection. It names the domain (AWS) but fails to list concrete actions, lacks a 'Use when...' clause, and uses abstract buzzwords like 'cloud architecture patterns' instead of specific capabilities. It would benefit significantly from concrete action verbs and explicit trigger conditions.
Suggestions
List specific concrete actions such as 'Provisions AWS resources using CloudFormation/CDK, configures Lambda functions, sets up VPCs, manages S3 buckets, and deploys serverless applications.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS services, CloudFormation templates, CDK stacks, Lambda, EC2, S3, or cloud infrastructure deployment.'
Include natural trigger terms users would say, such as specific AWS service names (Lambda, EC2, S3, RDS, DynamoDB), file types (.yaml, .json for CloudFormation), and common task phrases ('deploy to AWS', 'set up infrastructure').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract 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' but only in vague terms, and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, but the 'what' is also weak enough to warrant a 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', 'deploy', or 'serverless' that users would naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'AWS' provides some specificity that distinguishes it from generic cloud or coding skills, but 'infrastructure automation' and 'cloud architecture patterns' are broad enough to overlap with Terraform, general DevOps, or other cloud provider 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 real content. The description is repeated three times as the overview, 'when to use,' and instructions sections, providing zero actionable guidance. It fails on every dimension as it contains no code, no commands, no workflows, and no meaningful references.
Suggestions
Replace the repeated description with actual AWS patterns, concrete CLI commands, or IaC code examples (e.g., CDK/CloudFormation snippets) that Claude can directly use.
Add specific workflow steps for common AWS tasks (e.g., deploying a stack, setting up IAM roles) with validation checkpoints like checking deployment status.
If detailed content lives in the GitHub repo, inline the most critical patterns in SKILL.md and link to specific sub-files (e.g., 'See [CDK_PATTERNS.md](CDK_PATTERNS.md) for construct examples') rather than just linking the repo root.
Define the scope clearly—specify which AWS services, tools (CDK, SAM, Terraform), and patterns are covered so Claude knows when and how to apply this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler that restates the description three times with no substantive information. Every line is redundant or obvious. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, or specific guidance of any kind. The skill provides zero actionable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are described. There is nothing for Claude to follow or execute. | 1 / 3 |
Progressive Disclosure | The only reference is an external GitHub link with no indication of what it contains. There is no structured navigation, no linked sub-files, and no organized content hierarchy. | 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
e874770
- 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.