Skip to content
TrustedSkillsbeta
Back to all skills

Code Modularization Evaluator

Checked
dotneet·vlatest·backend

This tool analyzes your code to assess how well it's modularized, helping you improve maintainability and reusability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dotneet/claude-code-marketplace --skill code-modularization-evaluator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dotneet

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dotneet/claude-code-marketplace at 07fa7eac95.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
07fa7eac95
Manifest
review-tool/skills/code-modularization-evaluator/SKILL.md
Scanned
4 files, 685 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes code to assess its modularity using the Balanced Coupling Model, a technique for identifying problematic coupling patterns in software design. It helps developers understand how well their code is structured and provides guidance on refactoring to improve maintainability and reusability. The tool evaluates coupling across three dimensions: Integration Strength, Distance, and Volatility, aiming for "balanced" rather than zero coupling.

When to use it

  • When refactoring existing codebases to improve modularity and reduce technical debt.
  • During design reviews to proactively identify potential coupling issues in new code.
  • To understand the impact of changes across different modules or services within a system.
  • To evaluate whether shared domain models are contributing to unnecessary coupling.

Key capabilities

  • Evaluates code based on Integration Strength (Intrusive, Functional, Model, Contract).
  • Assesses Distance between components (within class, same file, separate services, etc.).
  • Considers Volatility using Domain-Driven Design subdomain classification (Core, Supporting, Generic).
  • Provides actionable refactoring guidance based on the Balanced Coupling Model.

Example prompts

  • "Analyze this code snippet for modularity issues." [paste code]
  • "Evaluate the coupling between Service A and Service B."
  • "How can I reduce intrusive coupling in this module?"

Tips & gotchas

  • The skill focuses on identifying misdesigned coupling, not eliminating all coupling. The goal is balanced coupling.
  • Understanding Domain-Driven Design subdomains (Core, Supporting, Generic) will help interpret volatility assessments.
  • This is a code analysis tool; it does not automatically refactor code. It provides guidance for manual adjustments.