SKILLEMALL.ai
GitHub ↗ RU Sign in

AB domain-driven-design

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

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 553 tokens Open the sourcegithub.com↗ analyzed 2 d ago

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

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: domain-driven-design (sickn33/agentic-awesome-skills)

The same skill appears in 3 more places: agentic-awesome-skills, agentic-awesome-skills, RA-Skills

How to improve

    For the model run — optional
    • 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

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    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: 88.