heterogeneous-agent

Diagnose heterogeneous-agent pipeline failures across CLI adapters, IPC, and tool chains.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/mDevsLabs/mAI --skill heterogeneous-agent-mdevslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heterogeneous-agent
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/heterogeneous-agent
Command: npx skills add https://github.com/mDevsLabs/mAI --skill heterogeneous-agent-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Heterogeneous agent debugging across pipelines that connect external CLI agents, adapters, IPC, and tool-call sequences often leads to hard-to-trace failures. This skill provides a guided workflow to diagnose and isolate issues efficiently.

Core Features & Use Cases

  • Pipeline visibility across raw traces, adapted events, and persistence.
  • Reference flows for Claude Code and Codex adapters, subagent handling, and tool state tracking.
  • Repro-to-fix workflow guidance with focused tests and breakpoint strategies.

Quick Start

Follow the Heterogeneous Agent Debug Workflow to capture raw traces, compare raw and adapted events, and isolate the failing layer.

Frequently Asked Questions about heterogeneous-agent

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

FAQPage Schema
How do I debug a heterogeneous agent pipeline spanning CLI adapters and IPC?

Debugging a heterogeneous agent pipeline involves capturing raw CLI traces, comparing them to adapted events, and isolating the failing layer across adapters, IPC, and tool-call chains. This skill provides a structured workflow with reference flows and invariants to diagnose these cross-layer failures efficiently.

What is the best way to trace tool-call failures across Claude Code and Codex adapters?

Tracing tool-call failures across Claude Code and Codex adapters requires comparing raw traces against adapted events to pinpoint mapping mismatches. The workflow provides specific reference flows for these adapters, subagent handling, and tool state tracking to isolate persistence or hydration faults.

How do I isolate faults in agent tool persistence and UI hydration?

Isolating faults in agent tool persistence and UI hydration requires checking step boundaries and adapter mapping against raw CLI traces. The skill defines well-defined invariants for step boundaries and subagent handling, enabling focused tests and breakpoint strategies to isolate the exact failing layer.

Can I use this workflow to diagnose issues across external CLI agents and tool-call chains?

Yes, this workflow is specifically designed for diagnosing issues across external CLI agents, IPC, and tool-call chains. It provides a repro-to-fix workflow with practical guidance for isolating faults, comparing raw and adapted events, and running focused tests across the pipeline.

Why does my agent pipeline fail when mapping raw CLI traces to adapted events?

Agent pipeline failures during trace mapping often stem from broken invariants at step boundaries or subagent handling mismatches. The skill provides reference repository files and structured breakpoint strategies to compare raw and adapted events, isolating whether the fault lies in the adapter, persistence, or UI hydration.