aws-skills

AWS development with infrastructure automation and cloud architecture patterns

Quality

35%

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

26%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 SKILL.md body is an auto-generated stub: it repeats the same vague phrase across four sections and provides no executable guidance, code, commands, or workflow. Section organization is reasonable, but the content is substantively empty.

Suggestions

Replace the descriptive Instructions section with concrete, executable guidance: specific commands or code snippets for the common AWS infrastructure tasks (e.g. a Terraform apply workflow or a CloudFormation deploy command).

Add a sequenced workflow with explicit validation checkpoints for destructive or batch operations (e.g. plan -> validate -> apply -> verify), which is required to lift workflow_clarity above 1.

Eliminate the verbatim repetition across Overview/When-to-Use/Instructions; give each section distinct, earned content so every token adds value.

Dimension	Reasoning	Score
Conciseness	The body is short in absolute terms, but the Overview, When-to-Use, and Instructions sections all repeat the identical phrase 'AWS development with infrastructure automation and cloud architecture patterns' verbatim, which is redundant padding that should be tightened; not a 4 because the repetition is clearly unnecessary.	3 / 5
Actionability	The Instructions section only states 'This skill provides guidance and patterns for...' with no code, commands, or concrete steps, matching the anchor 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.	1 / 5
Workflow Clarity	There is no multi-step process, sequence, or validation checkpoint anywhere in the body; the Limitations mention validation generically but do not constitute a workflow, fitting 'Steps missing or incoherent; no sequence'.	1 / 5
Progressive Disclosure	The body is under 50 lines with clear section headers (Overview, When to Use, Instructions, Example, Limitations) and no bundle files are needed; structure is good with only minor gaps (the sole reference is an external repo link rather than a bundle file), so it sits above a 3 but lacks the one-level-deep bundle references of a 5.	4 / 5
	Total	9 / 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 is a generic domain label rather than an actionable capability statement: it names AWS infrastructure automation but provides no concrete actions, no natural trigger phrases, and no explicit 'use when' guidance. It is coherent enough to avoid the lowest scores but reads as buzzword filler.

Suggestions

Replace the abstract phrase with concrete actions, e.g. 'Provision AWS resources with Terraform/CloudFormation, automate deployment pipelines, and design cloud architecture patterns'.

Add an explicit trigger clause: 'Use when the user asks to provision, deploy, or refactor AWS infrastructure, or mentions Terraform, CloudFormation, EC2, S3, or AWS deployment pipelines'.

Include natural synonyms and service names users actually say (Terraform, CloudFormation, EC2, S3, IAM) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ("AWS development", "infrastructure automation", "cloud architecture patterns") but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic' rather than level 3 which requires 1-2 concrete actions.	2 / 5
Completeness	It states a 'what' (AWS infrastructure automation) but contains no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3; it is not a 2 because the what names a coherent domain rather than being entirely vague.	3 / 5
Trigger Term Quality	Relevant keywords like 'AWS' and 'infrastructure automation' are present, but the phrasing is buzzword-heavy and misses the natural terms users would actually say (e.g. deploy, provision, Terraform, CloudFormation, EC2); not comprehensive enough for a 4.	3 / 5
Distinctiveness Conflict Risk	Being AWS-specific gives some distinctiveness, but the extremely broad scope ('infrastructure automation and cloud architecture patterns') creates high overlap risk with many possible AWS-related skills, fitting 'somewhat specific but could still overlap'.	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/agentic-awesome-skills
Path: skills/aws-skills/SKILL.md
Commit: b1aebac

Reviewed: ~17 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.