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/antigravity-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, lacks a 'Use when...' clause, and uses broad terms that could overlap with other infrastructure or cloud skills. It needs significant improvement in specificity and completeness.
Suggestions
List specific concrete actions such as 'Write CloudFormation templates, configure Lambda functions, set up VPC networking, manage IAM policies, deploy with CDK'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS services, cloud deployment, CloudFormation, CDK, serverless architecture, or AWS infrastructure setup'.
Include natural trigger terms users would say, such as 'S3', 'EC2', 'Lambda', 'CloudFormation', 'CDK', 'serverless', 'deploy to AWS', '.yaml templates'.
| 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 only weakly addresses 'what' (AWS development with automation and patterns) and completely lacks a 'when' clause. There are no explicit triggers or guidance for when Claude should select this skill. | 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 cloud or infrastructure 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. The same generic description is repeated across multiple sections, providing zero actionable guidance on AWS development, infrastructure automation, or cloud architecture patterns. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples for common AWS tasks (e.g., CDK stack definitions, CloudFormation templates, CLI commands for deploying infrastructure).
Define clear multi-step workflows for key operations like provisioning infrastructure, with validation checkpoints (e.g., 'cdk diff' before 'cdk deploy').
Replace the repeated generic description with specific patterns and guidance for AWS architecture (e.g., VPC setup, IAM best practices, common service integrations).
If detailed content exists in the referenced GitHub repository, either inline the most critical guidance or create bundle files with clear references from the SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and repetition. The overview, 'when to use', and 'instructions' sections all repeat the same sentence verbatim. There is no substantive information that Claude doesn't already know. | 1 / 3 |
Actionability | There are no concrete commands, code examples, architecture patterns, or specific AWS guidance. The skill describes rather than instructs, offering only a link to an external repository with no actionable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. For a skill about infrastructure automation and cloud architecture, there should be at least some sequenced guidance, but none is provided. | 1 / 3 |
Progressive Disclosure | There are no bundle files and no meaningful references beyond a single external GitHub link. The content is a near-empty shell with no structured navigation to deeper materials. | 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
- boisenoise/skills-collections
- Commit
8ac11ab
- 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.