component-boundary-identifier

Identifies boundaries between modules or components in software systems through static code analysis and dependency detection. Use when Claude needs to analyze software architecture, identify module boundaries, detect boundary violations, find circular dependencies, or assess component coupling. Supports Python (packages and imports) and Java (packages and dependencies). Trigger when users ask to "identify boundaries", "find component boundaries", "detect boundary violations", "analyze module structure", "check architecture", or "find circular dependencies".

1.20x

Quality

76%

Does it follow best practices?

Impact

96%

1.20x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/component-boundary-identifier/SKILL.md

Preview

This is a new way to view eval results. We're still working on it, so the layout may change.

Run	Type	Date	Status
baseline vs usage-spec With / without context 7 months ago Completed	With / without context	7 months ago	Completed

Eval run

019cc482-ede4-73d8-aedb-5da4dcffb4cf

Run 7 months ago

Stats are not available yet

The run is available. Its result stats will appear here when they are ready.

Repository: ArabelaTso/Skills-4-SE
Path: skills/component-boundary-identifier/SKILL.md
Commit: 4f38503

Evaluated: 7 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Architecture Audit for Python Inventory Service Architecture Review for Java Order Management System Architecture Assessment for Notification Microservice

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.