CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-solution-architect

Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.

84

1.24x
Quality

85%

Does it follow best practices?

Impact

81%

1.24x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is aws-solution-architect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

A highly actionable, well-sequenced workflow with strong validation and failure-handling loops, undermined by structural redundancy across sections and references to bundle files that are not actually provided.

Suggestions

De-duplicate the requirements (Step 1 vs. 'Input Requirements'), the tool documentation (Workflow vs. 'Tools'), and the pattern lists (Step 2 vs. 'Quick Start') so each fact appears in one place.

Provide the referenced bundle files (references/architecture_patterns.md, service_selection.md, best_practices.md, and the scripts/*.py invoked in the workflow) or remove the references and inline only what is needed.

Move the large CloudFormation YAML and CDK TypeScript blocks into the reference files, keeping only a compact representative snippet inline in SKILL.md.

DimensionReasoningScore

Conciseness

Avoids explaining basic concepts Claude already knows, but carries real redundancy: requirements appear in Step 1 and again in the 'Input Requirements' table/JSON, tools are documented in the Workflow and repeated in 'Tools', and patterns are listed in Step 2 and restated in 'Quick Start'.

3 / 5

Actionability

Provides mostly executable guidance (real aws CLI commands, CloudFormation YAML, CDK TypeScript), but the core workflow invokes scripts/*.py that are not present in the bundle and one CloudWatch alarm command is truncated with '...'.

4 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint (Step 2) and a thorough failure-recovery feedback loop in Step 6 (check failure reason, review logs, fix, delete failed stack, redeploy).

5 / 5

Progressive Disclosure

References are signaled one level deep, but the referenced files (references/architecture_patterns.md, references/service_selection.md, references/best_practices.md and scripts/*.py) do not exist in the bundle, and large code blocks that could live in references are inlined, leaving organization weaker than the signaling suggests.

3 / 5

Total

15

/

20

Passed

Description

100%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.

A strong, well-structured description that concretely states capabilities, gives explicit 'Use when' triggers with natural phrasing, and names specific AWS services to anchor its niche. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS') plus a covered-services list (Lambda, API Gateway, DynamoDB, ECS, Aurora), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (Design AWS architectures for startups using serverless patterns and IaC templates; covers named services) and 'when' ('Use when asked to design serverless architecture, create CloudFormation templates...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ('optimize AWS costs', 'create CloudFormation templates', 'migrate to AWS', 'set up CI/CD pipelines') with synonyms (CloudFormation/IaC, serverless).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (AWS serverless/IaC architecture for startups) with AWS-specific service names and distinct triggers, minimizing overlap with generic cloud or coding skills.

5 / 5

Total

20

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 11 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-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.