peer-status

Queries peer agent status and sends messages via the Gateway API.

14|6|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/shuanbao0/agent-factory --skill peer-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer-status
Source: https://github.com/shuanbao0/agent-factory/tree/main/skills/peer-status
Command: npx skills add https://github.com/shuanbao0/agent-factory --skill peer-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Querying peer status and sending cross-agent messages can be complex without a unified workflow. This skill centralizes peer discovery and messaging through the Gateway.

Core Features & Use Cases

  • Peer status query: check which peers are online or busy before collaborating.
  • Cross-agent messaging: send messages to peers via the Gateway using the peer-status workflow.
  • Use Case: Coordinate a multi-agent task by validating availability and messaging the selected peer.

Quick Start

Run the peer-status script with your agent-id to fetch and display peer statuses.

Frequently Asked Questions about peer-status

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

FAQPage Schema
How do I check peer agent status before sending cross-agent messages?

To check peer agent status, query the Gateway API to discover which peers are online or busy. This validates peer availability and handles sessions before initiating direct cross-agent communication.

What is cross-agent messaging via a websocket gateway?

Cross-agent messaging via a websocket gateway is a centralized workflow that discovers peer agents and routes direct messages between them. It replaces fragmented communication by unifying peer discovery and message delivery through a single Gateway endpoint.

How do I send a message to a specific peer agent through a gateway?

Send a message to a specific peer agent through the gateway by executing the peer-send workflow with the target agent-id. The process includes peer validation and session handling to ensure secure direct delivery.

Can I coordinate multi-agent workflows by checking peer availability first?

Yes, you can coordinate multi-agent workflows by first querying peer status to check availability. The Gateway API identifies which peers are online or busy, allowing you to validate readiness before messaging selected peers.

Are there safety checks to prevent unauthorized messaging across agents?

Yes, basic safety checks are implemented to prevent unauthorized cross-agent messaging. The Gateway integration includes peer validation and session handling to ensure messages are only sent to authorized and available peers.