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

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

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

The body is a concise, well-structured set of DDD rich-model guidelines with concrete anchors (setter patterns, method examples, exception type, spec-file sourcing), though it could be more actionable by replacing a few abstract directives with explicit patterns and trimming light concept re-explanations.

Suggestions

Replace abstract directives like 'Controle a consistência' and 'Execute as validações' with concrete patterns (e.g., a short invariant-check method example and the exact DomainException throw signature).

Trim the definitional re-explanations of Entity and Value Object to one line each, since Claude already knows these DDD primitives.

Dimension	Reasoning	Score
Conciseness	The body is lean and largely assumes Claude's DDD knowledge, but it mildly over-explains concepts Claude already knows (e.g. 'Objetos com uma identidade única e contínua', 'Objetos imutáveis definidos unicamente por seus atributos') that could be trimmed.	4 / 5
Actionability	Guidance includes concrete specifics (private setters '{ get; private set; }', method examples like 'AlterarStatus', 'DomainException', extracting rules from 'spec-*.md'), but several directives remain abstract ('Controle a consistência', 'Execute as validações') with no executable code or exact patterns.	3 / 5
Workflow Clarity	As a single-purpose guidance skill with no destructive or batch operation, its parallel guidelines are clearly organized into a numbered structure; it lacks explicit validation checkpoints, but none are required for this non-fragile, non-batch context.	4 / 5
Progressive Disclosure	The skill is under 50 lines, requires no external references (none of references/, scripts/, or assets/ exist), and is organized into well-labeled numbered sections, meeting the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

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

The description provides a clear, third-person trigger condition tied to DDD domain modeling and a distinct niche, but it is stronger on 'when' than on 'what' and relies on technical jargon rather than natural user phrasing.

Suggestions

Add an explicit 'what' clause listing the concrete actions the skill performs (e.g., 'Define estruturas de domínio, encapsula estado via métodos de negócio e valida invariantes') before the 'when' trigger.

Broaden trigger terms with natural-language synonyms a user might say (e.g., 'entidade de domínio', 'modelo rico', 'DDD', 'anemic model') alongside the technical DDD vocabulary.

Dimension	Reasoning	Score
Specificity	Names the DDD domain layer and the concrete actions 'definir ou modificar Aggregate Roots, Entities ou Value Objects' plus the outcome 'garantindo o encapsulamento correto e evitando modelos anêmicos', but coverage is limited to a single trigger action rather than several specific capabilities.	3 / 5
Completeness	It gives a clear 'when' trigger ('Ativado ao definir ou modificar...') but the 'what' is only weakly implied (ensuring encapsulation, avoiding anemic models) rather than an explicit statement of the concrete actions the skill performs.	3 / 5
Trigger Term Quality	Relevant keywords are present ('Aggregate Roots', 'Entities', 'Value Objects', 'camada de domínio', 'modelos anêmicos') but these are technical DDD jargon rather than the natural phrases a user would say, and common synonyms or variations are missing.	3 / 5
Distinctiveness Conflict Risk	The trigger is clearly niched to DDD domain-layer modeling (aggregate roots, entities, value objects), making overlap with unrelated skills low, though the phrasing could be more concrete to fully minimize conflict risk.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 1cbe5bc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.