CtrlK
BlogDocsLog inGet started
Tessl Logo

ubiquitous-language

从当前对话提取 DDD 风格的 ubiquitous language glossary,标记歧义并提出标准术语。保存到 UBIQUITOUS_LANGUAGE.md。适用于用户想定义领域术语、构建词汇表、收紧术语、创建通用语言,或提到 “domain model” / “DDD” 时。

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-structured skill body with a concrete output template and clear workflows. The main weakness is token efficiency: a redundant second dialogue example and a verbose rules list could be trimmed.

Suggestions

Remove the standalone <example> dialogue block (or the one inside the Output Format template) — two near-identical dialogue examples are redundant; one suffices to demonstrate the pattern.

Tighten the 9-item Rules list by merging related bullets (e.g., the 'Only include domain terms' and 'Only include terms relevant for domain experts' rules overlap) to reduce tokens.

The Output Format example glossary is lengthy; consider trimming it to a minimal schema-defining example and letting Claude fill in real terms from the conversation.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but it carries two near-duplicate dialogue examples (one embedded in the Output Format template and a second in the <example> block) plus a 9-item rules list that could be tightened; this matches 'mostly efficient but could be tightened' rather than every token earning its place.

2 / 3

Actionability

It provides a concrete, copy-paste-ready markdown template with exact table columns (Term / Definition / Aliases to avoid), explicit opinionated rules, and a re-running procedure — fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

A clear numbered Process (Scan → Identify problems → Propose → Write → Summarize) plus a separate Re-running sequence, with the 'Identify problems' step acting as an inline check; the task is a non-destructive single-file write so the absence of an explicit validate-fix loop does not cap the score.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is self-contained; content is well-organized into clear sections (Process, Output Format, Rules, Re-running) with no nested references, which is appropriate for a single-purpose skill.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that states concrete capabilities and gives explicit trigger guidance in a distinct niche. It uses third-person voice with no over-claims or fluff.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '提取...glossary,标记歧义...提出标准术语...保存到 UBIQUITOUS_LANGUAGE.md' — matching the anchor for several specific concrete actions; it is not merely naming a domain with some actions.

3 / 3

Completeness

It explicitly answers both 'what' (extract, mark ambiguity, propose terms, save to file) and 'when' via an explicit '适用于...' trigger clause, so it is not capped at 2 for a missing Use-when clause.

3 / 3

Trigger Term Quality

It covers natural trigger phrasings a user would say — '定义领域术语、构建词汇表、收紧术语、创建通用语言' plus the English 'domain model' / 'DDD' — giving good coverage of common variations rather than jargon-only.

3 / 3

Distinctiveness Conflict Risk

The DDD ubiquitous-language glossary niche with explicit 'domain model' / 'DDD' triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vinvcn/mattpocock-skills-zh-CN
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.