CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

domain-analysis

Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).

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 ./packages/skills-catalog/skills/(architecture)/domain-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers a genuinely actionable six-phase analysis method with concrete patterns, a cohesion formula, and complete output templates. However, it is noticeably verbose — it teaches DDD fundamentals Claude already knows and duplicates its own decision trees and cohesion guidance — and it makes no use of progressive disclosure, inlining ~435 lines of content that belongs partly in reference files.

Suggestions

Trim or remove the conceptual DDD explanations (Bounded Context definition, subdomain definitions, the six integration patterns) — Claude already knows DDD Strategic Design; keep only the skill's own heuristics and scoring rubric.

Eliminate duplication: the subdomain decision tree appears in Phase 3 and again in Quick Reference, and the cohesion quick-check repeats Phase 4 indicators; keep one canonical copy.

Move the three output-format templates, the DDD integration-pattern reference, and the cohesion scoring detail into references/ files (e.g. references/output-formats.md) and keep SKILL.md as a lean overview with well-signaled links, converting the ~435-line monolith into progressive disclosure.

DimensionReasoningScore

Conciseness

The ~435-line body explains standard DDD theory Claude already knows (the bounded context definition, the six integration patterns like Shared Kernel and Anti-corruption Layer), duplicates the subdomain decision tree in both Phase 3 and Quick Reference, repeats cohesion indicators in the Quick Check section, and pads with three overlapping summary sections (Best Practices, Notes, Validation Criteria). This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than the mostly-efficient anchor 3.

2 / 5

Actionability

For an instruction-only skill it is largely actionable: concrete scan patterns (@Entity, *Service, *UseCase, *Controller), a quantified 0-10 cohesion formula, decision trees, and copy-paste output templates. Minor gaps — sub-scores like 'Linguistic Cohesion (0-3)' lack operational definitions of how to assign values, keeping it below the fully executable anchor.

4 / 5

Workflow Clarity

Six clearly sequenced phases (extract → group → classify → assess → detect issues → map contexts) with an Analysis Checklist acting as an end-of-workflow validation. Not 5 because validation is a trailing checklist rather than explicit in-phase checkpoints, and no feedback loop for revising boundaries when cohesion is low.

4 / 5

Progressive Disclosure

No bundle files exist, and the entire skill is one monolithic file with output templates, DDD reference material, and cohesion scoring all inlined in SKILL.md — content that clearly belongs in separate reference files. Header structure is good, matching the 'some structure but content that should be separate is inline' anchor rather than the minimal-structure anchor 2.

3 / 5

Total

13

/

20

Passed

Description

90%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 is well-crafted: concrete what-statement, explicit and natural trigger phrases including question forms users would actually say, and negative boundaries that disambiguate sibling skills. The only weakness is that the capability statement lists just two actions while the full scope (classification, cohesion scoring, bounded-context suggestion) is left implicit in the trigger list.

DimensionReasoningScore

Specificity

"Maps business domains and suggests service boundaries" names the domain with two concrete actions, but classification, cohesion assessment, and bounded-context mapping only appear as trigger phrases rather than stated capabilities. This matches the '1-2 concrete actions, but not comprehensive' anchor; not 4 because several specific actions are not explicitly listed as what the skill does.

3 / 5

Completeness

Explicitly answers what ("Maps business domains and suggests service boundaries... using DDD Strategic Design") and when ("Use when asking..." with concrete trigger phrases), plus negative boundary guidance. Clearly matches the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasings as explicit triggers: "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", "analyzing domain cohesion" — comprehensive coverage with question-form synonyms users would naturally say.

5 / 5

Distinctiveness Conflict Risk

A clear DDD Strategic Design niche with distinct triggers, and explicit do-not-use pointers routing to sibling skills ("use domain-identification-grouping", "use coupling-analysis") eliminate conflict risk. Minimal overlap with any generic skill.

5 / 5

Total

18

/

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

tech-leads-club/agent-skills

Path

packages/skills-catalog/skills/(architecture)/domain-analysis/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.