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
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill aws-solution-architect36
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 establishes a clear domain focus on AWS architecture for startups but reads more like a tagline than actionable skill guidance. It lacks concrete actions Claude would perform and critically omits any 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about AWS architecture, serverless design, Lambda, CDK, CloudFormation, or cloud infrastructure for startups'
Replace abstract descriptors with concrete actions: 'Design serverless architectures, write CDK/CloudFormation templates, configure Lambda functions, set up API Gateway endpoints'
Include common user phrasings and service names: 'AWS', 'Lambda', 'S3', 'DynamoDB', 'deploy to cloud', 'cloud costs', 'Terraform'
| 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 architectures', 'write CloudFormation templates', or 'configure Lambda functions'. | 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 variations users might say like 'Lambda', 'CDK', 'Terraform', 'cloud setup', or 'deploy to AWS'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'startups' focus and combination of 'serverless' + 'cost-effective' provides some distinction, but 'DevOps practices' and 'infrastructure-as-code' are broad enough to overlap with general DevOps or IaC skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like an AWS reference guide or blog post than actionable Claude instructions. It extensively catalogs AWS services and patterns Claude already understands, while failing to provide the concrete code templates, executable scripts, or step-by-step workflows that would make it useful. The mentioned scripts don't exist in the content, and there are no actual CloudFormation/CDK/Terraform examples despite promising them.
Suggestions
Replace service descriptions with actual executable code: provide real CloudFormation/CDK templates for each architecture pattern instead of just listing components
Include the actual script implementations (architecture_designer.py, iac_generator.py, etc.) or remove references to non-existent scripts
Add concrete workflows with validation steps, e.g., 'Step 1: Run cost analysis -> Step 2: Validate template with cfn-lint -> Step 3: Deploy to staging -> Step 4: Verify with smoke tests'
Remove explanations of what AWS services are (Lambda, DynamoDB, etc.) and focus only on startup-specific decision criteria and implementation patterns Claude wouldn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400 lines with extensive explanations of AWS services Claude already knows. Lists capabilities, service descriptions, and general cloud concepts that don't add actionable value beyond Claude's existing knowledge. | 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 concrete implementation examples. | 1 / 3 |
Workflow Clarity | No clear step-by-step workflows with validation checkpoints. The 'How to Use' section lists example prompts but doesn't explain the actual process. Migration and deployment guidance is vague ('1-3 days setup time') without concrete steps. | 1 / 3 |
Progressive Disclosure | Content is organized into logical sections (Architecture Patterns, Best Practices, Service Selection), but everything is in one monolithic file. References to external resources are URLs rather than linked skill files, and the document would benefit from splitting detailed patterns into separate files. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.