aws-skills

AWS development with infrastructure automation and cloud architecture patterns

1.01x

Quality

21%

Does it follow best practices?

Impact

98%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/aws-skills/SKILL.md

The canonical home for this skill is aws-skills in sickn33/agentic-awesome-skills

Quality

Content

15%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 a near-empty placeholder that restates the description three times without any executable guidance, workflow steps, or substantive reference material. It provides nothing Claude could act on.

Suggestions

Replace the repeated generic sentences with concrete, actionable guidance: specific AWS CLI or Terraform commands and short executable code examples for the common tasks.

Add a real workflow sequence (e.g. provision -> configure -> validate -> deploy) with explicit validation checkpoints for any destructive or batch operations.

Either populate the Instructions with substantive patterns or split detailed material into well-signaled reference files (e.g. terraform-patterns.md, iam-best-practices.md) instead of linking only to an external repo.

Dimension	Reasoning	Score
Conciseness	The body repeats the same generic phrase verbatim three times across Overview, When to Use, and Instructions, which is unnecessary padding despite the short length, matching the 'noticeably verbose; several unnecessary padded sections' anchor; not a 3 because the repetition is pure filler rather than minor over-explanation.	2 / 5
Actionability	The Instructions section only states 'This skill provides guidance and patterns for aws development...' with no concrete code, commands, or steps, matching the 'entirely vague or abstract; no concrete code or commands' anchor; it cannot be a 2 because there are not even high-level actionable hints.	1 / 5
Workflow Clarity	No multi-step process, sequence, or validation checkpoints are present anywhere in the body, matching the 'steps missing or incoherent; no sequence' anchor; not a 2 because there is not even a rough sequence to evaluate.	1 / 5
Progressive Disclosure	Section headers (Overview, When to Use, Instructions) provide some structure and no bundle files are needed, but the sections are hollow and contain no substantive reference material or signaled deeper content, fitting the 'some structure but could be better organized' anchor; not a 4 because there is no real content appropriately placed and the only link is to an external repo.	3 / 5
	Total	7 / 20 Passed

Description

28%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 that names AWS but provides no concrete actions, no natural trigger phrasing, and no explicit use-when guidance. It risks blending in with many other cloud/DevOps skills.

Suggestions

Replace abstract nouns with concrete actions, e.g. 'Provision AWS resources with Terraform/CloudFormation, design VPC and IAM architectures, and automate deployments'.

Add an explicit trigger clause: 'Use when working with AWS infrastructure, writing Terraform or CloudFormation, or designing cloud architecture for AWS services'.

Include natural trigger terms users actually say (Terraform, CloudFormation, EC2, S3, Lambda, IAM, VPC) to improve trigger matching and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the AWS domain and broad areas ('infrastructure automation', 'cloud architecture patterns') but lists no concrete actions like 'provision', 'deploy', or 'write Terraform', matching the 'names the domain but actions are minimal or generic' anchor; it is not a 1 because AWS is a concrete domain, and not a 3 because no actionable verbs are present.	2 / 5
Completeness	Provides a vague 'what' ('AWS development with infrastructure automation and cloud architecture patterns') and has no 'Use when...' trigger clause, matching the 'has a vague what and no when' anchor; the missing explicit trigger guidance caps it below 3 per the rubric guideline.	2 / 5
Trigger Term Quality	'AWS' is a natural keyword but the phrasing 'AWS development with infrastructure automation and cloud architecture patterns' is generic and misses the specific terms users actually say (Terraform, CloudFormation, EC2, S3, Lambda), fitting the 'one or two generic keywords; missing the natural phrases users say' anchor; not a 3 because no common variations or synonyms appear.	2 / 5
Distinctiveness Conflict Risk	AWS-specific framing gives it a niche, but the broad scope ('cloud architecture patterns') would overlap with general cloud or DevOps skills, matching the 'somewhat specific but could still overlap with similar skills' anchor; not a 4 because the description is too generic within AWS to be clearly distinct.	3 / 5
	Total	9 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/aws-skills/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.