aws-cloud

AWS cloud infrastructure patterns and best practices. Use when designing or implementing AWS solutions including EC2, Lambda, S3, RDS, and infrastructure as code with Terraform or CloudFormation.

Quality

63%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops-data/skills/aws-cloud/SKILL.md

Quality

Discovery

89%

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 is a solid skill description with excellent trigger term coverage and clear completeness through an explicit 'Use when' clause. The main weakness is the somewhat vague capability description - 'patterns and best practices' and 'designing or implementing' could be more concrete with specific actions like provisioning, configuring, or deploying.

Suggestions

Replace 'patterns and best practices' with specific concrete actions like 'provision EC2 instances, configure S3 buckets, set up Lambda functions, design VPC architectures'

Consider adding more trigger variations like 'serverless', 'cloud deployment', 'AWS architecture', or file extensions like '.tf' for Terraform

Dimension	Reasoning	Score
Specificity	Names the domain (AWS cloud infrastructure) and lists specific services (EC2, Lambda, S3, RDS) and tools (Terraform, CloudFormation), but describes actions vaguely as 'patterns and best practices' and 'designing or implementing' rather than listing concrete actions like 'provision EC2 instances, configure S3 buckets, write Terraform modules'.	2 / 3
Completeness	Clearly answers both what ('AWS cloud infrastructure patterns and best practices') and when ('Use when designing or implementing AWS solutions including...') with an explicit 'Use when' clause and specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'AWS', 'EC2', 'Lambda', 'S3', 'RDS', 'Terraform', 'CloudFormation', 'infrastructure as code', 'cloud infrastructure'. These cover common service names and IaC tools users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific AWS service names and IaC tools as triggers. Unlikely to conflict with other skills unless there are multiple AWS-specific skills, as the combination of AWS services plus Terraform/CloudFormation creates a clear niche.	3 / 3
	Total	11 / 12 Passed

Implementation

37%

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

This skill provides a surface-level overview of AWS services and concepts but lacks the actionable depth needed for implementation. It reads more like a reference card than a skill that teaches Claude how to perform specific tasks. The single Terraform example is helpful but isolated, and critical workflows for infrastructure deployment are entirely missing.

Suggestions

Add a complete Terraform workflow with validation: terraform init -> plan -> review -> apply -> verify, including how to handle plan errors

Replace the basic service table with specific implementation patterns Claude doesn't already know (e.g., Lambda cold start mitigation, RDS connection pooling patterns)

Add executable examples for at least 2-3 more common tasks (e.g., S3 bucket with proper security, IAM role for Lambda, CloudFormation stack deployment)

Include references to separate files for detailed topics: IAM_PATTERNS.md, TERRAFORM_MODULES.md, CLOUDFORMATION_TEMPLATES.md

Dimension	Reasoning	Score
Conciseness	The content is relatively lean and avoids excessive explanation, but includes basic information Claude already knows (e.g., 'EC2 = Virtual servers', 'S3 = Object storage'). The Well-Architected Framework summary is also common knowledge for Claude.	2 / 3
Actionability	Provides one concrete Terraform example which is executable, but most content is high-level bullet points and descriptions rather than actionable code or commands. Security and cost sections are lists of principles, not specific implementation guidance.	2 / 3
Workflow Clarity	No workflows are defined. There's no sequence for deploying infrastructure, no validation steps for Terraform (plan/apply/verify), and no guidance on how to actually implement the patterns mentioned. For IaC operations, missing terraform plan/apply workflow with validation is a significant gap.	1 / 3
Progressive Disclosure	Content is organized into clear sections which is good, but everything is in one file with no references to detailed materials for complex topics like IAM policies, CloudFormation templates, or specific service configurations that would benefit from separate files.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 24 days 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.