aws-sdk-java-v2-messaging
Implement AWS messaging patterns using AWS SDK for Java 2.x for SQS queues and SNS topics. Send/receive messages, manage FIFO queues, implement DLQ, publish messages, manage subscriptions, and build pub/sub patterns.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-messaging77
Quality
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aws-java/aws-sdk-java-v2-messaging/SKILL.mdQuality
Discovery
82%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 strong technical description with excellent specificity and trigger term coverage for AWS Java developers. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description clearly carves out a distinct niche but relies on implicit context rather than explicit selection guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to implement messaging with SQS or SNS in Java, or mentions AWS queues, topics, or pub/sub patterns.'
Consider adding file extension triggers like '.java' or mentioning 'Maven/Gradle dependencies' as additional natural trigger terms developers might use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Send/receive messages, manage FIFO queues, implement DLQ, publish messages, manage subscriptions, and build pub/sub patterns' - these are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the technical context. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AWS', 'SQS', 'SNS', 'queues', 'topics', 'FIFO', 'DLQ', 'pub/sub', 'messaging', 'Java 2.x', 'subscriptions' - good coverage of technical terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: AWS SDK for Java 2.x + SQS/SNS messaging. The combination of AWS, Java SDK version, and specific services (SQS, SNS) creates a distinct trigger profile unlikely to conflict with other skills. | 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 solid, actionable skill with excellent code examples that are immediately executable. The main weaknesses are some verbosity in introductory sections and missing validation/verification steps in the workflow guidance, which is important for messaging systems where message loss can occur silently.
Suggestions
Remove or significantly trim the 'Overview' and 'When to Use' sections - Claude already knows what SQS and SNS are used for
Add explicit validation steps in the workflow, such as verifying message delivery with message IDs, checking DLQ for failed messages, and confirming subscription status before publishing
Add a feedback loop example showing how to verify messages were processed successfully and handle partial batch failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use' that explain obvious use cases Claude would know. The 'Overview' section restates what the title already conveys. However, the code examples themselves are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Java code examples for all major operations including client setup, queue creation, message sending/receiving, FIFO queues, SNS-SQS subscriptions, and Spring Boot integration. All examples include proper imports and are complete. | 3 / 3 |
Workflow Clarity | The 'Implement Message Processing' section lists steps but lacks explicit validation checkpoints. For messaging operations that can fail silently or lose messages, there's no feedback loop for verifying message delivery or handling partial failures in batch operations. | 2 / 3 |
Progressive Disclosure | Well-structured with Quick Start, Examples (basic to advanced), Best Practices, and Instructions sections. References detailed documentation files for comprehensive coverage. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | 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 |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 10 / 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.