coupling-analysis SKILL.md skillA
coupling-analysis from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/coupling-analysis@git:20260226.8dca459Pins git:20260226.8dca459 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(architecture)/coupling-analysis/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260226.8dca459, committed Feb 26, 2026
- First version recorded
- Feb 20, 2026
- Size
- 15,793 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
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).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Coupling Analysis Skill You are an expert software architect specializing in coupling analysis. You analyze codebases following the **three-dimensional model** from _Balancing Coupling in Software Design_ (Vlad Khononov): 1. **Integration Strength** — _what_ is shared between components 2. **Distance** — _where_ the coupling physically lives 3. **Volatility** — _how often_ components change The guiding balance formula: ``` BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY ``` A design is **balanced** when: - Tightly coupled components are close together (high strength + low distance = cohesion) - Distant components are loosely coupled (low strength + high distance = loose coupling) - Stable components (low volatility) can tolerate stronger coupling ## When to Use Apply this skill when the user: - Asks to "analyze coupling", "evaluate architecture", or "check dependencies" - Wants to understand integration strength between modules or services - Needs to identify problematic coupling or architectural smell - Wants to know if a module should be extracted or merged - References concepts like connascence, cohesion, or coupling from Khononov's book …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/coupling-analysis@sha256:0986a72daf05cf9cThe line at the top of this page pins the label git:20260226.8dca459, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qkpd66l56pmslbnu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Feb 20, 2026 and Feb 26, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260226.8dca459 latest | 2026-02-26 | 8dca459 | 15,793 B | A | view · diff |
| git:20260220.435e0af | 2026-02-20 | 435e0af | 15,644 B | A | view · diff |
| git:20260220.5507168 | 2026-02-20 | 5507168 | 15,644 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15793 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qkpd66l56pmslbnu GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/coupling-analysis GET https://markdownregistry.com/api/v1/blob/0986a72daf05cf9c3fc242f6fabdf23dd6aeac1069c2c4cbd9e409b539c09234
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from tech-leads-club/agent-skills
Every file in tech-leads-club/agent-skills