m09-domain
CRITICAL: Use for domain modeling. Triggers: domain model, DDD, domain-driven design, entity, value object, aggregate, repository pattern, business rules, validation, invariant, 领域模型, 领域驱动设计, 业务规则
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 excels at trigger term coverage with comprehensive DDD terminology including Chinese translations, making it highly discoverable. However, it reads more like a keyword list than a capability description - it tells Claude when to use the skill but not what actions the skill enables. Adding concrete actions would significantly improve its utility.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Designs domain models, defines aggregates and entities, implements repository patterns, enforces business invariants'
Restructure to separate capabilities from triggers: start with what it does, then list 'Use when...' triggers
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (domain modeling, DDD) and mentions concepts like entity, value object, aggregate, repository pattern, but doesn't describe concrete actions the skill performs (e.g., 'creates domain models', 'validates business rules'). | 2 / 3 |
Completeness | Has a 'Use for' clause indicating when to use it (domain modeling) and lists triggers, but lacks explicit description of WHAT the skill actually does - it only lists concepts/keywords without describing capabilities or actions. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms including 'domain model', 'DDD', 'domain-driven design', 'entity', 'value object', 'aggregate', 'repository pattern', 'business rules', 'validation', 'invariant', plus Chinese translations for international users. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche with DDD-specific terminology (aggregate, value object, invariant, repository pattern) that clearly distinguishes it from general coding or architecture skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently maps DDD concepts to Rust patterns. It provides actionable code templates, clear decision workflows, and well-organized cross-references without any unnecessary explanation of basic concepts. The tables and code examples are immediately usable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code snippets without explaining concepts Claude already knows. Every section adds value without padding or unnecessary context about what DDD is. | 3 / 3 |
Actionability | Provides fully executable Rust code templates for Value Objects, Entities, and Aggregates. The pattern templates are copy-paste ready with proper validation and identity equality implementations. | 3 / 3 |
Workflow Clarity | The 'Thinking Prompt' section provides a clear decision sequence (identity → invariants → ownership) for modeling choices. The trace up/down sections create explicit navigation paths for different scenarios. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from concepts to patterns to templates. References to related skills (m01-ownership, m05-type-driven, domain-*) are one level deep and clearly signaled in tables. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.