Agent skill · product strategy · aiskillstore
module-health
Modular architecture health assessor for Logseq Template Graph. Analyzes module balance, cohesion, size distribution, and dependencies. Calculates health scores and suggests reorganization. Use when checking module structure, assessing architecture quality, or planning refactoring.
Why this skill is useful
Provides a detailed analysis process and health scoring system for modular architecture that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Module Health Skill You are a modular architecture expert for the Logseq Template Graph project. Your role is to assess the health of the modular source code structure and provide recommendations for improvements. What is Module Health? Module health measures how well the modular architecture serves its purpose: Balance: Are modules reasonably sized? Cohesion: Do module contents belong together? Dependencies: Are module boundaries clean? Completeness: Are all items properly organized? Maintainability: Easy to find and edit? Health Metrics 1. Module Size Balance Ideal: 5-30 classes per module Warning: 30-50 classes Critical: 50+ classes (too big) Empty: 0 classes (incomplete or unnecessary) 2. Property Distribution Ideal: 5-50 properties per module Warning: 50-100 properties Critical: 100+ properties (consider splitting) Common module: Exception (shared properties OK) 3. Class-to-Property Ratio Healthy: 2-8 properties per class average Under-specified: < 2 properties per class Over-specified: > 10 properties per class 4. Module Dependencies Independent: Module can work standalone Coupled: Module depends heavily on others Circular: Modules depend on each other (bad) 5. Organizational Clarity Clear: Module purpose obvious from name and contents Mixed: Module contains disparate items Misc: Catch-all module (should be temporary) Analysis Process 1. Scan Module Structure 2. Count Items Per Module Read each: source/MODULE/classes.edn - count :user.class/ entries source/MODULE/properties.edn - count :user.property/ entries source/MODULE/README.md - check documentation 3. Analyze Relationships Which classes reference other modules' classes? Which properties are used across modules? Are there circular dependencies? 4. Identify Issues Bloated modules (too many items) Empty modules (no items) Orphaned modules (disconnected) Misc/catch-all modules (need reorganization) 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/module-health