Name: aws-s3
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

aws-s3

AWS S3 integration. Manage Buckets. Use when the user wants to interact with AWS S3 data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/aws-s3/SKILL.md

Quality

Content

75%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 content is highly actionable with copy-paste CLI commands and a clear connection workflow with state-based checkpoints. Its main weakness is conciseness — the introductory paragraph re-explains S3 concepts Claude already knows — alongside minor organization gaps where reference-style detail is inlined.

Suggestions

Remove or condense the opening S3 overview paragraph and the filler line "Use action names and parameters as needed." since Claude already knows what S3 is.

Consider moving the proxy request flag table and the clientAction state reference into a separate reference file to improve progressive disclosure.

Add an explicit validation/verification step after running S3 actions (e.g., re-list the bucket to confirm a write succeeded) to strengthen the feedback loop for destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("AWS S3 is a cloud-based object storage service… Developers and businesses use it to store and retrieve any amount of data…") and filler like "Use action names and parameters as needed." explain concepts Claude already knows, while the bulk is lean CLI commands — matching "mostly efficient but includes some unnecessary explanation" rather than the minor-trim anchor above.	3 / 5
Actionability	The body is packed with copy-paste-ready commands (membrane login, connection ensure, action list/run with --input JSON, request with full flag table) that cover the common integration cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install → auth → connection ensure → poll until READY → search → run) with explicit state-based checkpoints and error-recovery guidance (CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but validation around the actual S3 operations themselves is implicit, leaving a minor gap short of the full feedback-loop anchor.	4 / 5
Progressive Disclosure	As a single well-sectioned SKILL.md with no bundle files, it is organized into clear top-level sections (Overview, Working with AWS S3, Popular actions, Best practices); content like the proxy flag table and clientAction state reference is inline and could be split out, but structure is good with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

68%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 cleanly names a distinct AWS S3 niche with a usable trigger clause, but its capability list is too thin (only "Manage Buckets") to be comprehensive. Strengthening the action coverage would lift specificity and completeness.

Suggestions

Expand the capability list beyond "Manage Buckets" to concrete actions like creating/listing buckets, uploading, downloading, and deleting objects.

Add natural trigger variations and synonyms (e.g., "object storage", "S3 objects") to improve trigger-term coverage.

Make the "Use when" clause more specific by naming common intents (e.g., upload or download files, list bucket contents).

Dimension	Reasoning	Score
Specificity	The phrase "Manage Buckets" names the AWS S3 domain but offers only one minimal, generic action with no mention of objects, uploads, downloads, or listings — closer to "names the domain but actions are minimal or generic" than to the two-action anchor above.	2 / 5
Completeness	Both parts are present (what: "AWS S3 integration. Manage Buckets."; when: "Use when the user wants to interact with AWS S3 data"), but the "what" is thin and the trigger could be more specific, matching the anchor where both exist yet could be more explicit.	4 / 5
Trigger Term Quality	It surfaces natural terms users say — "AWS S3", "S3 data", "Buckets" — giving good keyword coverage, though synonyms like "object storage" and variations are missing, so it stops short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	"AWS S3" is a clear, narrowly-scoped niche with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	15 / 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-s3/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.