component-flattening-analysis
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).
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-flattening-analysis/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 hits all the marks. It provides specific concrete actions, includes natural trigger terms users would say, explicitly answers both what and when, and actively differentiates itself from related skills with 'Do NOT use' guidance. The negative boundary clauses are a particularly strong feature for disambiguation in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: detects misplaced classes, fixes component hierarchy problems, finds code that should belong inside a component but sits at root level. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (detects misplaced classes, fixes component hierarchy problems) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also includes explicit 'Do NOT use' guidance to prevent misuse, which goes beyond the minimum. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'clean up component structure', 'find orphaned classes', 'fix module hierarchy', 'flatten nested components', 'misplaced code', 'namespaces'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinctive with clear niche (component hierarchy and misplaced classes). The explicit 'Do NOT use' clauses referencing specific alternative skills (coupling-analysis, domain-identification-grouping) actively reduce 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 extremely verbose and repetitive, restating the same three flattening strategies and orphaned class concept across multiple sections (core concepts, analysis phases, output formats, common patterns, notes). While it provides some useful concrete examples like directory structures and JavaScript detection functions, the signal-to-noise ratio is very low. The content would benefit enormously from being condensed to ~25% of its current size and splitting detailed reference material into separate files.
Suggestions
Reduce the skill to under 100 lines by eliminating repeated explanations of the same concepts (orphaned classes, three flattening strategies) — state each concept once with one clear example.
Split detailed content into separate files: move fitness functions to FITNESS.md, output format templates to TEMPLATES.md, and language-specific implementation notes to IMPLEMENTATION.md, with clear one-level references from the main skill.
Replace the abstract 'the skill will' usage examples with concrete, executable examples showing actual commands or code that Claude should run/produce.
Add explicit validation checkpoints with specific commands in the execution workflow — e.g., 'verify no broken imports by running X' rather than just 'run tests to verify changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Massive repetition across phases, examples, output formats, patterns, and notes — the same concepts (orphaned classes, flattening strategies, consolidate/split/shared) are restated 5-6 times in slightly different forms. Claude already understands directory structures, namespaces, and refactoring; this over-explains basic concepts. | 1 / 3 |
Actionability | Provides some concrete code examples (JavaScript detection functions, fitness functions) and specific directory structure examples, but much of the content is descriptive workflow prose rather than executable guidance. The 'Usage Examples' section just describes what 'the skill will do' in abstract numbered steps rather than showing actual commands or code to run. | 2 / 3 |
Workflow Clarity | Has a clear 5-phase process with numbered steps and a comprehensive checklist, but validation/verification is weak — 'Run tests to verify changes' is vague with no specific validation commands. The execution phase lacks explicit feedback loops for error recovery despite being a destructive refactoring operation (moving files, updating imports). | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content — core concepts, analysis process, output formats, implementation notes, fitness functions, best practices, common patterns — is inlined in a single massive document. Much of this (especially the repeated examples and fitness functions) should be split into separate reference files. | 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 (694 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.