CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

domain-modeling

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

Quality

74%

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 ./.claude/cloud-profile/skills/domain-modeling/SKILL.md

The canonical home for this skill is domain-modeling in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 an efficient, well-organized set of during-session heuristics with genuinely useful example phrasings and a disciplined ADR gate. Its main defect is that both of its format references dangle — CONTEXT-FORMAT.md and ADR-FORMAT.md do not exist — which degrades actionability and leaves the progressive-disclosure structure unverifiable.

Suggestions

Create CONTEXT-FORMAT.md and ADR-FORMAT.md (or inline their formats into SKILL.md) so the instructions 'Use the format in [CONTEXT-FORMAT.md]' and 'Use the format in [ADR-FORMAT.md]' resolve to real content — as written, a session cannot execute the record/update steps.

Add a brief explicit ordering of the session moves (challenge → sharpen → cross-reference with code → record resolved term → evaluate ADR gate) so the flow reads as a sequence rather than parallel heuristics.

Trim the two ASCII directory trees to a single compact example (e.g. show the multi-context layout only, and describe the single-context case in one line) to cut ~10 lines of visual bulk.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — terse sections, illustrative one-line dialogue quotes, a crisp three-condition ADR test — with every token earning its place. Falls short of 5 because the two full ASCII directory trees (~25 lines) and the meta-parenthetical distinguishing this skill from passive CONTEXT.md reading could be compressed without losing guidance.

4 / 5

Actionability

The conversational moves are concrete ("Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"), but the operative formatting guidance is delegated to "Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md)" and "[ADR-FORMAT.md](./ADR-FORMAT.md)" — files that do not exist in the bundle. That leaves key execution details missing, matching the anchor for incomplete concrete guidance rather than the mostly-executable level above.

3 / 5

Workflow Clarity

Each move has an explicit trigger condition ("When the user uses a term that conflicts...", "When a term is resolved...") plus lazy-creation rules for CONTEXT.md and docs/adr/, giving a discernible detect → challenge → resolve → record flow. Not 5 because the moves are presented as parallel heuristics with no explicit ordering or checkpoint tying them together, and the record step is undercut by the missing format files.

4 / 5

Progressive Disclosure

References are well-signaled one-level-deep links and the body is sensibly sectioned, but both referenced files (CONTEXT-FORMAT.md, ADR-FORMAT.md) are absent from the bundle — there is no references/, scripts/, or assets/ directory at all. Navigation to the detailed material fails outright, so the disclosure structure is present on paper but broken in fact, fitting the mid anchor rather than the well-placed level above.

3 / 5

Total

14

/

20

Passed

Description

75%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-formed description with a proper third-person what-clause and an explicit multi-condition Use-when trigger covering user- and skill-initiated cases. It sits just below the top anchors on every dimension due to minor gaps: no artifact-level vocabulary (glossary, ADR) and a thin what-clause.

DimensionReasoningScore

Specificity

"Build and sharpen a project's domain model", "pin down domain terminology or a ubiquitous language", "record an architectural decision", "maintain the domain model" list several concrete actions in a named domain. Falls short of the 5 anchor because coverage has minor gaps — it never names the concrete artifacts (glossary/CONTEXT.md, ADRs) the skill actually produces.

4 / 5

Completeness

Both halves are explicit: the what ("Build and sharpen a project's domain model") and a three-clause "Use when..." covering terminology, decisions, and skill-to-skill invocation. Not 5 because the what-clause is a single terse sentence that doesn't preview the skill's concrete capabilities, leaving the when-clause carrying the detail.

4 / 5

Trigger Term Quality

Natural phrases like "domain model", "domain terminology", "ubiquitous language", and "record an architectural decision" match what users would actually say. Not the 5 anchor because common synonyms are missing — users would plausibly say "glossary", "write an ADR", or "ubiquitous language" as the standalone term "ADR" is absent.

4 / 5

Distinctiveness Conflict Risk

Domain modeling is a clear niche ("ubiquitous language", "record an architectural decision") that most skills would not claim. Not 5 because "record an architectural decision" overlaps with a hypothetical dedicated ADR-writing skill, and "maintain the domain model" is broad enough to collide with general documentation skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/domain-modeling/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.