fabrcore-messaging

Route AgentMessage and EventMessage between FabrCore agents with ACL enforcement.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-messaging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrcore-messaging
Source: https://github.com/vulcan365/FabrCore/tree/main/docs/skills/fabrcore-messaging
Command: npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-messaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages secure, scalable messaging among FabrCore agents, enforcing ACL rules and routing decisions to ensure correct delivery and policy compliance.

Core Features & Use Cases

  • Structured messaging schemas: AgentMessage and EventMessage with routing metadata for reliable delivery.
  • ACL enforcement: Cross-owner access control with rule evaluation to guard agent interactions.
  • Orchestration patterns: Delegator, Fan-Out, and Pipeline workflows to coordinate multi-agent tasks.

Quick Start

Configure a basic router that forwards an AgentMessage to a target agent while applying ACL rules.

Frequently Asked Questions about fabrcore-messaging

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

FAQPage Schema
How do I route messages securely between multiple agents?

Secure inter-agent messaging routes AgentMessage data to target agents while evaluating access control rules to ensure policy-compliant delivery and correct orchestration across cross-owner and owner-scoped agents.

What orchestration patterns can I use to coordinate multi-agent workflows?

Multi-agent workflows can be coordinated using Delegator, Fan-Out, and Pipeline orchestration patterns, enabling structured task delegation and parallel execution across multiple agents with reliable message delivery.

How does access control enforcement work for cross-owner agent interactions?

Cross-owner access control enforcement evaluates ACL rules during message routing to guard agent interactions, ensuring that only authorized messages are delivered across different agent owners.

Can I customize access control rules for inter-agent messaging?

Yes, inter-agent messaging supports optional ACL customization, allowing you to define specific access control rules to enforce cross-owner security policies during AgentMessage routing.

How do I monitor and trace inter-agent message routing?

Inter-agent message routing is monitored using OpenTelemetry instrumentation, which captures telemetry data on AgentMessage and EventMessage flows to provide observability into orchestration workflows and delivery status.

When should I use Pipeline orchestration for agent communication?

Pipeline orchestration should be used for agent communication when sequential, step-by-step task processing is required, ensuring that AgentMessage data flows through a structured series of agents with ACL enforcement at each stage.