CtrlK
BlogDocsLog inGet started
Tessl Logo

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Scale 1-3

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

This is a well-crafted skill that provides clear, actionable guidance for extracting ubiquitous language glossaries. Its strengths are the concrete output format template and opinionated rules that leave little room for ambiguity. The main weakness is mild redundancy between the output format example and the separate example block, plus a few rules that could be tightened.

Suggestions

Remove the duplicate example dialogue — either keep it in the output format template or as a standalone example, but not both, to save tokens.

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some redundancy. The example dialogue appears twice (once in the output format template and once as a separate example), and some rules restate what's already implied by the output format. However, it doesn't over-explain concepts Claude already knows.

2 / 3

Actionability

The skill provides a fully concrete output format with a complete markdown template, specific table structures, explicit rules for term selection, and a clear example of the expected file output. Claude can execute this immediately without ambiguity.

3 / 3

Workflow Clarity

The 5-step process is clearly sequenced, the re-running section provides an explicit update workflow with validation (read existing → incorporate → update → re-flag → rewrite), and the operation is non-destructive (writing a markdown file), so heavy validation checkpoints aren't necessary.

3 / 3

Progressive Disclosure

For a standalone skill with no bundle files, the content is well-organized with clear sections (Process, Output Format, Rules, Re-running) that are appropriately sized. No external references are needed given the skill's scope, and the structure supports easy scanning.

3 / 3

Total

11

/

12

Passed

Description

100%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly articulates specific capabilities (extracting glossaries, flagging ambiguities, proposing canonical terms), specifies the output artifact (UBIQUITOUS_LANGUAGE.md), and provides comprehensive trigger guidance with natural user terms. It occupies a distinct niche in DDD terminology management that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: extract a glossary, flag ambiguities, propose canonical terms, and save to a specific file (UBIQUITOUS_LANGUAGE.md).

3 / 3

Completeness

Clearly answers both 'what' (extract glossary, flag ambiguities, propose canonical terms, save to file) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'domain terms', 'glossary', 'terminology', 'ubiquitous language', 'domain model', 'DDD'. Good coverage of variations a user might naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: DDD-style ubiquitous language glossary extraction is a very specific domain with clear triggers like 'DDD', 'ubiquitous language', and 'domain model' that are unlikely to conflict with other 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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
SnowingFox/ai-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.