component-boundary-identifier
Identifies natural component boundaries inside a monolith by clustering the dependency graph, finding the cuts with minimum coupling. Use when planning to modularize or extract microservices, when deciding what can be deployed independently, or when the user asks where the seams in this codebase are.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill component-boundary-identifier100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 articulates specific technical capabilities (dependency graph clustering, finding minimum coupling cuts) while providing explicit trigger guidance for when to use it. The description uses proper third-person voice and covers multiple natural phrasings users might employ when seeking this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'clustering the dependency graph', 'finding the cuts with minimum coupling', 'identifies natural component boundaries'. These are precise technical operations, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Identifies natural component boundaries inside a monolith by clustering the dependency graph, finding the cuts with minimum coupling') AND when ('Use when planning to modularize or extract microservices, when deciding what can be deployed independently, or when the user asks where the seams in this codebase are'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'modularize', 'extract microservices', 'deployed independently', 'seams in this codebase'. These cover common ways developers discuss code decomposition. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on monolith decomposition and dependency analysis. Distinct triggers like 'microservices', 'seams', 'minimum coupling', and 'modularize' are unlikely to conflict with general code analysis or refactoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates expert-level content design. It provides a complete methodology for identifying component boundaries with concrete metrics, a realistic worked example, clear anti-patterns, and a structured output format. The content is dense but well-organized, respecting Claude's intelligence while providing genuinely novel domain guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with actionable tables, metrics, and examples. No explanation of basic concepts Claude would know; jumps straight into domain-specific guidance on graph clustering and coupling metrics. | 3 / 3 |
Actionability | Provides concrete metrics (cohesion > 0.5, coupling < 0.2), specific edge types with weight hints, a complete worked example with real numbers, and a detailed output format template. Claude can immediately apply this methodology. | 3 / 3 |
Workflow Clarity | Clear sequence: build graph → cluster → measure cohesion/coupling → drill into problem areas → propose cuts → determine extraction order. The 'Do not' section provides explicit validation checkpoints and the extraction order section gives clear sequencing for implementation. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from concepts to methods to worked example to output format. Content is appropriately sized for a single skill file (~150 lines) with no need for external references. Tables organize dense information efficiently. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.