domain-modeling

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, or when another skill needs to maintain the domain model.

Quality

78%

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 ./.agents/skills/domain-modeling/SKILL.md

Quality

Content

75%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-structured instruction skill with concrete example phrasing and clear file-structure guidance. Its main weakness is the dangling reference to a CONTEXT-FORMAT.md file that is neither linked nor present in the bundle, leaving the format unspecified.

Suggestions

Inline a short example of the CONTEXT.md glossary format (or add the file to the bundle and link it) so the 'update inline' step is fully actionable instead of pointing at an absent file.

Add an explicit verification checkpoint after capturing a term, e.g. re-reading CONTEXT.md to confirm the entry is unambiguous and not duplicating an existing definition.

Convert the raw path '.agents/skills/domain-modeling/CONTEXT-FORMAT.md' into a markdown link so the reference is clearly signaled for navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean, avoids explaining what a domain model is, and gives every section a job; the only mild over-explanation is the parenthetical distinguishing "active" modeling from passively reading CONTEXT.md, which could be trimmed, keeping it just below the lean-5 bar.	4 / 5
Actionability	Concrete example phrases (e.g. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?") and specific file paths make the guidance mostly executable; the gap is that the referenced CONTEXT-FORMAT.md content is not shown inline and the file is absent from the bundle.	4 / 5
Workflow Clarity	The session behaviors (challenge → sharpen → discuss → cross-reference → update inline) are clearly sequenced with a lazy-creation rule for files; it stays at 4 rather than 5 because there are no explicit validation/verification checkpoints for confirming a resolved term is correctly captured.	4 / 5
Progressive Disclosure	Sections are well-organized and the skill is near the simple/short threshold where good structure alone can earn a 5, but the single external reference (CONTEXT-FORMAT.md) is signaled by raw path with no link and the file is missing from the bundle, a minor navigation gap that drops it to 4.	4 / 5
	Total	16 / 20 Passed

Description

82%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 strong description that clearly states both purpose and trigger conditions in third person. Its only weakness is that the stated actions (build, sharpen) are somewhat abstract rather than enumerating concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Build and sharpen a project's domain model" names the domain plus two actions (build, sharpen), but the actions are abstract rather than concrete operations, matching the 1-2-action anchor and not reaching the several-specific-actions bar of 4.	3 / 5
Completeness	It explicitly answers both what ("Build and sharpen a project's domain model") and when ("Use when the user wants to pin down domain terminology or a ubiquitous language, or when another skill needs to maintain the domain model") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural user phrases like "pin down domain terminology", "ubiquitous language", and "maintain the domain model" give good keyword coverage; it falls short of 5 only because common synonyms and concrete file/format triggers are absent.	4 / 5
Distinctiveness Conflict Risk	The domain-modeling niche is clearly delimited with distinct triggers (ubiquitous language, domain terminology) and minimal overlap with unrelated skills, matching the clear-niche anchor.	5 / 5
	Total	17 / 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: windmill-labs/windmill
Path: .agents/skills/domain-modeling/SKILL.md
Commit: 7915540

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.