skills.rest
htlin222
htlin222COMMUNITY
Explore all skills by this author →
Website𝕏@htlin222GitHub

module-management

Validate module documentation and registry consistency across four documentation layers.

115|45|Updated Feb 5, 2026
Search Tags:#workflow#documentation#validation#quality#registry#scripts#module-management
One-click install
npx skills add https://github.com/htlin222/meta-pipe --skill module-management-htlin222
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-management
Source: https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/module-management
Command: npx skills add https://github.com/htlin222/meta-pipe --skill module-management-htlin222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and maintain module registry to ensure every new script, template, or feature is properly documented across all layers, preventing orphan scripts and ghost references.

Core Features & Use Cases

  • Ensures registration across Module SKILL.md, CLAUDE.md, GETTING_STARTED.md, and tests/README.md
  • Detects orphan scripts and ghost references and guides maintenance
  • Provides a repeatable workflow for adding, renaming, or removing scripts and templates

Quick Start

After adding or renaming a script, run the Module Management Skill to verify registration across all documentation layers.

Frequently Asked Questions about module-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate module documentation and registry consistency after adding new scripts?▼

To validate module documentation and registry consistency, run the validation workflow to enforce that every user-facing script is registered across Module SKILL.md, CLAUDE.md, GETTING_STARTED.md, and tests/README.md, ensuring no orphan scripts or ghost references remain.

What is the best way to prevent orphan scripts and ghost references in module registries?▼

Preventing orphan scripts and ghost references requires enforcing registration across four documentation layers: Module SKILL.md, CLAUDE.md, GETTING_STARTED.md, and tests/README.md. This validates that corresponding resources exist under ma-*/scripts/, ma-*/references/, or assets/.

How do I maintain documentation layers when renaming or removing scripts and templates?▼

Maintaining documentation layers when renaming or removing scripts requires a repeatable workflow that updates registrations across Module SKILL.md, CLAUDE.md, GETTING_STARTED.md, and tests/README.md, detecting orphan scripts and guiding maintenance to keep registries aligned.

Does module registry validation work with scripts located in tooling/python/ or ma-*/scripts/?▼

Module registry validation applies directly to scripts added in ma-*/scripts/ or tooling/python/. It enforces that these user-facing scripts are registered in all four documentation layers and that corresponding resources exist in the proper directories.

Why does updating reference templates require validation across multiple documentation layers?▼

Updating reference templates requires validation across multiple documentation layers because the registry enforces that every user-facing script and related doc is registered in Module SKILL.md, CLAUDE.md, GETTING_STARTED.md, and tests/README.md to prevent misalignment and ghost references.

Related Skills

Explore More Software Engineering Skills→
Areo-RGBAreo-RGB

skill-creator

Generate standardized SKILL.md frontmatter and optional bundled resource directories for Claude Skills.

Community
Intermediate
PackmindHubPackmindHub
306

packmind-create-skill

Scaffold SKILL.md frontmatter and resource directories for new Skill units.

Official
Intermediate
pisithrpspisithrps

connect-mcps

Connect MCP servers to a PM OS workspace and update SKILL.md files.

Community
Advanced
PracticalSwanPracticalSwan
7

documentation-automation

Configure markdownlint, link checkers, and pre-commit hooks for documentation validation.

Community
Intermediate