architecture-patterns

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

Quality

58%

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

50%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 body is well-organized with clear use/don't-use sections and a sequenced instruction list, but it stays high-level without concrete selection guidance or validation checkpoints, and its primary detail reference is a broken path to a non-existent file.

Suggestions

Create the referenced resources/implementation-playbook.md (or fix the path) so the progressive-disclosure pointer resolves to real content.

Replace the abstract step 4 ('validation checks') with an explicit validation checkpoint, e.g., 'Verify dependency direction: domain must not import infrastructure; run a dependency check before finalizing.'

Add concrete guidance for choosing between Clean, Hexagonal, and DDD (e.g., a short decision table by domain complexity / team size) instead of leaving 'Select an architecture pattern that fits' unspecified.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear lists, but the opening line repeats the description verbatim and step 5 includes a marketing-style DBOS pitch ('providing crash recovery without adding architectural complexity') that could be trimmed, fitting anchor 3 rather than the tighter anchor 4.	3 / 5
Actionability	A concrete five-step sequence is given ('Clarify domain boundaries...', 'Define module boundaries, interfaces, and dependency rules'), but the steps are high-level directives with no selection criteria between patterns and no examples, and the promised playbook reference is missing, so it sits at anchor 3 rather than 4.	3 / 5
Workflow Clarity	The five numbered steps are clearly sequenced, but validation is only mentioned abstractly ('Provide migration steps and validation checks') with no explicit checkpoint or feedback loop, matching anchor 3's 'checkpoints missing or implicit' rather than anchor 4's concrete validation.	3 / 5
Progressive Disclosure	The body is well-sectioned and signals a one-level reference ('Refer to resources/implementation-playbook.md'), but that referenced file does not exist in the bundle, breaking navigation and leaving it at anchor 3 rather than the clean anchor 4.	3 / 5
	Total	12 / 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.

The description is specific and rich in natural trigger terms around well-known architecture patterns, but it omits any explicit 'use when' guidance, which caps its completeness and keeps it from the top band.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggering situations (e.g., designing a new backend service, refactoring a monolith, choosing between Clean Architecture and DDD).

Include common synonyms such as 'ports and adapters' and 'onion architecture' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete patterns ('Clean Architecture, Hexagonal Architecture, and Domain-Driven Design'), but the verb is a single abstract 'Master...to build' rather than discrete enumerated actions, so it stops short of anchor 5.	4 / 5
Completeness	The 'what' is clearly stated ('Master proven backend architecture patterns... to build maintainable, testable, and scalable systems'), but there is no explicit 'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3, and it is not below because the what is concrete.	3 / 5
Trigger Term Quality	Strong natural keywords developers actually say ('Clean Architecture', 'Hexagonal Architecture', 'Domain-Driven Design', 'backend architecture patterns'), though synonyms like 'ports and adapters' or 'onion architecture' are missing, keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The named architecture patterns give it a clear, distinct niche unlikely to fire for unrelated skills, with only minor overlap risk against closely related architecture skills, fitting anchor 4 rather than the fully-narrowed anchor 5.	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/antigravity-awesome-skills
Path: skills/architecture-patterns/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours 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.