aws-sdk-java-v2-core
Core patterns and best practices for AWS SDK for Java 2.x. Use when configuring AWS service clients, setting up authentication, managing credentials, configuring timeouts, HTTP clients, or following AWS SDK best practices.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-core80
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Quality
Discovery
89%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-structured skill description that clearly identifies its domain (AWS SDK for Java 2.x) and provides explicit trigger guidance. The 'Use when...' clause covers multiple relevant scenarios. The main weakness is that the capabilities could be more specific - listing concrete actions like 'implement retry policies' or 'configure connection pooling' rather than general configuration categories.
Suggestions
Consider adding more specific concrete actions like 'implement retry strategies', 'configure connection pooling', 'set up async clients' to improve specificity beyond general configuration categories
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AWS SDK for Java 2.x) and mentions several actions like 'configuring AWS service clients', 'setting up authentication', 'managing credentials', 'configuring timeouts', but these are somewhat general configuration tasks rather than highly specific concrete actions like 'create S3 bucket policies' or 'implement retry strategies'. | 2 / 3 |
Completeness | Clearly answers both what ('Core patterns and best practices for AWS SDK for Java 2.x') and when ('Use when configuring AWS service clients, setting up authentication, managing credentials, configuring timeouts, HTTP clients, or following AWS SDK best practices'). Has explicit 'Use when...' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'AWS SDK', 'Java 2.x', 'service clients', 'authentication', 'credentials', 'timeouts', 'HTTP clients', 'best practices'. These are terms developers naturally use when working with AWS SDK configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting AWS SDK for Java 2.x specifically, with distinct triggers around SDK configuration, credentials, and client setup. Unlikely to conflict with general Java skills or other AWS-related skills due to the specific SDK version and configuration focus. | 3 / 3 |
Total | 11 / 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 and highly actionable skill for AWS SDK Java 2.x with excellent code examples and good progressive disclosure. The main weaknesses are moderate verbosity (some sections explain concepts Claude already knows) and missing explicit validation/verification workflows for ensuring proper client configuration and error recovery patterns.
Suggestions
Remove the 'When to Use' section entirely - Claude can infer appropriate usage from the content itself
Add explicit validation steps for client configuration, such as a health check pattern to verify credentials and connectivity before production use
Trim explanatory prose like 'This skill provides essential patterns for building robust...' and let the code examples speak for themselves
Add a troubleshooting workflow with explicit steps: check credentials -> verify region -> test connectivity -> validate permissions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity like the 'When to Use' section listing obvious use cases, and explanatory text that Claude would already understand. The content could be tightened by removing redundant explanations while keeping the valuable code examples. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes complete Java code with proper imports, Maven/Gradle dependencies, and configuration examples that can be directly used. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the skill lacks explicit validation checkpoints and feedback loops. For example, the testing section doesn't include verification steps, and there's no guidance on validating that clients are properly configured before use in production scenarios. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from Quick Start to advanced topics. References to detailed documentation in 'references/' directory and related skills are clearly signaled with one-level-deep navigation. Content is appropriately split between overview and detailed sections. | 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 (660 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.