aws-solution-architect

Expert AWS solution architecture for startups focusing on serverless, scalable, and cost-effective cloud infrastructure with modern DevOps practices and infrastructure-as-code

Overall
score

29%

Review — 17%

Does it follow best practices?

Validation — 13 / 16 Passed

Validation for skill structure

Install with Tessl CLI

npx tessl i github:alirezarezvani/claude-skills --skill aws-solution-architect

Activation

33%

The description establishes a clear domain focus on AWS architecture for startups with modern practices, but lacks concrete actions and explicit trigger guidance. It reads more like a tagline than a functional skill description, missing the 'Use when...' clause entirely which is critical for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about AWS architecture, Lambda functions, serverless design, or cloud deployment for startups'

List specific concrete actions such as 'Design serverless architectures, create CloudFormation/CDK templates, configure API Gateway and Lambda, optimize AWS costs'

Include more natural trigger terms users would say: 'Lambda', 'S3', 'DynamoDB', 'Terraform', 'CDK', 'deploy to AWS', 'cloud costs'

Dimension	Reasoning	Score
Specificity	Names the domain (AWS, cloud infrastructure) and mentions some approaches (serverless, scalable, cost-effective, DevOps, infrastructure-as-code), but doesn't list concrete actions like 'design Lambda architectures', 'create CloudFormation templates', or 'configure API Gateway'.	2 / 3
Completeness	Describes what the skill covers (AWS architecture for startups) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'AWS', 'serverless', 'cloud infrastructure', 'DevOps', and 'infrastructure-as-code', but misses common user terms like 'Lambda', 'S3', 'EC2', 'Terraform', 'CDK', or 'deploy to AWS'.	2 / 3
Distinctiveness Conflict Risk	The 'startups' focus and 'serverless' emphasis provide some distinction, but 'cloud infrastructure' and 'DevOps practices' are broad enough to potentially overlap with general cloud or DevOps skills.	2 / 3
	Total	7 / 12 Passed

Implementation

This skill reads like an AWS documentation overview rather than actionable guidance for Claude. It explains concepts Claude already knows (AWS services, their purposes, general best practices) without providing executable code, concrete templates, or clear workflows. The content would benefit from dramatic reduction and focus on startup-specific decision frameworks with actual IaC templates.

Suggestions

Remove service descriptions and general AWS knowledge - focus only on startup-specific decision criteria and trade-offs Claude wouldn't know

Add actual executable CloudFormation/CDK/Terraform templates for the architecture patterns instead of just describing stacks

Create a clear workflow with validation steps: e.g., '1. Run cost estimator script → 2. Validate against budget → 3. Generate IaC → 4. Validate template → 5. Deploy to staging'

Split content into SKILL.md (quick decision framework) with references to separate files: PATTERNS.md, TEMPLATES/, COMPLIANCE.md

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400 lines with extensive explanations of AWS concepts Claude already knows (what Lambda is, what DynamoDB does, basic service descriptions). Lists capabilities, service selection guides, and compliance information that are general AWS knowledge rather than startup-specific actionable guidance.	1 / 3
Actionability	Despite mentioning scripts like 'architecture_designer.py' and 'iac_generator.py', no actual code is provided. The content describes what could be done rather than providing executable templates, commands, or copy-paste ready configurations. Architecture patterns are high-level descriptions without implementation details.	1 / 3
Workflow Clarity	No clear step-by-step workflows with validation checkpoints. The 'How to Use' section shows example prompts but no actual process. Migration strategies mention 'phased migration plans' but provide no concrete steps. No feedback loops or verification steps for any operations.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including detailed service selection guides, compliance information, and architecture patterns that should be in separate reference documents. No clear navigation structure or signposted references.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	13 / 16 Passed

Reviewed

20 days ago

Table of Contents

Activation 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.