CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-skills

AWS development with infrastructure automation and cloud architecture patterns

52

1.01x
Quality

27%

Does it follow best practices?

Impact

98%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

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 body is a near-empty placeholder that repeats the description across three sections and provides no actionable guidance, no workflow steps, and no reference materials beyond an external repo link.

Suggestions

Add concrete, executable guidance in the Instructions section: example Terraform/CloudFormation snippets, specific AWS CLI commands, or named service configuration patterns.

Replace the three repeated restatements of the description with distinct, useful content per section (e.g., real triggers in When-to-Use, actual patterns/steps in Instructions).

Provide a sequenced workflow with validation checkpoints for any infrastructure provisioning or deployment operations the skill is meant to guide.

DimensionReasoningScore

Conciseness

The body is brief and does not over-explain concepts Claude already knows, but it repeats the identical phrase 'aws development with infrastructure automation and cloud architecture patterns' across the Overview, When-to-Use, and Instructions sections, which is redundant and could be tightened; fits the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; not a 4 because the triple repetition is unnecessary padding.

3 / 5

Actionability

The Instructions section only states 'This skill provides guidance and patterns' with no concrete code, commands, or specific steps, matching the 'entirely vague or abstract; only describes rather than instructs' anchor; not a 2 because there is not even a high-level hint toward executable steps.

1 / 5

Workflow Clarity

There is no sequence of steps, no procedure, and no validation checkpoints anywhere in the body, matching the 'steps missing or incoherent; no sequence' anchor; not a 2 because not even a rough step list is present.

1 / 5

Progressive Disclosure

The body is organized into clearly labeled sections (Overview, When to Use This Skill, Instructions) with a single one-level-deep external link to the source repository and no nested references, fitting the 'good structure; most content appropriately placed; minor organization gaps' anchor; not a 5 because the section content is essentially a placeholder and there are no well-signaled internal reference paths.

4 / 5

Total

9

/

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 single generic sentence that names the AWS domain but provides no concrete actions, no natural trigger phrases, and no 'when to use' guidance, giving it high overlap risk with other cloud skills.

Suggestions

Add a 'Use when...' clause listing concrete trigger phrases (e.g., 'Use when provisioning AWS resources with Terraform/CloudFormation, configuring EC2/S3/IAM, or deploying cloud infrastructure').

Replace generic terms with specific actions such as 'provision', 'deploy', 'configure', 'orchestrate' tied to named AWS services or IaC tools.

Include natural synonyms and file/extension terms users actually say (Terraform, CloudFormation, .tf, SAM, CDK) to improve trigger-term quality and distinctiveness.

DimensionReasoningScore

Specificity

The description names the AWS domain but the actions are minimal and generic ('development', 'infrastructure automation', 'cloud architecture patterns') with no concrete operations listed, matching the 'names the domain but actions are minimal or generic' anchor; not a 1 because it does identify a domain, and not a 3 because no 1-2 concrete actions are specified.

2 / 5

Completeness

It provides a vague 'what' ('AWS development with infrastructure automation and cloud architecture patterns') and entirely omits any 'when/Use when' guidance, matching the 'vague what and no when' anchor; per the rubric a missing 'Use when' clause caps completeness at 3, and the vagueness pushes it to 2.

2 / 5

Trigger Term Quality

It offers a couple of generic keywords ('AWS development', 'infrastructure automation', 'cloud architecture patterns') but misses the natural terms users actually say (Terraform, CloudFormation, EC2, provision, deploy), fitting the 'one or two generic keywords; missing the natural phrases' anchor; not a 3 because the keywords lack common variations or synonyms.

2 / 5

Distinctiveness Conflict Risk

Naming the AWS platform adds some specificity, but 'infrastructure automation and cloud architecture patterns' is broad and would overlap with general cloud/IaC skills, matching the 'somewhat specific but could still overlap' anchor; not a 2 because AWS is a concrete platform niche, and not a 4 because the generic phrasing keeps overlap risk elevated.

3 / 5

Total

9

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.