CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

modular-decomposition

Runs a sequenced monolith-to-modular pipeline that sizes and inventories components, finds shared domain duplication, addresses flattening and hierarchy issues, analyzes coupling, then groups components into candidate domain-aligned units, with optional embedded DDD strategic analysis for bounded contexts. Use when asking how to split a monolith, size components before extraction, find duplicated domain logic, clean up module hierarchy, measure coupling between modules, or group components into services. Do NOT use for phased extraction roadmaps or prioritization without the prior analysis steps (use decomposition-planning-roadmap after this pipeline), end-to-end legacy migration strategy writeups (use legacy-migration-planner), pure infrastructure capacity sizing, or when you only need DDD without the structural pipeline (install domain-analysis standalone).

Quality

88%

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

72%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 is a well-structured orchestration overview with strong progressive disclosure and good actionability, but its multi-step batch workflow lacks explicit validation checkpoints between pattern stages, capping workflow clarity.

Suggestions

Add an explicit validation/checkpoint step between patterns (e.g., 'Before Pattern 4, confirm a component inventory exists from Pattern 1; if missing, run Pattern 1 or derive and state an explicit module list') to lift workflow_clarity above 3.

Consolidate the DDD reference guidance into a single section to remove repetition across 'How to Use,' 'Prerequisites,' and 'Bounded contexts.'

Tighten the three usage examples to one line each to reduce padding without losing trigger coverage.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, though the DDD reference handling is repeated across 'How to Use,' 'Prerequisites,' and the 'Bounded contexts' section, and the three usage examples are slightly padded.

4 / 5

Actionability

Provides concrete, executable orchestration guidance — exact ordered steps (1→5), explicit file path patterns (references/pattern-NN-*.md), and a primary/optional reference table; minor gaps only. Code is absent but appropriately so for an instruction-only coordination skill.

4 / 5

Workflow Clarity

A clear ordered sequence and prerequisites exist, but this is a multi-pattern batch analysis pipeline with no explicit validation/checkpoint step between patterns (e.g., confirming an inventory exists before coupling analysis), which caps workflow clarity per the batch-operations guideline.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview that delegates bulk content to one-level-deep references/pattern-NN-*.md files (all verified to exist), with optional quick-reference variants and DDD files clearly signaled in both a table and inline text.

5 / 5

Total

16

/

20

Passed

Description

100%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 specific, trigger-rich, complete, and clearly bounded from sibling skills. It names concrete pipeline actions, lists natural trigger phrases, and provides explicit negative-scope guidance to avoid mis-invocation.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'sizes and inventories components, finds shared domain duplication, addresses flattening and hierarchy issues, analyzes coupling, then groups components' — giving comprehensive coverage of the pipeline's capabilities.

5 / 5

Completeness

Explicitly answers both what (the sequenced monolith-to-modular analysis pipeline) and when ('Use when asking how to split a monolith...'), with concrete trigger phrases and explicit exclusion guidance.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are well covered with synonyms: 'split a monolith,' 'size components before extraction,' 'find duplicated domain logic,' 'clean up module hierarchy,' 'measure coupling between modules,' and 'group components into services.'

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (structural analysis before extraction) and includes a 'Do NOT use' clause routing roadmaps to decomposition-planning-roadmap, migration strategy to legacy-migration-planner, and standalone DDD to domain-analysis, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

tech-leads-club/agent-skills

Path

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