CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ubiquitous-language

Builds a project glossary that maps everyday wording to canonical terms, repository actions, and reusable engineering rules. Use when a user asks "what does X mean here?", "define our terms", "standardize this naming", "turn this phrase into a repo action", "grill the domain language", or whether a local correction should apply to similar code.

Quality

80%

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/agent-ops/ubiquitous-language/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, largely actionable instruction skill with genuine one-level-deep progressive disclosure and an explicit validation section with fail-fast behavior. Its main costs are redundancy across sections and a confusing project-specific worked example that pads the body without adding executable guidance.

Suggestions

Collapse "Outputs" into the Workflow and drop the "Term Rules" entries already covered by references/output-format.md's Quality Bar to cut duplicated tokens.

Replace the leaked project snippet in the worked glossary example with a generic, self-contained translation example so it instructs rather than confuses.

Convert the directory-level pointer "Local contract, evals, and task profile: `references/`" into named links (e.g., references/contract.yaml, references/evals.yaml, references/task-profile.json).

DimensionReasoningScore

Conciseness

The body is dense and free of concept explanations Claude already knows, but it could be tightened: the "Outputs" section duplicates Workflow step 9, "Term Rules" repeats the quality bar already in references/output-format.md, "When to use" re-derives the frontmatter triggers, and Gotchas overlaps Failure Mode and Corrective Feedback Mode. That puts it at "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the lean anchor of 5 or the noticeably-padded anchor of 2.

3 / 5

Actionability

As an instruction-only skill it gives mostly concrete guidance: two worked examples with exact output shapes, enumerated classifications (line/function/file/package/repository/architecture_rule/durable_memory), and named disposition options (align now, different semantics, defer with reason, not applicable). Minor gaps keep it below fully-executable: "nearest active agent instruction surface" is undefined, and the worked glossary example embeds a confusing project-specific snippet ("SDK-checked private Tessl version or verified OpenAI-provider exemption") that reads as leaked context rather than instruction.

4 / 5

Workflow Clarity

The 9-step Workflow is clearly sequenced (scope → resolve glossary → read existing → extract → correct → choose terms → write → pointer → report), and the Validation section supplies explicit gates with a fail-fast loop ("stop at the first failed gate and do not proceed until the blocker is fixed") plus a Failure Mode stop condition. It sits just below anchor 5 because the steps themselves are terse and some checkpoints (e.g., how to detect an ambiguous multi-context situation) are implicit rather than stated as validation steps inside the workflow.

4 / 5

Progressive Disclosure

The structure is good: the body is an overview and the deep material (output template, grill procedure, contract, evals, task profile) lives one level deep in references/output-format.md and references/domain-grill.md, both of which exist and are clearly linked from the body. Minor gaps: the inlined worked-glossary example is detail that could live in output-format.md, and the bare pointer "Local contract, evals, and task profile: `references/`" is a vague directory reference rather than a signaled link.

4 / 5

Total

15

/

20

Passed

Description

83%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: third-person, concrete about what the skill builds, and paired with an explicit Use-when clause full of natural quoted trigger phrases. Its only weaknesses are summary-level action detail and slight trigger overlap with rename/refactor and code-review requests.

Suggestions

Enumerate one or two more concrete operations (e.g., 'extracts domain nouns and lifecycle states from source and tests') to lift specificity toward comprehensive coverage.

Add a clarifying trigger variation such as 'build or update a glossary' and 'what does this word mean in this repo' to widen natural-term coverage.

Sharpen the rename/refactor boundary (e.g., 'for reusable terminology decisions, not one-off symbol renaming') to reduce overlap with rename and code-review skills.

DimensionReasoningScore

Specificity

The description states a concrete capability in third person — "Builds a project glossary that maps everyday wording to canonical terms, repository actions, and reusable engineering rules" — naming the domain and several specific actions. It stops short of anchor 5 because the actions (canonical terms, aliases, repository actions, engineering rules) are described at a summary level rather than a comprehensive list of concrete operations.

4 / 5

Completeness

Both halves are explicit: the "what" is the opening sentence (builds a glossary mapping everyday wording to canonical terms, repo actions, and engineering rules), and the "when" is an explicit "Use when..." clause with concrete quoted trigger phrases. This matches the anchor that clearly answers both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It quotes natural user phrasings — "what does X mean here?", "define our terms", "standardize this naming", "turn this phrase into a repo action", "grill the domain language" — which users would genuinely say. A few natural variations are missing (e.g., "glossary", "what does this word mean", "naming conventions"), so it falls just below the comprehensive-synonyms anchor of 5 and clearly above the sparse keyword coverage of 3.

4 / 5

Distinctiveness Conflict Risk

The glossary/ubiquitous-language niche is well staked out with distinct triggers like "grill the domain language" and "turn this phrase into a repo action". Minor overlap risk remains: "standardize this naming" could also match a rename/refactor request, and "whether a local correction should apply to similar code" borders on code-review territory, keeping it below the minimal-conflict anchor of 5.

4 / 5

Total

17

/

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

jscraik/Agent-Skills

Path

Skills/agent-ops/ubiquitous-language/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.