troubleshooting-s3-files

Diagnoses and resolves Amazon S3 Files issues including mount failures, permission errors, synchronization problems, and performance issues. Use when the user has an S3 file system that is not mounting, returning access denied, not syncing changes to S3, showing files in lost+found, or performing slower than expected.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/storage-skills/troubleshooting-s3-files/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.

A well-structured diagnostic guide: every category pairs a symptom with an executable command or a precise fix, the symptom-to-category table gives an unambiguous entry point, and safety gating of mutating commands is explicit. The remaining gaps are minor — one vague destructive branch, a single-distro install command, and light redundancy.

Suggestions

Add a validation checkpoint before the destructive 'delete/recreate the file system' branch in Category C (e.g., confirm statusMessage shows access denied via get-file-system, and confirm with the user before deleting), which would raise workflow_clarity to a 5.

Extend the Category A install fix beyond Amazon Linux (e.g., apt/get URL or build-from-source one-liner for Ubuntu) and add the concrete command for verifying a KMS key in Category G, closing the actionability gaps.

Drop the duplicated AWS troubleshooting link (Overview vs. Additional Resources) and replace the Overview paragraph with a one-line pointer to the classification table to trim redundant tokens.

Dimension	Reasoning	Score
Conciseness	Mostly lean — terse tables, direct commands, and no tutorials on concepts Claude already knows — but includes minor trimmable redundancy: the AWS troubleshooting doc link appears in both Overview and Additional Resources, and the Overview restates the description verbatim, so it fits anchor 4 rather than 5.	4 / 5
Actionability	Concrete, copy-paste-ready commands dominate (e.g., 'aws s3files list-mount-targets --file-system-id fs-ID --region REGION', 'nc -zv az-ID.fs-ID.s3files.REGION.on.aws 2049', the getfattr status check), but the install fix covers only Amazon Linux and branches like 'fix the IAM role and delete/recreate' and 'verify key is enabled' lack commands, matching anchor 4.	4 / 5
Workflow Clarity	Clear sequence — verify dependencies, classify via symptom table, then category-specific fixes — with embedded verification commands (statusMessage check, getfattr sync status, nc connectivity test, VPC attribute checks) and section 0 explicitly gating mutating commands. The destructive 'delete/recreate' branch lacks a pre-destruction validation loop, keeping it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	A single ~180-line file with well-organized headers, a symptom-classification table, and clearly signaled external AWS doc links. It is above the 50-line simple-skill case and some deep-dive material (IAM details, the sync error table) could live in separate reference files, so anchor 4 fits better than 5.	4 / 5
	Total	16 / 20 Passed

Description

83%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 with an explicit 'Use when...' clause containing natural, symptom-based trigger phrases and a clear third-person statement of capabilities. Its only weaknesses are that the capability list is issue-category-level rather than fully enumerated and a few natural synonym triggers are absent.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('mount failures, permission errors, synchronization problems, and performance issues') but these are issue categories rather than a fully comprehensive set of actions — conflict resolution appears only via the lost+found trigger, matching anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both questions: 'Diagnoses and resolves Amazon S3 Files issues including...' states what it does, and 'Use when the user has an S3 file system that is not mounting, returning access denied...' provides concrete trigger phrases, matching the anchor-5 example exactly.	5 / 5
Trigger Term Quality	Natural symptom phrases like 'not mounting', 'returning access denied', 'not syncing changes to S3', and 'performing slower than expected' mirror what users would say, but common synonyms and variations (e.g., 'mount stuck', 'slow S3') are missing, so it falls just short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	'Amazon S3 Files' names a specific product with product-specific symptoms (lost+found, s3files mount) giving a clear niche, but generic S3 or other file-system complaints could still overlap slightly, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	17 / 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: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/storage-skills/troubleshooting-s3-files/SKILL.md
Commit: b8171ad

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