ddd-context-mapping

Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ddd-context-mapping/SKILL.md

Quality

Content

50%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 skill is well-structured and concise, appropriately scoping when to use it and what outputs to expect. However, it lacks concrete, actionable guidance—there are no examples of actual context maps, pattern definitions, or sample outputs that would let Claude produce high-quality results. The referenced supporting file does not exist in the bundle, undermining progressive disclosure.

Suggestions

Add a concrete example showing a completed context map (e.g., a table or diagram of context pairs with their relationship patterns like Shared Kernel, Customer-Supplier, ACL, etc.) so Claude knows exactly what to produce.

List the available relationship patterns (e.g., Shared Kernel, Customer-Supplier, Conformist, Anti-Corruption Layer, Open Host Service, Published Language) directly in the skill or in the referenced file.

Provide a sample output template (e.g., a contract ownership matrix and translation rules table) so the output requirements are actionable rather than abstract.

Create the referenced `references/context-map-patterns.md` file with detailed pattern descriptions and decision criteria.

Dimension	Reasoning	Score
Conciseness	The skill is fairly lean and avoids explaining what DDD or context mapping is, which respects Claude's intelligence. Minor verbosity in the 'Use this skill when' / 'Do not use this skill when' sections could be tightened slightly, but overall it's efficient.	4 / 5
Actionability	The instructions are high-level directives ('List all context pairs', 'Choose relationship patterns') without concrete examples of what a context map looks like, what specific patterns to choose from, or any executable/structured output. The example is just a prompt invocation, not a demonstration of input/output.	2 / 5
Workflow Clarity	There is a clear 4-step sequence, but steps are vague (e.g., 'Choose relationship patterns per pair' without listing the patterns or decision criteria). There are no validation checkpoints or feedback loops for verifying the mapping is correct or complete.	3 / 5
Progressive Disclosure	The skill references `references/context-map-patterns.md` for detailed mapping structures, which is good progressive disclosure design. However, no bundle files are provided, meaning the reference is a dead link. The skill itself is well-sectioned but the lack of actual supporting files limits the score.	3 / 5
	Total	12 / 20 Passed

Description

53%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 identifies a clear domain (DDD context mapping) and mentions two concrete actions, but lacks a 'Use when...' clause that would help Claude know when to select this skill. The trigger terms are overly technical and miss natural language synonyms users might employ. It's reasonably distinctive within its niche but would benefit from explicit trigger guidance and broader keyword coverage.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about service integration patterns, bounded context relationships, context maps, anti-corruption layers, shared kernels, or how microservices should communicate.'

Include natural language synonyms and related terms users might say, such as 'microservice boundaries', 'service dependencies', 'upstream/downstream relationships', 'ACL', 'shared kernel', 'open host service'.

List more specific actions such as 'identify upstream/downstream relationships, apply patterns like anti-corruption layer, shared kernel, open host service, and published language'.

Dimension	Reasoning	Score
Specificity	Names the domain (DDD context mapping) and mentions two concrete actions ('map relationships between bounded contexts' and 'define integration contracts'), but doesn't elaborate on specific patterns or outputs, leaving coverage incomplete.	3 / 5
Completeness	Has a clear 'what' (map relationships and define integration contracts using DDD context mapping patterns) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.	3 / 5
Trigger Term Quality	Includes relevant DDD-specific terms like 'bounded contexts', 'integration contracts', and 'context mapping patterns', but these are fairly technical. Missing natural user phrases like 'how services communicate', 'anti-corruption layer', 'shared kernel', 'upstream/downstream', or 'microservice boundaries' that users might actually say.	3 / 5
Distinctiveness Conflict Risk	The focus on DDD context mapping patterns is fairly niche and distinct. There's minor overlap risk with general DDD skills or architecture skills, but the specific mention of 'bounded contexts' and 'context mapping patterns' narrows the scope well.	4 / 5
	Total	13 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/ddd-context-mapping/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.