aws-sdk-java-v2-s3
Amazon S3 patterns and examples using AWS SDK for Java 2.x. Use when working with S3 buckets, uploading/downloading objects, multipart uploads, presigned URLs, S3 Transfer Manager, object operations, or S3-specific configurations.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-s384
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It uses third person voice, provides specific concrete actions, includes natural trigger terms developers would use, and clearly distinguishes itself by specifying both the AWS service (S3) and the SDK (Java 2.x). The explicit 'Use when...' clause with comprehensive trigger scenarios makes it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'uploading/downloading objects, multipart uploads, presigned URLs, S3 Transfer Manager, object operations, S3-specific configurations' - these are all distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Amazon S3 patterns and examples using AWS SDK for Java 2.x') and when ('Use when working with S3 buckets, uploading/downloading objects...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'S3 buckets', 'uploading/downloading', 'multipart uploads', 'presigned URLs', 'S3 Transfer Manager' - these match how developers naturally describe S3 tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets AWS SDK for Java 2.x with S3, includes unique triggers like 'presigned URLs', 'S3 Transfer Manager', and 'multipart uploads' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable S3 skill with excellent code examples that are immediately usable. The main weaknesses are some verbosity in explanatory sections and missing validation/verification steps in multi-step workflows, particularly for batch operations and error recovery scenarios.
Suggestions
Trim the 'When to Use' section to 4-5 key scenarios; Claude can infer related use cases
Add explicit validation steps to batch processing example (e.g., verify upload count matches file count, check for failed uploads in response)
Remove explanatory text in Best Practices that states obvious concepts (e.g., 'Clients are thread-safe') and keep only the actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, particularly in the 'When to Use' section which lists 12 bullet points that Claude could infer. The Best Practices section explains concepts Claude already knows (e.g., 'Clients are thread-safe and should be reused'). However, code examples are generally lean. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every operation includes complete Java code with proper imports, error handling, and realistic usage patterns. Dependencies are clearly specified with Maven coordinates. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints for multi-step processes. The batch processing example doesn't include verification that uploads succeeded beyond 'All files uploaded successfully'. No feedback loops for error recovery in complex operations like multipart uploads. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from basic to advanced. References section appropriately points to external detailed documentation with one-level-deep links. Content is logically organized: setup → basic operations → advanced operations → integration → examples → best practices. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (691 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 Passed | |
- 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.