aws-skills

AWS development with infrastructure automation and cloud architecture patterns

Quality

42%

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 ./skills/aws-skills/SKILL.md

Quality

Content

40%Weight 40%Scale 1-5

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

The body is well-sectioned and lean, but it is essentially boilerplate with no executable guidance, no concrete examples, and no real workflow, so it adds almost no actionable value beyond the description. Its only meaningful content is a link to the source repository and generic limitation caveats.

Suggestions

Add concrete, executable guidance — example Terraform/CloudFormation snippets, common CLI commands, or a representative task walkthrough — instead of restating the description.

Define an actual workflow with sequenced steps (e.g., provision → validate → deploy) including a validation checkpoint for destructive infra changes.

Replace the boilerplate 'Instructions' paragraph with skill-specific patterns or move detailed material into reference files linked one level deep.

Dimension	Reasoning	Score
Conciseness	The body is terse and does not over-explain concepts Claude already knows (no 'what is AWS' padding), but several lines are boilerplate ("This skill provides guidance and patterns for...") that do not earn their place, fitting score 4's 'efficient; minor instances that could be trimmed' rather than the fully-lean score 5.	4 / 5
Actionability	The body offers only abstract description ("provides guidance and patterns for aws development...") with no code, commands, or specific steps, matching score 1's 'entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.	1 / 5
Workflow Clarity	There is no real multi-step workflow, only loosely sequenced boilerplate sections plus a generic 'stop and ask for clarification' note; this sits between score 1 (no sequence) and score 3 (steps listed with validation gaps), closer to score 2's 'rough sequence present but many gaps'.	2 / 5
Progressive Disclosure	The under-50-line body is organized into clear sections (Overview, When to Use, Instructions, Limitations) and points to a single one-level-deep external reference (the source repository URL), fitting score 4's 'good structure; references mostly clear' though no bundle files exist to warrant deeper splitting.	4 / 5
	Total	11 / 20 Passed

Description

45%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the AWS domain and a couple of topic areas but uses no concrete action verbs and provides no 'Use when' trigger guidance, leaving it vague and hard to match. It is borderline distinguishable due to the AWS scope yet broad enough to overlap with many AWS skills.

Suggestions

Add concrete action verbs (e.g., 'Provision', 'Deploy', 'Refactor') instead of topic-area nouns so the capability is specific.

Append an explicit 'Use when...' clause with natural trigger phrases users would say (e.g., Terraform, CloudFormation, IaC, infrastructure-as-code).

Narrow the scope (e.g., a specific IaC tool or set of services) to reduce overlap with other AWS skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("AWS development") plus two topic areas ("infrastructure automation", "cloud architecture patterns") but describes no concrete actions, matching the score-2 anchor of naming the domain with minimal/generic actions; it falls short of score 3 which requires 1-2 concrete actions like 'extracts' or 'fills'.	2 / 5
Completeness	It states a 'what' (AWS development with infra automation and cloud architecture patterns) but has no 'Use when...' or equivalent trigger clause, so per the missing-trigger cap it cannot exceed 3; the 'what' is identifiable but not as concrete as the score-3 example.	3 / 5
Trigger Term Quality	Terms like "AWS development", "infrastructure automation", and "cloud architecture patterns" are somewhat natural, but common synonyms users would actually say (Terraform, CloudFormation, IaC, deployment, .tf) are missing, fitting score 3's 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	AWS-specificity narrows it somewhat, but "AWS development" is broad and would overlap with many related AWS skills (Terraform, CloudFormation, Lambda, etc.), fitting score 3's 'somewhat specific but could still overlap with similar skills'.	3 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/aws-skills/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours 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.