mot

The mot skill acts as the system integrity auditor for the Continuous Claude ecosystem. It provides a structured health check mechanism designed to ensure that the complex interplay between skills, autonomous agents, event-driven hooks, and the persistence-based memory system remains functional and consistent over time. It is intended for developers and power users who maintain, extend, or customize their agentic development environment and need a reliable way to verify system state after configuration changes or codebase updates.

• Performs a multi-phase audit covering skill frontmatter validation, agent configuration consistency, shell wrapper executability, and hook registration integrity.

• Validates memory system infrastructure, specifically ensuring PostgreSQL connectivity, pgvector extension availability for archival memory, and repository dependency health.

• Executes cross-reference checks between skills and agents to prevent dangling references and broken orchestration logic.

• Provides an automated fix capability through the --fix flag, which can resolve common environmental issues like missing executable permissions, outdated bundle builds, and missing directory structures.

• Offers granular execution modes, including a --quick flag for time-sensitive P0 checks and category-specific filtering (e.g., /mot hooks) to narrow down investigations.

• Use this tool periodically or following any structural changes to the .claude directory to ensure system stability.

• Typical inputs include command-line arguments like --fix for auto-remediation or specific category arguments to isolate failures.

• Expected outputs are standard out logs reporting pass/fail status for each phase, with diagnostic warnings for non-existent references or missing dependencies.

• Prerequisites include a configured .claude environment, active shell access for script execution, and appropriate database credentials for the memory system audit.

• The tool is strictly structural; it does not replace functional unit tests but acts as a first-line defensive measure against configuration drift and environmental setup errors.