aws-skills

AWS development with infrastructure automation and cloud architecture patterns

Quality

11%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/aws-skills/SKILL.md

Quality

Content

0%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is an empty shell 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 code examples for key AWS tasks (e.g., CDK stack definitions, CloudFormation templates, CLI commands for common operations).

Define specific workflows with validation steps for infrastructure operations (e.g., deploy -> validate -> rollback pattern).

Replace the repeated abstract description with actual AWS architecture patterns, service-specific guidance, and best practices.

Either include bundle files with detailed references (e.g., patterns for Lambda, ECS, S3) or inline the essential content directly in the skill body.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely filler. It repeats the description ('aws development with infrastructure automation and cloud architecture patterns') four times and provides no actual technical content. Every line is either redundant or states something Claude already knows.	1 / 3
Actionability	There are zero concrete instructions, no code examples, no commands, no specific AWS services mentioned, no architecture patterns described. The skill provides absolutely no executable or actionable guidance—it merely describes itself in abstract terms and links to an external repository.	1 / 3
Workflow Clarity	No workflow, steps, or processes are defined. There is no sequence of actions, no validation checkpoints, and no guidance on how to accomplish any AWS-related task.	1 / 3
Progressive Disclosure	There are no bundle files, no referenced supporting documents, and the only link is to an external GitHub repository 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

Description

22%Scale 1-3

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 like 'infrastructure automation' and 'cloud architecture patterns' that don't tell Claude what the skill specifically does or when to invoke it.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about AWS services, deploying infrastructure, writing CloudFormation/CDK templates, or configuring cloud resources.'

List specific concrete actions the skill performs, e.g., 'Creates CloudFormation templates, configures Lambda functions, sets up VPCs and security groups, deploys S3 buckets and IAM policies.'

Include natural trigger terms users would say, such as 'CloudFormation', 'CDK', 'Lambda', 'EC2', 'S3', 'deploy', 'provision', 'serverless', and specific AWS service names.

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 weakly addresses 'what' (AWS development with infrastructure automation) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent.	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 'provision'.	2 / 3
Distinctiveness Conflict Risk	'AWS' provides some specificity that distinguishes it from generic cloud or coding skills, but 'development' and 'cloud architecture patterns' are broad enough to overlap with general cloud skills, IaC tools, or DevOps-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills/skills/aws-skills/SKILL.md
Commit: a5a6601

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.