mthds-check

Original：🇺🇸 English
Translated

Check and validate MTHDS bundles for issues. Use when user says "validate this", "check my workflow", "check my method", "does this .mthds make sense?", "review this pipeline", "any issues?", "is this correct?". Reports problems without modifying files. Read-only analysis.

3installs
Sourcemthds-ai/skills
Added on

NPX Install

npx skill4agent add mthds-ai/skills mthds-check

Tags

Translated version includes tags in frontmatter
mthds-validationcli-toolbundle-auditworkflow-reviewread-only-analysis

SKILL.md Content

View Translation Comparison →

Check MTHDS bundles

Validate and review MTHDS bundles based on the MTHDS standard without making changes.

Process

Step 0 — CLI Check (mandatory, do this FIRST)

Run 
mthds-agent --version
.
  • If it succeeds: proceed to the next step.
  • If it fails or the command is not found: STOP. Do not proceed with this skill. Tell the user:
The 
mthds-agent
CLI is required but not installed. Install it with:
npm install -g mthds
Then re-run this skill.
Do not write 
.mthds
files manually, do not scan for existing methods, do not do any other work. The CLI is required for validation, formatting, and execution — without it the output will be broken.
  1. Read the .mthds file — Load and parse the method
  2. Run CLI validation (use 
    -L
    pointing to the bundle's own directory to avoid namespace collisions):
    bash
    mthds-agent pipelex validate pipe <file>.mthds -L <bundle-directory>/
  3. Parse the JSON output:
    • If 
      success: true
      — all pipes validated, report clean status
    • If error — see Error Handling Reference for error types and recovery
  4. Cross-domain validation — when the bundle references pipes from other domains, use 
    --library-dir
    (see Error Handling — Cross-Domain)
  5. Analyze for additional issues (manual review beyond CLI validation):
    • Unused concepts (defined but never referenced)
    • Unreachable pipes (not in main_pipe execution path)
    • Missing descriptions on pipes or concepts
    • Inconsistent naming conventions
    • Potential prompt issues (missing variables, unclear instructions)
  6. Report findings by severity:
    • Errors: Validation failures from CLI (with 
      error_type
      and 
      pipe_code
      )
    • Warnings: Issues that may cause problems (e.g., model availability)
    • Suggestions: Improvements for maintainability
  7. Do NOT make changes — This skill is read-only

What Gets Checked

  • TOML syntax validity
  • Concept definitions and references
  • Pipe type configurations
  • Input/output type matching
  • Variable references in prompts
  • Cross-domain references
  • Naming convention compliance
  • Model preset resolution (dry run)

Reference

  • Error Handling — read when CLI returns an error to determine recovery
  • MTHDS Agent Guide — read for CLI command syntax or output format details
  • MTHDS Language Reference — read when reviewing .mthds TOML syntax
  • Native Content Types — read when checking 
    $var.field
    references in prompts to verify the attribute exists on the content type