CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/architecture-patterns/skills/architecture-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 skill delivers substantial executable code across all three patterns but spends tokens re-teaching concepts Claude already knows and lacks a sequenced application workflow. Organization is good for a single-file reference.

Suggestions

Remove or condense the Core Concepts section that re-explains layer/component definitions Claude already knows, keeping only non-obvious guidance.

Add a short sequenced 'how to apply' workflow (e.g., identify bounded contexts, define ports, implement adapters) with explicit checkpoints so the skill reads as procedural guidance rather than only a catalog.

Define or stub the referenced-but-undefined classes (CreateUserResponse, Order, OrderResult, domain events) so the code examples are fully copy-paste runnable.

DimensionReasoningScore

Conciseness

The Core Concepts section re-explains Clean/Hexagonal/DDD layering and terminology Claude already knows, adding padding; the code is efficient but the conceptual prose could be trimmed.

3 / 5

Actionability

Provides concrete, executable Python for entities, use cases, repositories, value objects and aggregates, with only minor gaps such as undefined helper classes (CreateUserResponse, Order).

4 / 5

Workflow Clarity

Content is a topical pattern catalog with no sequenced multi-step workflow or validation checkpoints; while no destructive/batch validation cap applies, procedural sequencing is absent.

3 / 5

Progressive Disclosure

Single well-organized file with clear sections and no nested references; for a no-bundle skill this is good structure with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

82%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.

A strong, well-formed description that clearly answers what and when with concrete, natural trigger terms. Its main weakness is specificity, where the action verbs are limited even though the named patterns are concrete.

DimensionReasoningScore

Specificity

Names three concrete patterns (Clean, Hexagonal, DDD) but the verbs are limited to 'Implement' and 'refactoring', leaving the action coverage incomplete rather than comprehensive.

3 / 5

Completeness

Explicitly states both what it does ('Implement proven backend architecture patterns including...') and when to use it ('Use when architecting complex backend systems or refactoring...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('architecting complex backend systems', 'refactoring', named pattern names), with good coverage though a few natural synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The three named architecture patterns form a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.