mthds-explain

Original：🇺🇸 English

Translated

Explain and document MTHDS bundles. Use when user says "what does this pipeline do?", "explain this workflow", "explain this method", "walk me through this .mthds file", "describe the flow", "document this pipeline", "how does this work?", or wants to understand an existing MTHDS method bundle.

3installs

Sourcemthds-ai/skills

Added on2026-02-27

NPX Install

npx skill4agent add mthds-ai/skills mthds-explain

SKILL.md Content

View Translation Comparison →

Explain MTHDS bundles

Analyze and explain existing MTHDS method bundles in plain language.

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.

Step 1: Read the .mthds File

Read the entire bundle file to understand its structure.

Step 2: Identify Components

List all components found in the bundle:

Domain: the
```
[domain]
```
declaration
Concepts: all
```
[concept.*]
```
blocks — note which are custom vs references to native concepts
Pipes: all
```
[pipe.*]
```
blocks — identify the main pipe and sub-pipes
Main pipe: declared in
```
[bundle]
```
section

Step 3: Trace Execution Flow

Starting from the main pipe, trace the execution path:

For PipeSequence: follow the
```
steps
```
array in order
For PipeBatch: identify
```
batch_over
```
and
```
batch_as
```
, then the inner pipe
For PipeParallel: list all branches
For PipeCondition: map condition → pipe for each branch
For PipeLLM / PipeExtract / PipeImgGen / PipeFunc: these are leaf operations

Step 4: Present Explanation

Structure the explanation as:

Purpose: one-sentence summary of what the method does
Inputs: list each input with its concept type and expected content
Output: the final output concept and what it contains
Step-by-step flow: walk through execution in order, explaining what each pipe does
Key concepts: explain any custom concepts defined in the bundle

Step 5: Generate Flow Diagram

Create an ASCII diagram showing the execution flow:

[input_a, input_b]
        |
   main_sequence
   ├── step_one (PipeLLM) → intermediate_result
   └── step_two (PipeExtract) → final_output

Adapt the diagram style to the method structure (linear, branching, batched).

Step 6: Optional — Validate

If the user wants to confirm the method is valid:

bash

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

Step 7: Optional — Visual Graph

For an interactive visual graph, suggest running the method with

/mthds-run

using real inputs: