CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-advisor

Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 well-structured, information-dense skill body with excellent progressive disclosure and mostly actionable guidance. The weakest areas are workflow validation (conditional steps exist but no checkpoints or feedback loops) and mild token inefficiency from inline IaC code examples that restate known syntax.

Suggestions

Move the four IaC code examples (Terraform/Serverless/SAM/CDK) into a references file (e.g., references/iac-examples.md) and keep only the selection table inline, cutting a significant block of syntax Claude already knows.

Add one example invocation with arguments and expected output per script (e.g., 'python scripts/security_review.py --services s3,lambda') so the workflow steps are copy-paste executable.

Add explicit validation checkpoints to the workflows, e.g., in Standard Question Flow: 'If search results don't answer the question, refine the query with different keywords before responding' — a feedback loop the current steps lack.

DimensionReasoningScore

Conciseness

The body is dense and table-driven — IaC selection, MCP tools, and search topics are all compact tables with no concept explanations Claude already knows. It falls short of the 5 anchor because the four inline IaC code examples (Terraform/SAM/CDK/Serverless 'Hello World' templates) restate syntax Claude already knows and duplicate the decision table's guidance, padding that could be trimmed or moved to a reference file.

4 / 5

Actionability

Guidance is mostly executable: exact MCP tool names ('aws___search_documentation') with topic/keyword mappings, concrete script paths in workflows, and a suggested user-facing question to ask. It sits below the 5 anchor because scripts are invoked by name only ('Run: scripts/well_architected_review.py') without example arguments or expected output, leaving a minor gap before copy-paste readiness.

4 / 5

Workflow Clarity

Three workflows are clearly sequenced with numbered steps and conditional branches ('Read if needed', 'Verify regional → if relevant'), but checkpoints are implicit — there is no validation of results (e.g., confirming documentation search answered the question) and no error-recovery guidance if a search returns nothing. This matches the 3 anchor ('sequence present but checkpoints missing or implicit') rather than 4, which requires most checkpoints explicitly present.

3 / 5

Progressive Disclosure

The body is a clean overview with well-signaled, one-level-deep navigation: a 'Reference Files' table with 'Load When' conditions linking references/mcp-guide.md, decision-trees.md, and checklists.md (all verified to exist, none referencing further files), and a scripts table with purposes. Content is appropriately split with nothing buried, matching the 5 anchor.

5 / 5

Total

16

/

20

Passed

Description

91%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 description: explicit what-and-when structure, comprehensive natural trigger terms including service names and task verbs, and a clear negative boundary. The only softness is that capability phrasing ('implementation guidance') is slightly generic and Terraform/CDK/Serverless triggers could collide with dedicated IaC skills.

DimensionReasoningScore

Specificity

The description names several concrete capabilities — 'architecture design, security review, and implementation guidance' — plus the mechanism 'Leverages AWS MCP tools for accurate, documentation-backed answers'. It falls just short of the 5 anchor because 'implementation guidance' is somewhat generic compared to the fully enumerated action lists in the top examples, and it clearly exceeds the 3 anchor (domain plus only 1-2 actions).

4 / 5

Completeness

It explicitly answers both questions: what ('Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance') and when ('Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS'), with concrete trigger phrases — the exact structure of the 5 anchor example. It also adds an explicit negative boundary ('Do NOT use for non-AWS cloud providers...'), which goes beyond the 4 anchor.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: service names users actually say ('Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway') plus task-oriented phrases ('service selection, migrations, troubleshooting, or learning AWS') and the catch-all 'or any AWS service'. This matches the 5 anchor's standard of synonyms and broad natural coverage with nothing significant missing.

5 / 5

Distinctiveness Conflict Risk

The AWS-only niche and explicit exclusion ('Do NOT use for non-AWS cloud providers or general infrastructure without AWS context') make it mostly distinct with minimal conflict risk. However, triggering on 'Terraform', 'Serverless', and 'CDK' creates minor overlap with dedicated IaC skills for those tools, keeping it just below the 5 anchor's 'clear niche with distinct triggers; minimal conflict risk'.

4 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-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.