CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rich-domain-builder

Ativado ao definir ou modificar Aggregate Roots, Entities ou Value Objects na camada de domínio, garantindo o encapsulamento correto e evitando modelos anêmicos.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/dotnet-clean-arch/skills/rich-domain-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A compact, well-organized set of project-specific DDD rules whose strongest parts are the concrete constraints (private setters, ValueObject base class, DomainException, spec-*.md as the sole rule source). It is dragged down by textbook DDD definitions Claude already knows, the absence of any complete code example, and the lack of a sequenced define-write-validate workflow with checkpoints.

Suggestions

Drop or compress the textbook definitions of Entities, Value Objects, and Aggregate Roots (items 2–4) to one-line constraints, keeping only project-specific rules like extending the 'ValueObject' base class.

Add one complete example (entity or value object) showing private setters, a business method like 'AlterarStatus(Status status)', and a 'DomainException' throw, so the guidance is executable rather than rule-based.

Restructure the guidance as a short ordered flow — read the 'spec-*.md' file for the entity, define the model with private setters, validate invariants before finishing — so the promised 'definição, escrita e validação' sequence is explicit.

DimensionReasoningScore

Conciseness

Mostly efficient — the numbered rules are short and constraint-focused — but several bullets restate textbook DDD definitions Claude already knows, e.g., 'Objetos com uma identidade única e contínua ao longo do tempo (possuem ID de entidade)' and 'Objetos imutáveis definidos unicamente por seus atributos, sem identidade própria', plus the generic aggregate-root example. This is 'some unnecessary explanation that could be tightened' rather than the noticeably padded level of 2, since the definitions are brief and the rest is project-specific guidance.

3 / 5

Actionability

There is some concrete guidance — '{ get; private set; }', method examples like 'AlterarStatus(Status status)', the 'ValueObject' base class, 'DomainException', and the 'spec-*.md' source of rules — but no complete executable example of an entity, value object, or a DomainException being thrown. The guidance is closer to rules with pseudocode-level hints than copy-paste-ready instruction, matching the 3 anchor ('some concrete guidance but incomplete') and clearly below the mostly-executable level of 4.

3 / 5

Workflow Clarity

The six numbered items are topic categories, not a sequence; although the header promises 'orienta a definição, escrita e validação', there is no ordered flow (e.g., read spec-*.md → define the entity → run invariant checks) and validation appears only as a rule ('Lance uma exceção de domínio') without checkpoints or a verification step. This is not incoherent (so above 2), but checkpoints and sequencing are missing, matching anchor 3.

3 / 5

Progressive Disclosure

The body is under 50 lines, needs no external reference files (none exist in the bundle), and is well organized as a single 'Diretrizes do Domínio' section with six numbered, titled rules — per the simple-skill scoring note this earns the top score without external file references.

5 / 5

Total

14

/

20

Passed

Description

73%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.

A well-scoped, distinct description in third person with an explicit activation condition tied to concrete DDD concepts. Its main weakness is that it states goals (encapsulation, avoiding anemic models) instead of naming the concrete actions the skill performs, keeping specificity and completeness just below top marks.

Suggestions

State the concrete actions the skill performs, e.g., 'Orienta a definição, escrita e validação de entidades de domínio ricas' — this would lift the vague goal-language in 'garantindo o encapsulamento correto' to specific actions.

Add one or two natural trigger variations users might say, such as 'modelo de domínio', 'entidades de domínio', or 'objeto de valor', to broaden natural-language trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Aggregate Roots, Entities ou Value Objects na camada de domínio") and two concrete concerns ("garantindo o encapsulamento correto e evitando modelos anêmicos"), but these are goals rather than a list of specific actions like define/write/validate. It does not list several concrete actions, so it fits the 'names domain and 1-2 concrete actions' anchor rather than 4; it is clearly above the generic-minimal anchor of 2.

3 / 5

Completeness

The 'when' is explicit and specific ("Ativado ao definir ou modificar Aggregate Roots, Entities ou Value Objects na camada de domínio"), and a 'what' is present ("garantindo o encapsulamento correto e evitando modelos anêmicos"), stated in third person as required. However, the 'what' states goals rather than concrete actions (it never says it guides defining, writing, or validating entities), so it does not reach the fully explicit what+when anchor of 5.

4 / 5

Trigger Term Quality

It includes natural terms a DDD user would say: "definir ou modificar", "Aggregate Roots", "Entities", "Value Objects", "camada de domínio", "modelos anêmicos". A few natural variations are missing (e.g., "domain model", "entidades de domínio", Portuguese synonyms like "objetos de valor"), so it falls just short of the comprehensive synonym/extension coverage of 5 but is well above the partial keyword coverage of 3.

4 / 5

Distinctiveness Conflict Risk

The triggers are tightly scoped to the DDD domain-modeling niche ("Aggregate Roots", "Value Objects", "modelos anêmicos", "camada de domínio") — a clear niche with distinct trigger phrases and minimal overlap risk with generic coding skills, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

JoseMD12/testing-tessl

Path

plugins/dotnet-clean-arch/skills/rich-domain-builder/SKILL.md

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.