aws-sdk-java-v2-rds
AWS RDS (Relational Database Service) management using AWS SDK for Java 2.x. Use when creating, modifying, monitoring, or managing Amazon RDS database instances, snapshots, parameter groups, and configurations.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-rds84
Quality
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Quality
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 clearly specifies the technology stack (AWS RDS + Java 2.x SDK), lists concrete actions and resources, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating, modifying, monitoring, or managing' and specific RDS resources: 'database instances, snapshots, parameter groups, and configurations'. | 3 / 3 |
Completeness | Clearly answers both what ('AWS RDS management using AWS SDK for Java 2.x') and when ('Use when creating, modifying, monitoring, or managing Amazon RDS database instances, snapshots, parameter groups, and configurations'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AWS RDS', 'Relational Database Service', 'database instances', 'snapshots', 'parameter groups'. Also specifies the SDK context 'AWS SDK for Java 2.x' for technical users. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically AWS RDS with Java 2.x SDK. Unlikely to conflict with other database skills or AWS skills due to the specific service and SDK combination. | 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 solid, actionable skill with excellent code examples and good progressive disclosure structure. The main weaknesses are verbosity in introductory sections that don't add value for Claude, and missing validation/verification workflows for database operations that could have destructive consequences.
Suggestions
Remove the 'When to Use This Skill' and 'Support' sections - Claude can infer appropriate usage and doesn't need external support links
Add explicit validation workflows for destructive operations (e.g., verify instance status before/after deletion, check snapshot completion before proceeding)
Consolidate the 'Best Practices' section into fewer, more impactful code snippets rather than many small fragments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' (Claude can infer this), 'Support' links, and verbose introductory text. However, the code examples themselves are reasonably efficient without excessive explanation. | 2 / 3 |
Actionability | Provides fully executable Java code examples with proper imports, complete method signatures, and copy-paste ready snippets. Each operation (create, modify, delete, snapshot) has concrete, working code. | 3 / 3 |
Workflow Clarity | Operations are presented individually but lack explicit validation checkpoints or feedback loops. For destructive operations like deleteDBInstance, there's no verification workflow (check status, confirm deletion, handle failures). The 'always close clients' note is good but workflows for multi-step processes are missing. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (spring-boot-integration.md, lambda-integration.md, api-reference.md). References are one level deep and clearly signaled with descriptive context about what each contains. | 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 |
|---|---|---|
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | 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.