AB domain-driven-design
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.
The skill promises to route Domain-Driven Design work from strategic modeling through tactical implementation to event-driven architecture patterns. Two files in the package, no critical errors, linter clean. Quality score 91, process score 70—structure holds, but documentation or examples may lack depth.
No model runs recorded, sandbox untested. Works across all major platforms from Claude to DeepSeek. If you already know DDD and need a task organization template, it fits. If you're looking for interactive guidance or code examples, skip it.
Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 553 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.