Check MTHDS bundles

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

Process

Prerequisite: See CLI Prerequisites

Read the .mthds file — Load and parse the method

Run CLI validation (use -L pointing to the bundle's own directory to avoid namespace collisions):

mthds-agent pipelex validate <file>.mthds -L <bundle-directory>/

Parse the JSON output:

• If success: true — all pipes validated, report clean status

• If error — see Error Handling Reference for error types and recovery

Cross-domain validation — when the bundle references pipes from other domains, use --library-dir (see Error Handling — Cross-Domain)

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)

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

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

• CLI Prerequisites — read at skill start to check CLI availability

• 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