CtrlK
BlogDocsLog inGet started
Tessl Logo

domain-driven-design

Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/domain-driven-design/SKILL.md

The canonical home for this skill is domain-driven-design in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a lean, well-structured routing skill with concrete skill pointers, a gating viability check, and a properly disclosed one-level reference file. Main improvement would be adding explicit validation/feedback checkpoints after routing decisions.

DimensionReasoningScore

Conciseness

Lean ~65-line body that assumes Claude's DDD competence with no padded concept explanations; every section earns its place.

5 / 5

Actionability

Concrete routing map of named skills, explicit viability criteria (two-of-four), and a specific output checklist provide mostly executable guidance, though it routes rather than supplies direct implementation steps.

4 / 5

Workflow Clarity

A clear four-step sequence with a viability-check gate and explicit pass criteria, plus defined output requirements; minor validation gaps keep it just below a 5.

4 / 5

Progressive Disclosure

Overview body points to a single, clearly signaled, one-level-deep reference (references/ddd-deliverables.md, verified to exist) with well-organized sections and easy navigation.

5 / 5

Total

18

/

20

Passed

Description

70%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 clearly conveys a distinct DDD niche with several concrete staged actions, but it lacks an explicit 'Use when...' trigger clause and omits common synonyms like 'DDD' and 'bounded context'. Adding trigger phrases and synonyms would raise completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause listing concrete user triggers (e.g., modeling bounded contexts, deciding on CQRS/event sourcing, multi-team domain collisions).

Add common synonyms and abbreviations users actually say — 'DDD', 'bounded context', 'event sourcing', 'sagas' — to broaden trigger-term coverage.

Tighten 'plan and route' into more concrete verbs (e.g., 'model subdomains, map bounded contexts, route to tactical and evented implementation skills').

DimensionReasoningScore

Specificity

Names the DDD domain plus several concrete actions ('strategic modeling', 'tactical implementation', 'evented architecture patterns') but 'plan and route' is somewhat high-level rather than fully concrete operations.

4 / 5

Completeness

A clear 'what' is present (plan and route DDD work across the three stages) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords ('Domain-Driven Design', 'strategic modeling', 'tactical implementation', 'evented architecture'), but missing common synonyms users say such as 'DDD', 'bounded context', and 'event sourcing'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Domain-Driven Design across strategic, tactical, and evented stages) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.