design-pattern-suggestor
Recognizes structural situations that match known design patterns and recommends whether to apply them — or explains why the pattern doesn't fit. Use when the user has a structural problem and is considering a pattern, when reviewing a design that uses a pattern questionably, or when the user asks which pattern fits their situation.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill design-pattern-suggestor90
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
75%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 description has strong completeness with an explicit 'Use when...' clause covering multiple scenarios, and good distinctiveness for its design pattern niche. However, it could benefit from more specific concrete actions (naming actual patterns) and additional natural trigger terms users might use when seeking pattern guidance.
Suggestions
Add specific pattern examples to increase specificity, e.g., 'Recognizes when to apply patterns like Factory, Observer, Strategy, or Singleton'
Include more natural trigger terms users might say, such as 'refactoring', 'code structure', 'architecture decision', or specific pattern names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (design patterns) and describes actions (recognizes, recommends, explains), but lacks specific concrete examples of which patterns or what types of structural situations it handles. | 2 / 3 |
Completeness | Clearly answers both what (recognizes structural situations, recommends patterns, explains fit) AND when with explicit 'Use when...' clause covering three distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes 'design patterns' and 'pattern' as keywords, but misses common variations users might say like 'factory pattern', 'singleton', 'refactoring', 'architecture', or specific pattern names that would naturally trigger this skill. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on design pattern recognition and recommendation; the explicit focus on 'structural situations' and 'pattern fit' creates distinct triggers unlikely to conflict with general code review or architecture skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Excellent skill that embodies the 'problem first, pattern second' philosophy it teaches. The 'or maybe just' column is particularly valuable for preventing pattern overuse. The worked example and explicit output format make this immediately actionable while the anti-pattern section adds important guardrails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No explanation of what patterns are conceptually (Claude knows). Every section earns its place with actionable tables, anti-patterns, and the critical 'or maybe just' column that prevents over-engineering. | 3 / 3 |
Actionability | Highly actionable with concrete symptom→pattern mapping table, specific code examples (Java Strategy interface), and a worked example showing the full reasoning process. The output format template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear workflow: identify symptom → match pattern → check 'or maybe just' → apply or reject. The worked example demonstrates this sequence explicitly, and the output format enforces validation via 'When NOT to' section. | 3 / 3 |
Progressive Disclosure | Well-organized single file appropriate for this scope. Clear sections (problem→pattern, anti-patterns, worked example, do not, output format) with logical flow. No need for external references given the focused nature of the skill. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.