CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

87

1.20x
Quality

81%

Does it follow best practices?

Impact

96%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Evaluation results

100%

22%

Architecture Audit for Python Inventory Service

Automated Python boundary analysis with script

Criteria
Without context
With context

Script invocation

0%

100%

IDENTIFIED BOUNDARIES section

100%

100%

BOUNDARY VIOLATIONS section

100%

100%

Severity tags present

100%

100%

CRITICAL classification for domain→infra

100%

100%

CRITICAL classification for circular deps

100%

100%

RECOMMENDATIONS section

100%

100%

Fix critical first

100%

100%

Interface/DI recommendations

100%

100%

Circular dependency fix

30%

100%

100%

20%

Architecture Review for Java Order Management System

Java layered architecture violation detection

Criteria
Without context
With context

IDENTIFIED BOUNDARIES section

100%

100%

BOUNDARY VIOLATIONS section

100%

100%

RECOMMENDATIONS section

100%

100%

Severity labels used

100%

100%

Domain→infra classified CRITICAL

100%

100%

Layer skipping classified HIGH

100%

100%

Framework annotation in domain classified HIGH

0%

100%

Package-private access classified MEDIUM

100%

100%

Java-specific fix: interface over concrete

100%

100%

Java-specific fix: separate persistence entity

0%

100%

Dependency direction noted

100%

100%

89%

7%

Architecture Assessment for Notification Microservice

Clean and hexagonal architecture assessment

Criteria
Without context
With context

Boundaries identified

100%

100%

Core→adapter violation flagged CRITICAL

83%

100%

Core→framework violation flagged HIGH

0%

60%

Private member access flagged MEDIUM

40%

30%

Inward-only dependency rule stated

100%

100%

IDENTIFIED BOUNDARIES section present

100%

100%

BOUNDARY VIOLATIONS section present

100%

100%

RECOMMENDATIONS section present

100%

100%

Interface/port recommendation

100%

100%

DI recommendation

100%

100%

Python-specific analysis applied

100%

100%

Repository
ArabelaTso/Skills-4-SE
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.