tlamatini-flw-doctor

Name: tlamatini-flw-doctor
Availability: InStock
Author: XAIHT

Validate .flw workflow files for structural and semantic issues.

14|1|Updated Mar 6, 2026

Search Tags:#automation #workflow #integration #validation #static-analysis #lint #flw

Ready to run

npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-flw-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tlamatini-flw-doctor
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/tlamatini_flw_doctor
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-flw-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates .flw workflow files to catch structural and semantic issues before execution, reducing runtime failures and debugging time.

Core Features & Use Cases

Structural validation: JSON parses, required keys present (version, nodes, connections) and node types match known agents.
Connection integrity: Ensures every connection references existing node IDs and that terminal nodes do not misuse target_agents.
Parametrizer constraints: Enforces single-lane queue invariant for parametrizer nodes, with proper inbound/outbound edge configuration.
Practical use: Ideal for teams building complex FLW workflows who need deterministic pre-flight checks and actionable feedback.

Quick Start

Validate a .flw file by running the doctor to produce an ok, problems, and summary report.

Frequently Asked Questions about tlamatini-flw-doctor

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

FAQPage Schema

How do I validate a .flw workflow file for structural and semantic errors?▼

To validate a .flw workflow file, run a doctor audit that checks JSON parsing, required keys, node types, connection integrity, and parametrizer queue constraints, producing an ok, problems, and summary report.

What does workflow topology validation check for in agent connections?▼

Workflow topology validation checks connection integrity by ensuring every connection references existing node IDs and that terminal nodes do not misuse target_agents, verifying inputs, outputs, and access controls.

How do I enforce single-lane queue constraints for parametrizer nodes?▼

To enforce single-lane queue constraints for parametrizer nodes, apply static analysis to verify proper inbound and outbound edge configuration during workflow validation, catching structural issues before execution.

Why does my .flw workflow fail at runtime due to invalid agent types?▼

A .flw workflow fails at runtime due to invalid agent types when node types do not match known agents, requiring structural validation to catch these semantic issues before execution.

Can I use static analysis to check access controls and inputs in FLW workflows?▼

Yes, you can use static analysis to check access controls, inputs, and outputs in FLW workflows by enforcing in-process validation that reports structural and semantic issues in a .flw file.

What is the best way to perform pre-flight checks on complex FLW workflows?▼

The best way to perform pre-flight checks on complex FLW workflows is to audit .flw files for correctness, generating deterministic reports on topology, valid agent types, and connection integrity to reduce runtime failures.