CtrlK
BlogDocsLog inGet started
Tessl Logo

coupling-analysis

Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/skills/(architecture)/coupling-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured methodology with concrete examples and a clear six-phase process, but it is a long monolithic document that would benefit from splitting detailed reference material into bundle files and adding verification checkpoints.

Suggestions

Move the detailed Integration Strength catalog (Phases 3-5 tables and connascence degrees) and the report templates (Phase 6) into separate reference files under references/, keeping SKILL.md as a concise overview with one-level-deep links.

Add an explicit verification step in Phase 6 (e.g., cross-check each identified issue against concrete code evidence and confirm the volatility/distance classification with the user) before finalizing the report.

Trim the 'When to Use' section since its trigger phrases already appear in the frontmatter description, and tighten the Known Limitations to avoid overlapping with the heuristics.

DimensionReasoningScore

Conciseness

Mostly substantive methodology with useful tables and code, but at ~420 lines it could be tightened — the 'When to Use' section duplicates the description's triggers and some classification detail could be trimmed.

3 / 5

Actionability

Concrete executable Python/TypeScript/bash snippets and specific report templates, but the code is illustrative of patterns rather than complete runnable programs, leaving minor gaps.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with sub-steps, but there are no explicit validate/verify checkpoints for confirming findings before reporting; the skill is analytical (not destructive), so the cap does not apply.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the skill is a single monolithic ~420-line file with no references; content like the integration-strength catalog and report templates that could live in separate files is inlined, and the <50-line simple-skill exception does not apply.

3 / 5

Total

14

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete model reference, rich natural trigger phrases, and explicit use-when guidance with a clear do-not-use boundary against sibling skills. Only minor room to expand the action verb list beyond 'Analyzes'.

DimensionReasoningScore

Specificity

Names the domain and the concrete three-dimensional model (strength, distance, volatility), giving several specific elements, though the action verb 'Analyzes' is generic and a fuller action list would reach 5.

4 / 5

Completeness

Explicitly states both what it does ('Analyzes coupling between modules using the three-dimensional model...') and when to use it ('Use when asking...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Six natural trigger phrases users would actually say ('are these modules too coupled?', 'show me dependencies', 'analyze integration quality', 'which modules should I decouple?', 'coupling report', 'evaluating architectural health') give comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (coupling analysis) with an explicit exclusion clause ('Do NOT use for domain boundary analysis (use domain-analysis) or component sizing...') minimizing conflict with sibling skills.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.