CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, actionable, and appropriately pushes detail into real reference files with clear navigation. Minor trimming of the restated opener and the long test fixture would push conciseness higher.

DimensionReasoningScore

Conciseness

The body is largely lean — terse bullet definitions and a focused code example assume Claude's competence — with only minor padding such as the restated opening line "Master proven backend architecture patterns..." and a slightly long in-memory test fixture.

4 / 5

Actionability

Provides a complete, copy-paste-ready Python test example and concrete remediation rules (e.g. "use_cases/ imports only from domain/", "Create a separate ORM model... in adapters/repositories/"), with the only gap being that full project scaffolding is deferred to references rather than shown inline.

4 / 5

Workflow Clarity

"When to Use" scenarios plus troubleshooting entries that name a symptom and prescribe a fix give a clear sequenced guide; the skill is design-time rather than a destructive/batch operation, so the absence of a strict validate-fix-retry loop is acceptable and only minor checkpoint detail is missing.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with clearly signaled one-level-deep references — "Detailed pattern documentation lives in `references/details.md`" and "see: [`references/advanced-patterns.md`](references/advanced-patterns.md)" — both of which resolve to real bundle files, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

92%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 concrete, third-person, and answers both what the skill does and when to invoke it, with multiple specific trigger scenarios. Its only mild gap is trigger-term breadth (technical vocabulary dominates, few synonyms).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Implement proven backend architecture patterns", "designing clean architecture for a new microservice", "refactoring a monolith to use bounded contexts", "debugging dependency cycles" — giving comprehensive coverage of the domain's actionable verbs.

5 / 5

Completeness

Explicitly answers both "what" ("Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design") and "when" via a concrete "Use this skill when..." clause listing four trigger scenarios.

5 / 5

Trigger Term Quality

Natural phrases like "clean architecture", "new microservice", "refactoring a monolith", "bounded contexts", and "dependency cycles" are strong, but the vocabulary leans technical with few synonyms or casual variants a user might say, so it is a notch below fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — backend layering/DDD patterns with distinct triggers like "dependency cycles between application layers" — making it unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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
wshobson/agents
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.