check

Validate memory bank directory layout and core machine files with nine invariant checks.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/jackson2787/torque-coding --skill check-jackson2787
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/jackson2787/torque-coding/tree/main/skills/memory-bank/check
Command: npx skills add https://github.com/jackson2787/torque-coding --skill check-jackson2787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the memory bank and state machine structure by ensuring required directories and key machine files exist, and reports findings without modifying any files.

Core Features & Use Cases

  • Structural validation: verifies the presence and consistency of memory-bank directories and key machine files.
  • Invariant checks: runs nine predefined invariants to surface misconfigurations before runtime.
  • Non-destructive diagnostics: read-only analysis that never modifies files and guides remediation.

Quick Start

Run the memory-bank check to verify structural integrity before commencing work.

Frequently Asked Questions about check

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

FAQPage Schema
How do I validate the structure of my memory bank and machine files?

To validate memory bank structure, run a diagnostic check that verifies required directories and key machine files exist. It runs nine invariant checks to surface structural issues before runtime without modifying any data.

When should I perform a memory bank structural health check?

Perform a memory bank structural health check during bootstrap, after editing machine files, or when runtime behavior is suspect. This proactive diagnostic surfaces structural issues before execution begins.

Can I run memory bank validation without modifying my files?

Yes, memory bank validation is completely read-only. It performs non-destructive diagnostics that analyze directory layout and machine file consistency, reporting findings and guiding remediation without altering any files.

What is the best way to diagnose memory bank misconfigurations before execution?

The best way to diagnose misconfigurations is running predefined invariant checks that verify directory presence and file consistency. This read-only analysis surfaces structural issues early, ensuring state machine integrity before runtime.

Why does my memory bank runtime behavior fail after editing machine files?

Runtime behavior may fail due to structural issues introduced during edits. A read-only diagnostic check validates the memory bank directory layout and key machine files, running nine invariants to identify misconfigurations.

Are there limitations to using read-only diagnostics for memory bank validation?

Read-only diagnostics identify structural issues and misconfigurations but do not modify or repair files. The validation reports findings and guides remediation, requiring manual intervention to fix directory layout or machine file inconsistencies.