Name: domain-driven-design
Rating: 57.599999999999994 (1 reviews)
Author: administrakt0r

domain-driven-design

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

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/domain-driven-design/SKILL.md

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

Quality

Content

75%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 content is a concise, well-structured routing skill that provides concrete actionable guidance and a clear sequenced workflow with a real one-level-deep reference file, with only minor gaps in validation feedback loops and reference signaling.

Suggestions

Add an explicit validate/retry loop for produced artifacts (e.g., confirm the ubiquitous-language glossary covers all invariants before routing to tactical patterns).

Convert the reference pointer to a markdown link (e.g., 'open [references/ddd-deliverables.md](references/ddd-deliverables.md)') for clearer navigation.

Tighten the small redundancy between the four-step Instructions list and the Viability check / Routing map subsections.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-driven prose that assumes Claude knows DDD concepts (no explanation of bounded contexts or aggregates), with only minor tightenable redundancy between the Instructions list and subsequent sections, matching anchor 4.	4 / 5
Actionability	Concrete, specific guidance is provided via the routing map with exact @skill handles, a two-of-four viability gate, and a deliverables checklist in the reference; it is instruction-only but actionable with minor gaps, matching anchor 4.	4 / 5
Workflow Clarity	A clear numbered sequence (viability check -> strategic artifacts -> route -> success criteria) with checkpoints (viability gate, success evidence) is present; not a 5 because explicit validation/feedback loops on outputs are only weakly specified, matching anchor 4.	4 / 5
Progressive Disclosure	A well-organized overview references a real one-level-deep bundle file (references/ddd-deliverables.md) that exists on disk; not a 5 because the reference is signaled with a backtick path rather than a clear markdown link and navigation could be more explicit, matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

58%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 what the skill does with several concrete DDD actions and a distinct niche, but lacks an explicit 'Use when...' trigger clause and omits common synonyms (DDD, bounded context), capping completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when modeling a complex business domain with explicit boundaries or planning CQRS, event sourcing, or sagas').

Include common user synonyms such as 'DDD', 'domain modeling', and 'bounded context' to broaden trigger coverage.

Consider enumerating the distinct sub-actions (strategic modeling, tactical patterns, evented architecture) so specificity reaches a comprehensive list.

Dimension	Reasoning	Score
Specificity	Names the DDD domain and several concrete actions ('Plan and route', 'strategic modeling', 'tactical implementation', 'evented architecture patterns'), matching anchor 4; not a 5 because it is a single sentence rather than a comprehensive enumerated action list.	4 / 5
Completeness	A clear 'what' is present ('Plan and route Domain-Driven Design work...') but there is no explicit 'when'/'Use when...' trigger clause; per the guidelines a missing Use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	'Domain-Driven Design' is a natural user phrase, but common synonyms/abbreviations users say (DDD, domain modeling, bounded context) are absent, matching anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	DDD is a clear niche with distinct triggers and minimal conflict risk, but 'plan and route ... work' has minor overlap with general architecture/planning skills, placing it at anchor 4 rather than 5.	4 / 5
	Total	14 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/domain-driven-design/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.