Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 provides specific pattern names, uses third person voice appropriately, includes an explicit 'Use when' clause with natural trigger terms, and carves out a clear niche that distinguishes it from general coding or architecture skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete patterns (Factory, Builder, Strategy, Observer, Decorator) and specifies Java examples, clearly describing what the skill provides. | 3 / 3 |
Completeness | Clearly answers both what (common design patterns with Java examples) and when (explicit 'Use when' clause with specific trigger phrases and use case scenario). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'implement pattern', 'use factory', 'strategy pattern', plus the contextual trigger 'designing extensible components' which captures intent-based queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around design patterns specifically in Java context; trigger terms like 'factory', 'strategy pattern', 'implement pattern' are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable design patterns reference with excellent code examples and clear decision guidance. The main weakness is its length - at ~500 lines with multiple implementation variants per pattern, it could benefit from splitting detailed examples into separate reference files while keeping SKILL.md as a concise overview with the quick reference table and basic examples.
Suggestions
Consider moving Spring-specific implementations to a separate SPRING-PATTERNS.md file and linking to it
The detailed code examples for each pattern could be in individual files (e.g., patterns/builder.md) with SKILL.md containing only the quick reference table and brief descriptions
Remove the 'Alternative: Using records' section for Builder - it adds length without being the primary recommendation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the content is well-organized and avoids explaining basic concepts, it's quite lengthy at ~500 lines. Some patterns include multiple implementation variants (e.g., Spring alternatives) that could be split into separate reference files rather than inline. | 2 / 3 |
Actionability | Excellent executable code examples throughout. Every pattern includes complete, copy-paste ready Java code with clear usage examples. The anti-pattern comparisons (❌ vs ✅) provide concrete guidance on what to avoid. | 3 / 3 |
Workflow Clarity | For a reference skill, workflow clarity is appropriate. The quick reference table at the top provides clear decision guidance, and each pattern section follows a consistent structure: use case, code example, usage demonstration. | 3 / 3 |
Progressive Disclosure | The skill mentions related skills at the end but keeps all pattern implementations inline rather than splitting detailed examples into separate files. The Spring alternatives and multiple variants per pattern could be in linked reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (748 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
d9fda23
Table of Contents
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.