CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-skills

AWS development with infrastructure automation and cloud architecture patterns

46

1.01x
Quality

18%

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-claude/skills/aws-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

14%Scale 1-3

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 three times and provides no actionable guidance, code examples, workflows, or structured references. It fails on every dimension because it contains no actual skill instructions.

Suggestions

Add concrete, executable code examples for common AWS tasks (e.g., CDK stack deployment, CloudFormation template snippets, CLI commands for common operations).

Define clear multi-step workflows with validation checkpoints for infrastructure operations (e.g., deploy -> validate -> rollback on failure).

Replace the repeated description with actual AWS patterns and guidance, organized into sections like 'Quick Start', 'Common Patterns', and 'Advanced Topics' with references to detailed sub-documents.

Remove the redundant 'When to Use This Skill' and 'Instructions' sections that merely restate the overview, and replace them with specific, actionable content.

DimensionReasoningScore

Conciseness

The content is short but entirely vacuous — it repeats the same description three times ('AWS development with infrastructure automation and cloud architecture patterns') without adding any actual information. While not verbose in the traditional sense, every token is wasted because none provides value.

2 / 3

Actionability

There are no concrete instructions, code examples, commands, or specific guidance whatsoever. The skill merely restates its own description and links to an external repository without any actionable content.

1 / 3

Workflow Clarity

No workflow, steps, or processes are described. There is no sequence of actions, no validation checkpoints, and no guidance on how to accomplish any task.

1 / 3

Progressive Disclosure

The only reference is a link to an external GitHub repository with no description of what it contains. There is no structured navigation, no signposted sub-documents, and no meaningful content organization.

1 / 3

Total

5

/

12

Passed

Description

22%Scale 1-3

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 to effectively guide skill selection. It names the domain (AWS) but fails to list concrete actions, lacks a 'Use when...' clause, and uses broad terms like 'cloud architecture patterns' that don't help distinguish it from other infrastructure or cloud skills.

Suggestions

List specific concrete actions such as 'Provisions AWS resources using CloudFormation/CDK, configures Lambda functions, sets up VPCs and IAM policies, deploys serverless applications'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS services, CloudFormation templates, CDK stacks, Lambda, S3, EC2, or deploying to AWS.'

Include natural trigger terms users would say, such as specific AWS service names (Lambda, S3, EC2, RDS, DynamoDB), file types (.yaml, .json for CloudFormation), and action verbs (deploy, provision, configure).

DimensionReasoningScore

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 cloud or coding skills, but 'infrastructure automation' and 'cloud architecture patterns' are broad enough to overlap with Terraform, general DevOps, or other cloud provider skills.

2 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.