Name: aws-well-architected
Rating: 61.6 (1 reviews)
Author: membranedev

aws-well-architected

AWS Well-Architected integration. Manage data, records, and automate workflows. Use when the user wants to interact with AWS Well-Architected data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aws-well-architected/SKILL.md

Quality

Content

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

The body is a strong, executable guide to the Membrane CLI integration with concrete commands and clear state-handling in the connection workflow. It loses points mainly for a short concept-explainer preamble Claude does not need and a slightly under-labeled, validation-light workflow sequence.

Suggestions

Trim or remove the opening paragraph explaining what AWS Well-Architected is and listing the five pillars; Claude already knows this and it competes with context budget.

Add an explicit validation/retry feedback loop for the connection flow (poll -> on CLIENT_ACTION_REQUIRED prompt user -> re-poll until READY) and label the referenced 'Step 2' anchor so the sequence is unambiguous.

Consider moving the full proxy flag reference table into a separate references file and keeping only the most common flags inline, which would push progressive disclosure to a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tight tables, though the opening paragraph restating what AWS Well-Architected is and the five pillars is concept explanation Claude already knows and could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready membrane CLI commands with flags, a parameter table, and worked examples for install, auth, connection, action discovery, action running, and proxy requests.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling checkpoints, but it lacks a validate-then-retry feedback loop and the numbering is inconsistent (it references 'Step 2' that is not labeled).	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (install, auth, connecting, searching, popular actions, proxy, best practices) with no nested references and no bundle files to manage, though some material like the full proxy flag table could live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

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

The description states both what the skill does and when to use it, anchored to a specific product niche, but its capability phrasing is generic boilerplate ('Manage data, records, and automate workflows') rather than concrete AWS Well-Architected actions. Tightening the action list and adding trigger synonyms would lift specificity and trigger-term quality.

Suggestions

Replace the boilerplate 'Manage data, records, and automate workflows' with concrete Well-Architected actions such as 'review workloads, answer pillar questions, manage milestones and lenses, and retrieve workload records'.

Expand the trigger clause with natural synonyms users might say, e.g. 'Use when the user mentions Well-Architected reviews, workload reviews, pillar questions, or WA tool'.

Keep the third-person imperative voice but make the 'when' clause more specific than 'interact with ... data' to reduce overlap with generic AWS skills.

Dimension	Reasoning	Score
Specificity	Names the domain (AWS Well-Architected) and a couple of generic actions ('Manage data, records, and automate workflows'), but the actions are not specific to the skill's concrete capabilities and read as boilerplate rather than a precise enumeration.	3 / 5
Completeness	Both 'what' (AWS Well-Architected integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with AWS Well-Architected data') are present, though the 'when' clause is fairly broad and could be more specific.	4 / 5
Trigger Term Quality	It includes 'Use when the user wants to interact with AWS Well-Architected data' with the product name as a trigger, but offers no synonyms, abbreviations, or natural variations a user might say, so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The narrow product name 'AWS Well-Architected' gives it a clear niche unlikely to collide with unrelated skills, with only minor overlap risk against generic AWS integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/aws-well-architected/SKILL.md
Commit: f484c82

Reviewed: 5 minutes 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.