Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is lean and demonstrates its rules with concrete Go code, but it is undermined by a dangling reference: DDD-RULES.md is cited as holding 'all aggregate design rules' yet is not in the bundle, and the code examples rely on helpers only that file would define. There is also no explicit step sequence for designing an aggregate, leaving the workflow implicit.
Suggestions
Add the missing DDD-RULES.md to the skill bundle (e.g., under references/), or inline the essential rules into SKILL.md — the current link points to a file that does not exist, breaking the skill's progressive-disclosure structure.
Define or inline the supporting pieces used by the code examples (eventRegister, addEvent, applayer.NewEvent, ErrEmptyOrder) so the patterns are copy-paste ready rather than depending on the missing rules file.
Add a short ordered workflow for designing a new aggregate (e.g., 1. identify invariants, 2. define factory with validation, 3. add actionable methods that record events, 4. implement Export) to make the sequence explicit instead of implied by example ordering.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is compact with no padding explaining concepts Claude already knows, and the Go examples are tight. It drops below 5 because the opening line ('Design and implement rich domain aggregates with proper encapsulation, domain events, and the Export pattern') and the 'When to Use This Skill' section substantially restate the frontmatter description, which could be trimmed. | 4 / 5 |
Actionability | Three concrete, mostly executable Go examples (NewOrder factory, Ship method, Export) directly demonstrate the stated rules. It is not a 5 because the examples depend on undefined helpers (eventRegister, addEvent, applayer.NewEvent) and the 'read DDD-RULES.md for all aggregate design rules' pointer leads to a file that is missing from the bundle, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The five core rules and ordered pattern examples imply a rough design sequence (factory → actions → events → Export), but there is no explicit sequenced workflow or checkpoints for designing an aggregate (e.g., identify invariants first, then factory, then methods). This matches the 'sequence present but checkpoints missing or implicit' anchor rather than the well-checkpointed anchor 4. | 3 / 5 |
Progressive Disclosure | The body defers all detailed rules to '[DDD-RULES.md](DDD-RULES.md)' — clearly signaled and one level deep — but no references/, scripts/, or assets/ directories exist and DDD-RULES.md is absent from the bundle, so the referenced path is broken and the deferred content is unreachable. Effectively the skill's substance lives in a file that isn't shipped, which matches the anchor-2 failure ('content that clearly belongs in separate files is inlined; or references are buried' — here the inverse: referenced but missing) rather than a 3 where structure is merely suboptimal. | 2 / 5 |
Total | 13 / 20 Passed |