Tessl • The management layer for AI agent skills

SkillPublic

architecture-patterns

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/architecture-patterns/SKILL.md

Quality

Content

38%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 has a clear section structure (use/don't-use triggers, instructions, related skills, limitations) but is effectively a stub: every instruction is an abstract directive and all detailed content is delegated to `resources/implementation-playbook.md`, which does not exist in the bundle. Duplicated text (verbatim description intro, repeated reference) and boilerplate limitations add tokens without value.

Suggestions

Fix the broken reference: either create `resources/implementation-playbook.md` with the promised patterns, checklists, and templates, or inline the essential decision guidance directly in SKILL.md.

Make instructions executable — e.g. give concrete criteria for choosing between Clean/Hexagonal/DDD (team size, domain complexity, coupling pain points) and a sample dependency-rule or module-boundary example instead of 'Select an architecture pattern that fits the domain complexity.'

Remove redundancy: drop the verbatim repetition of the frontmatter description in the intro, state the playbook reference once, and trim the generic Limitations boilerplate.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's knowledge of the patterns, but it opens by duplicating the frontmatter description verbatim, states the same playbook reference twice (in Instructions and Resources), and closes with generic boilerplate limitations ('Do not treat the output as a substitute for environment-specific validation, testing, or expert review').	3 / 5
Actionability	Every instruction is a one-line abstract directive — 'Select an architecture pattern that fits the domain complexity', 'Define module boundaries, interfaces, and dependency rules' — with no decision criteria, examples, checklists, or code that would let Claude actually execute; step 5 packs real guidance ('compare transactions/outbox, explicit sagas and a suitable durable-execution framework') into vague high-level hints.	2 / 5
Workflow Clarity	The five numbered steps give a rough sequence (clarify → select → define → migrate → compare durability options) and step 4 mentions 'validation checks', but no explicit checkpoints or feedback loops are defined, and 'Provide migration steps and validation checks' delegates the actual validation away.	3 / 5
Progressive Disclosure	The body defers all depth — 'Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates' — but no bundle files exist at all (no references/, scripts/, assets/, or resources/ directories), so the sole reference is a broken pointer and the skill has no content behind its overview; the reference is also repeated in two sections.	2 / 5
	Total	10 / 20 Passed

Description

66%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 specific, third-person description that clearly identifies its domain through named architecture patterns and quality goals. Its main weakness is the complete absence of any 'when to use' trigger clause, and its action verbs are generic ('Master ... to build') rather than describing concrete capabilities.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or refactoring backend systems, or when the user mentions Clean Architecture, Hexagonal Architecture, DDD, or layered/onion architecture.'

Replace the generic verb 'Master' with concrete capabilities such as 'Designs and applies Clean Architecture, Hexagonal Architecture, and DDD to define module boundaries, dependency rules, and migration plans.'

Include common synonyms users actually say (DDD, onion architecture, ports and adapters, microservices decomposition) to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names concrete subject matter — 'Clean Architecture, Hexagonal Architecture, and Domain-Driven Design' — plus explicit quality goals ('maintainable, testable, and scalable'), but the action verb 'Master ... to build' is generic rather than a concrete capability.	4 / 5
Completeness	The 'what' is clear (master backend architecture patterns to build maintainable, testable, scalable systems) but there is no 'Use when...' clause or any explicit trigger guidance, capping completeness at 3.	3 / 5
Trigger Term Quality	Good natural keywords ('Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend architecture patterns') that users would plausibly say, though common synonyms like 'DDD', 'onion architecture', 'ports and adapters', and 'microservices' are missing.	4 / 5
Distinctiveness Conflict Risk	The three named patterns are distinctive triggers within a clear niche, but the broad 'backend architecture ... scalable systems' framing creates minor overlap risk with closely related architecture and system-design skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/architecture-patterns/SKILL.md
Revision: 8aa4123

Reviewed: 9 days ago

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.

architecture-patterns

Table of Contents

Is this your skill?