a2a-role-auditor

Audit node template definitions and validate routing in tmux-a2a-postman TOML files.

6|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/i9wa4/tmux-a2a-postman --skill a2a-role-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a2a-role-auditor
Source: https://github.com/i9wa4/tmux-a2a-postman/tree/main/skills/a2a-role-auditor
Command: npx skills add https://github.com/i9wa4/tmux-a2a-postman --skill a2a-role-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a2a role templates to ensure node-to-node communication is correct and reliable within tmux-a2a-postman deployments.

Core Features & Use Cases

  • Detects missing or misconfigured edges and node templates.
  • Validates a2a role templates against the project's postman.toml; identifies cross-edge and on_join issues; provides patch guidance for fixes.
  • Useful during onboarding of new nodes or when diagnosing routing failures across agents.

Quick Start

Run the auditor against your tmux-a2a-postman project to validate all node templates.

Frequently Asked Questions about a2a-role-auditor

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

FAQPage Schema
How do I validate a2a role templates for tmux routing failures?

To validate a2a role templates, audit node template definitions against postman.toml and per-node TOML files to detect misconfigured edges, missing templates, and cross-edge or on_join issues, then apply patch guidance for fixes.

Why does my tmux-a2a-postman node misbehave during agent onboarding?

Nodes misbehave during agent onboarding due to incomplete templates or routing breakdowns. Auditing node definitions identifies missing edges and validates talking lines across per-node TOML files to ensure correct node-to-node communication.

What's the best way to audit node templates for cross-edge interaction issues?

The best way to audit cross-edge interaction issues is to run a comprehensive auditing protocol that verifies edges and talking lines across postman.toml and per-node TOML files, generating patch guidance to fix interaction breakdowns.

Can I detect missing edges in postman.toml using template validation?

Yes, template validation detects missing or misconfigured edges by validating a2a role templates against the project's postman.toml, identifying cross-edge issues and providing patch guidance to fix routing failures.

Do I need per-node TOML files to run a routing audit for a2a roles?

Yes, per-node TOML files are required for routing audits. The auditing protocol verifies edges, talking lines, and on_join issues by checking template definitions across both postman.toml and per-node TOML files to produce patch guidance.

What limitations should I expect when diagnosing tmux routing failures with template audits?

Template audits diagnose routing failures by checking template completeness and edge configurations but are limited to producing patch guidance for fixes, requiring manual application of those patches to resolve misbehaving nodes.