domain-identification-grouping
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (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)/domain-identification-grouping/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 disambiguates itself from related skills. The 'Do NOT use' clauses with references to alternative skills are particularly effective for preventing misselection in a multi-skill environment. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists a concrete action ('Groups existing components into logical business domains to plan service-based architecture') and further clarifies scope with explicit boundary statements about what it does NOT do, which adds specificity. | 3 / 3 |
Completeness | Clearly answers both 'what' (groups existing components into logical business domains for service-based architecture planning) and 'when' (explicit 'Use when' clause with multiple trigger scenarios). Also includes 'Do NOT use' guidance for disambiguation, which goes above and beyond. | 3 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases users would actually say: 'which components belong together?', 'group these into services', 'organize by domain', 'component-to-domain mapping', 'service extraction'. These cover a good range of natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills (domain-analysis and coupling-analysis) with 'Do NOT use for' clauses, creating a clear niche. The specific focus on grouping existing components into domains is well-differentiated. | 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 extremely verbose and repetitive, presenting the same domain grouping examples multiple times across different sections (analysis process, output format, domain map). While it provides some concrete artifacts like namespace refactoring tables and fitness function code, the signal-to-noise ratio is very low. The content would benefit enormously from being condensed to ~30% of its current size and splitting reference material into separate files.
Suggestions
Eliminate repetition: The Customer/Ticketing/Reporting domain examples appear in at least 4 different sections. Show them once in a concise example, then reference that example.
Split into multiple files: Move output format templates to OUTPUT_TEMPLATES.md, fitness functions to FITNESS_FUNCTIONS.md, and language-specific implementation notes to separate files. Keep SKILL.md as a concise overview with the core process.
Remove explanations of basic concepts Claude already knows (what a domain is, what namespaces are, what business capabilities are) and focus on the specific decision criteria and heuristics that make this skill unique.
Add concrete validation steps for namespace refactoring: specify actual commands to verify imports are updated, tests pass, and no broken references remain, rather than just 'Run tests to verify changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The same examples (Customer/Ticketing/Reporting domains, namespace refactoring tables) are repeated 3-4 times across different sections. Core concepts Claude already understands (what a domain is, what namespaces are) are over-explained. The content could be reduced by 60-70% without losing actionable information. | 1 / 3 |
Actionability | Provides concrete examples of domain groupings, namespace refactoring tables, and fitness function code. However, much of the guidance is procedural description ('The skill will: 1. Analyze... 2. Check...') rather than executable instructions. The fitness function code is useful but the bulk of content describes what to do abstractly rather than providing specific, executable steps for analyzing a real codebase. | 2 / 3 |
Workflow Clarity | The 5-phase process is clearly sequenced and includes a validation phase (Phase 3) with a checklist. However, the validation steps are soft ('Get stakeholder validation', 'Check cohesion') rather than concrete automated checks. The namespace refactoring phase mentions 'Run tests to verify changes' but lacks specific validation commands or error recovery steps for what is a potentially destructive batch operation. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to external documents. The content is extremely long with repeated examples, output format templates, implementation notes for multiple languages, fitness functions, best practices, common patterns, and domain size guidelines all inline. Much of this should be split into separate reference files (e.g., OUTPUT_TEMPLATES.md, FITNESS_FUNCTIONS.md, EXAMPLES.md). | 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 (732 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- tech-leads-club/agent-skills
- Commit
906a57d
- 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.