Skills module-health

📦

module-health

Name: module-health
Author: C0ntr0lledCha0s

Content revision r2 Safe ⚙️ External commands📁 Filesystem access

Assess Module Architecture Health

Unbalanced modules and unclear dependencies make Logseq templates difficult to maintain. This skill scores module health and recommends focused structural improvements.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "module-health" from https://skillstore.io/skills/c0ntr0lledcha0s-module-health.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-module-health/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/c0ntr0lledcha0s-module-health.md Signed manifest GET /api/skills/c0ntr0lledcha0s-module-health/manifest Signed lockfile GET /api/skills/c0ntr0lledcha0s-module-health/lockfile

Test it

Using "module-health". Check module health and show the main concerns.

Expected outcome:

Overall health: 73 out of 100. Eight modules are healthy. The misc module is bloated, and two small modules need review.

Using "module-health". How should the misc module be reorganized?

Expected outcome:

Split communication, medical, financial, and education classes into focused modules.
Keep only items without a stable domain in misc.
Update references, build configuration, documentation, and validation checks in that order.

Using "module-health". Explain the person module score.

Expected outcome:

The module has strong documentation and clear cohesion. Its high property ratio needs contextual review, but its structure remains maintainable.

Security Audit

Safe

v9 • 7/23/2026 Open versioned report

All 66 static alerts are false positives after contextual review. PowerShell interpolation and Bash substitutions only format or calculate local health metrics; Markdown detections are code fences or inline formatting. No network access, destructive operation, credential handling, data exfiltration, or prompt injection was found.

Files scanned

1,546

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (50)

📁 Filesystem access (1)

scripts/health-check.sh:35

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/c0ntr0lledcha0s-module-health/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/c0ntr0lledcha0s-module-health/security.svg)](https://skillstore.io/skills/c0ntr0lledcha0s-module-health?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/c0ntr0lledcha0s-module-health?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-module-health/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-module-health.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

C0ntr0lledCha0s. (2026). module-health security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-module-health/audits/9

BibTeX citation

@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-module-health-2026,
  author = {C0ntr0lledCha0s},
  title = {module-health security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/c0ntr0lledcha0s-module-health/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "module-health security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "C0ntr0lledCha0s"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-module-health/audits/9"
identifiers:
  - type: other
    value: "skillstore:c0ntr0lledcha0s-module-health:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Review Current Module Health

Generate a scored overview before deciding which modules need attention.

Plan Architecture Refactoring

Identify natural module boundaries and create a prioritized reorganization plan.

Validate a New Module

Check size, documentation, references, and consistency before submitting changes.

Try These Prompts

Run a Quick Health Check

Check module health in the current Logseq Template Graph. Show scores, key counts, and the three most important issues.

Analyze One Module

Analyze the [module name] module in detail. Explain its score, cohesion, documentation, dependencies, and practical improvements.

Compare Architecture Changes

Compare current module health with [revision or date]. Summarize score changes, growth, new coupling, and regressions.

Design a Reorganization Plan

Create a reorganization plan for [module name]. Group classes by domain, map dependency impacts, define migration steps, and estimate effort.

Best Practices

Review score details before accepting a recommendation.
Confirm cross-module references before moving classes or properties.
Run validation and compare health scores after each structural change.

Avoid

Do not split modules only to satisfy a numeric threshold.
Do not move classes without updating dependent references and build configuration.
Do not treat the common module like a standard domain module.