Name: amazon-eks
Rating: 53.6 (1 reviews)
Author: membranedev

amazon-eks

Amazon EKS integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon EKS data.

Quality

60%

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/amazon-eks/SKILL.md

Quality

Content

63%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 highly actionable with concrete CLI commands and a well-sequenced connection workflow including state-based validation, but it opens with unnecessary EKS background, repeats the discovery command, and inlines reference-grade material that would benefit from separate files. Overall solid and usable with moderate trimming and restructuring.

Suggestions

Remove or condense the opening paragraph explaining what Amazon EKS is, since Claude already knows this.

De-duplicate the action-discovery command that appears in both 'Searching for actions' and 'Popular actions'.

Move the proxy request flag table and the detailed clientAction state handling into a separate reference file and link to it from the main body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but the opening paragraph explains what Amazon EKS is (a concept Claude already knows) and the action-discovery command is repeated in both 'Searching for actions' and 'Popular actions', fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (npm install, membrane login, connection ensure, action run, request with a full flag table), with only minor gaps such as inconsistent membrane vs npx invocation and unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → search → run sequence is clear and includes state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a polling feedback loop, but the 'Step 2' reference and '1b' labeling are not cleanly anchored to numbered steps.	4 / 5
Progressive Disclosure	The skill is a ~140-line single file with no bundle files and no external references, and content that could be split out (the proxy flag table, the detailed clientAction state machine) is inlined, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

57%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 names a specific domain and includes an explicit 'Use when' trigger, but its capability list is generic rather than EKS-specific and it omits common synonyms like Kubernetes and clusters. It is functional but could be sharpened to reduce overlap and improve trigger coverage.

Suggestions

Replace 'Manage data, records, and automate workflows' with EKS-specific actions such as managing clusters, node groups, addons, and Fargate profiles.

Add natural trigger synonyms users would say, e.g. 'Kubernetes on AWS', 'EKS clusters', or 'AWS Kubernetes'.

Tighten the 'what' so it concretely reflects the actions documented in the body rather than generic data/workflow phrasing.

Dimension	Reasoning	Score
Specificity	The domain (Amazon EKS) is named, but the listed actions — 'Manage data, records, and automate workflows' — are generic and not EKS-specific (no clusters, node groups, or addons), matching the 'names the domain but actions are minimal or generic' anchor rather than the concrete-action anchor at 3.	2 / 5
Completeness	Both 'what' (Amazon EKS integration, manage data/records/automate workflows) and an explicit 'when' ('Use when the user wants to interact with Amazon EKS data') are present, though the 'what' is generic enough that it does not reach the fully concrete anchor at 5.	4 / 5
Trigger Term Quality	'Amazon EKS' and 'EKS data' are relevant natural keywords, but common variations users would say — 'Kubernetes', 'AWS', 'clusters', 'EKS clusters' — are absent, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'Amazon EKS' is a clear, specific niche with a distinct trigger phrase, but the generic action phrasing leaves minor overlap risk with broader AWS or Kubernetes skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 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/amazon-eks/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.