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/antigravity-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 essentially a placeholder with no substantive content. It repeats its own description multiple times, provides no actionable guidance, code examples, architecture patterns, or workflows for AWS development. The boilerplate limitations section is the most detailed part of the file, which itself is generic and not AWS-specific.

Suggestions

Add concrete, executable 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 pipeline).

Include actual AWS architecture patterns with code samples rather than just describing the skill's scope repeatedly.

If detailed content exists in the linked repository, extract key patterns into bundle files and reference them with clear navigation from SKILL.md.

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 rather than instructs, offering only a link to an external repository with no inline content.	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 actually perform any AWS-related task.	1 / 3
Progressive Disclosure	There are no bundle files, no referenced supporting documents, and the only external reference is a GitHub link with no description of what it contains. The content is a near-empty shell 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, reading more like a resume bullet point than a skill selector. It lacks concrete actions, specific AWS services, and any 'Use when...' guidance. The inclusion of 'AWS' as a keyword is its strongest element, but the description needs significantly more detail to be useful for skill selection among many options.

Suggestions

List specific concrete actions such as 'Write CloudFormation templates, configure Lambda functions, set up VPCs, manage S3 buckets, deploy CDK stacks'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS services, cloud deployment, CloudFormation, CDK, serverless architecture, or any AWS resource configuration'.

Include natural trigger terms for specific AWS services and tools users would mention: 'EC2', 'S3', 'Lambda', 'CDK', 'CloudFormation', 'IAM', 'serverless', 'deploy to AWS'.

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 down 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', 'deploy', or 'serverless' that users would naturally mention.	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

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: boisenoise/skills-collections
Commit: 47e0c5a

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