aws-skills

AWS development with infrastructure automation and cloud architecture patterns

Quality

11%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/aws-skills/SKILL.md

Quality

Content

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 placeholder that provides no actionable content whatsoever. It repeats its own description three times, contains no code, commands, patterns, or concrete guidance for AWS development, and delegates entirely to an external repository without summarizing or structuring any of that content. It fails on every dimension of the rubric.

Suggestions

Add concrete, executable code examples for core AWS tasks (e.g., CDK stack definitions, CloudFormation templates, CLI commands for common operations).

Define specific workflows with validation steps for infrastructure deployment (e.g., synth -> diff -> deploy -> verify), including error recovery guidance.

Replace the repeated description with actual patterns and guidance covering specific AWS services and architecture patterns relevant to the skill's scope.

If detailed content exists in the linked repository, extract key reference material into bundle files and provide a clear overview with one-level-deep references to those files.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely filler. It repeats the description verbatim multiple times ('aws development with infrastructure automation and cloud architecture patterns' appears 3 times), provides no actual technical content, and the 'Instructions' section contains no instructions—just a link to an external repository.	1 / 3
Actionability	There is zero concrete, executable guidance—no code, no commands, no specific patterns, no examples. The entire skill is a vague placeholder that describes rather than instructs, offering nothing Claude can act on.	1 / 3
Workflow Clarity	No workflow, steps, or processes are defined at all. There are no sequences, no validation checkpoints, and no guidance on how to perform 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%

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 relies on broad buzzwords like 'infrastructure automation' and 'cloud architecture patterns' instead of specific capabilities.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about AWS services, deploying infrastructure, or working with CloudFormation, CDK, Lambda, S3, EC2, or other AWS resources.'

Replace vague phrases with concrete actions, e.g., 'Creates CloudFormation/CDK templates, configures Lambda functions, sets up VPCs and networking, manages IAM policies, and deploys serverless architectures.'

Include common AWS service names and file extensions as trigger terms (e.g., '.yaml templates', 'SAM', 'serverless', 'terraform', 'EC2', 'S3', 'RDS') to improve keyword coverage.

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 coding skills, but 'development', 'infrastructure automation', and 'cloud architecture patterns' are broad enough to overlap with general DevOps, IaC, or cloud engineering 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: sickn33/antigravity-awesome-skills
Commit: 9431b67

Reviewed: 3 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.