design-pattern-suggestor

Recommends appropriate software design patterns based on problem descriptions, requirements, or code scenarios. Use when designing software architecture, refactoring code, solving common design problems, or choosing between design approaches. Analyzes the problem context and suggests suitable creational, structural, behavioral, architectural, or concurrency patterns with implementation guidance and trade-off analysis.

1.14x

Quality

74%

Does it follow best practices?

Impact

92%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/design-pattern-suggestor/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and well-sequenced with genuine offloading to reference files, but it is verbose and padded with template scaffolding, recap lists, and concepts Claude already knows. Tightening would notably improve token efficiency.

Suggestions

Remove the 'Core Capabilities' list and template-placeholder blocks (e.g. '[Reason 1]', '[Benefit 1]'); they restate the workflow and add tokens without executable value.

Consolidate the duplicate Strategy/payment example that appears in both Step 4 and Example 1 into a single canonical instance.

Drop the language-specific interface primers (Python ABC, TypeScript/Java interface syntax) since they explain concepts Claude already knows; keep only non-obvious language idioms.

Dimension	Reasoning	Score
Conciseness	The 435-line body is noticeably verbose: the 'Core Capabilities' recap, template placeholders like '[Reason 1: Matches problem characteristic]', a repeated Strategy/payment example (Step 4 and Example 1), and language-specific interface primers explaining ABC/interfaces Claude already knows all pad the skill.	2 / 5
Actionability	Provides executable Python code, concrete decision trees, a pattern-matching table, and a structured recommendation template, with only minor gaps where output-format scaffolding substitutes for runnable guidance.	4 / 5
Workflow Clarity	A clear 7-step sequence (Understand → Categorize → Decision Trees → Suggest → Alternatives → Combination → Implementation) is present with clarifying-question gating up front; no explicit validation checkpoints, but this advisory skill is neither destructive nor batch so the 3-cap does not apply.	4 / 5
Progressive Disclosure	Body points to two real one-level-deep references (references/selection_guide.md and references/pattern_catalog.md, both verified present) and offloads the bulk catalog there, though a fair amount of decision-tree and table content remains inlined that could live in references.	4 / 5
	Total	14 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: third person, explicit what-and-when, with concrete actions and natural trigger phrases. It is comprehensive and largely distinguishable from sibling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Recommends appropriate software design patterns', 'Analyzes the problem context and suggests suitable creational, structural, behavioral, architectural, or concurrency patterns', and 'implementation guidance and trade-off analysis' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers 'what' (recommends/analyzes/suggests patterns with implementation guidance and trade-off analysis) and 'when' ('Use when designing software architecture, refactoring code...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'designing software architecture', 'refactoring code', 'solving common design problems', and 'choosing between design approaches' are present, but a few common synonyms a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	The design-pattern-suggestion niche is clearly bounded with distinct triggers, though there is minor overlap risk with general architecture or coding-assistant skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/design-pattern-suggestor/SKILL.md
Commit: 4f38503

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.