component-common-domain-detection
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).
70
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(architecture)/component-common-domain-detection/SKILL.mdQuality
Discovery
100%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 defines its purpose, provides rich natural-language trigger terms, and explicitly delineates its boundaries from related skills. The inclusion of both 'Use when' and 'Do NOT use' clauses makes it highly effective for skill selection among a large pool of available skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: finding duplicate business logic across components, suggesting consolidation, and analyzing component overlap before refactoring. It also clearly delineates what it does NOT do (code-level duplication, dependency analysis). | 3 / 3 |
Completeness | Clearly answers both 'what' (finds duplicate business logic across components and suggests consolidation) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also includes 'Do NOT use' guidance which further clarifies scope. | 3 / 3 |
Trigger Term Quality | Includes natural phrases users would actually say: 'where is this logic duplicated?', 'find common code between services', 'what can be consolidated?', 'detect shared domain logic', and 'component overlap before refactoring'. These cover a good range of natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche by specifying business logic duplication (not code-level duplication) and explicitly distinguishes itself from linters and coupling-analysis skills. The 'Do NOT use' clause directly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is far too verbose for its purpose, repeating the same notification/audit/validation examples across nearly every section and explaining concepts Claude already understands (coupling, shared libraries, domain vs infrastructure). While the structured analysis phases and output format templates provide some value, the content would be dramatically more effective at 25-30% of its current length with detailed templates and language-specific examples split into referenced files.
Suggestions
Reduce content by 60-70%: eliminate repeated examples (notification/audit appear in nearly every section), remove explanations of basic concepts (what coupling is, what shared libraries are), and consolidate redundant sections.
Split detailed content into referenced files: move output format templates to OUTPUT_TEMPLATES.md, fitness functions to FITNESS_FUNCTIONS.md, and language-specific implementation notes to separate files.
Add explicit validation checkpoints: what to verify after each analysis phase, how to handle edge cases (no patterns found, high coupling increase), and when to abort consolidation recommendations.
Make the Usage Examples section actionable by showing actual tool commands or file operations Claude should perform, rather than just describing what 'the skill will do' in abstract terms.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Extensively explains concepts Claude already knows (domain vs infrastructure, what shared libraries are, what coupling means). Massive amounts of repetition — the same notification/audit/validation examples are repeated across nearly every section. The output format examples, analysis process, and implementation notes all re-explain the same concepts. | 1 / 3 |
Actionability | Provides some concrete code snippets (namespace detection, shared class detection functions) and structured output formats, but much of the content is descriptive rather than executable. The 'Usage Examples' section just describes what the skill will do rather than showing actual commands or tool usage. The code examples are illustrative helper functions, not complete executable workflows. | 2 / 3 |
Workflow Clarity | The 5-phase analysis process is clearly sequenced and the checklist at the end is useful. However, there are no explicit validation checkpoints or error recovery steps — no guidance on what to do if namespace scanning finds nothing, if coupling analysis reveals problems, or how to verify consolidation recommendations are correct before acting on them. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. Content that could easily be split out (detailed output format templates, fitness functions, implementation notes for different languages, the full consolidation plan template) is all inline, making the skill extremely long and hard to navigate. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (607 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.