CtrlK
BlogDocsLog inGet started
Tessl Logo

m09-domain

CRITICAL: Use for domain modeling. Triggers: domain model, DDD, domain-driven design, entity, value object, aggregate, repository pattern, business rules, validation, invariant, 领域模型, 领域驱动设计, 业务规则

62

Quality

78%

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 ./skills/m09-domain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a well-structured, concise decision guide with executable Rust templates and clear trace navigation. Its main limitation is that all templates live inline in a single file rather than being split into a deeper reference.

DimensionReasoningScore

Conciseness

The body is lean throughout — tables, a short thinking prompt, and tight code templates with no padding explaining what DDD or Rust ownership is, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides copy-paste-ready Rust templates for Email, User, and Order plus concept-to-pattern tables, but templates carry placeholder lines ('// ... other fields', '// Enforce aggregate invariants') that are minor gaps short of fully executable, keeping it just below 5.

4 / 5

Workflow Clarity

The Thinking Prompt gives a clear sequenced decision process (identity → invariants → ownership) and Trace Up/Trace Down give navigation, with most decision checkpoints present; it is a reference skill with no destructive steps requiring validation, so it sits just below the explicit-checklist anchor at 5.

4 / 5

Progressive Disclosure

Sections are clearly headed and well-organized with no nested references and no bundle files to navigate, but the ~175-line body is monolithic with all pattern templates inlined where a separate templates reference could offload detail, keeping it just below the ideal split at 5.

4 / 5

Total

17

/

20

Passed

Description

63%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 excels at trigger coverage with comprehensive synonyms and bilingual terms, but its 'what' statement is minimal and lacks concrete actions. Distinctiveness is strong thanks to specialized DDD vocabulary.

Suggestions

Add one or two concrete actions to the description (e.g., 'Map domain concepts to Rust patterns, design aggregates and validated value objects') so the 'what' is specific rather than restating the domain.

Drop the 'CRITICAL:' prefix — it is filler that does not aid triggering and slightly undermines the concise third-person voice.

Consider trimming the broadest terms ('validation', 'business rules') if they risk colliding with other skills, or qualify them with 'domain' to keep triggers distinctive.

DimensionReasoningScore

Specificity

It names the domain ('domain modeling') and lists concept nouns (entity, value object, aggregate) but enumerates no concrete actions or verbs, matching the 'names the domain but actions are minimal or generic' anchor; a 3 would require 1-2 explicit actions which are absent.

2 / 5

Completeness

The 'when' is explicit and well-handled via the Triggers clause, but the 'what' is minimal — 'Use for domain modeling' restates the domain without describing what the skill concretely does, so it falls short of the both-clearly anchor at 4.

3 / 5

Trigger Term Quality

The Triggers list covers natural terms comprehensively with synonyms (DDD / domain-driven design), concept names (entity, value object, aggregate, repository pattern), and Chinese equivalents (领域模型, 领域驱动设计, 业务规则), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Specialized DDD terminology (aggregate, repository pattern, invariant) gives it a clear niche with minimal conflict risk, though broad terms like 'validation' and 'business rules' create minor overlap with adjacent skills, keeping it just below 5.

4 / 5

Total

14

/

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
actionbook/rust-skills
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.