fipa-00037-communicative-act-library

Select FIPA communicative acts using feasibility preconditions and rational effects.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill fipa-00037-communicative-act-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fipa-00037-communicative-act-library
Source: https://github.com/curiositech/port-daddy/tree/main/skills/fipa-00037-communicative-act-library
Command: npx skills add https://github.com/curiositech/port-daddy --skill fipa-00037-communicative-act-library

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Agents in distributed systems need a principled way to choose what messages to send, how to route them, and how to recover when coordination fails; this Skill provides formal decision rules and patterns grounded in the FIPA Communicative Act Library to remove guesswork from multi-agent messaging design.

Core Features & Use Cases

  • Act selection decision trees for selecting inform, request, query-if, query-ref, confirm, disconfirm, refuse, failure, and not-understood based on sender/receiver mental states.
  • Federation and routing guidance for proxying, propagation, and store-and-forward patterns when agents are not directly reachable.
  • Failure and recovery patterns including explicit refuse/failure handling, timeout strategies, and cancellation/cleanup protocols.
  • Compositional action expressions for building query-if, inform-if, inform-ref, subscribe, and Contract Net–style interactions from small primitives.
  • Use Case: designing or debugging an orchestrator that must request work from heterogeneous autonomous agents while avoiding duplicate work, handling refusals, and recovering from failed attempts.

Quick Start

Ask the skill to "Recommend the appropriate FIPA communicative act and fallback strategy for requesting a long-running computation from an autonomous worker that may refuse or time out."

Frequently Asked Questions about fipa-00037-communicative-act-library

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

FAQPage Schema
How do I choose the right FIPA communicative act for multi-agent messaging?

Choosing the right FIPA communicative act requires evaluating sender and receiver mental states using feasibility preconditions and rational effects to select actions like inform, request, query-if, or refuse. Decision trees map mental-state conditions to specific acts, ensuring agents exchange messages that accurately reflect their knowledge and intentions.

What's the best way to handle failure and recovery in multi-agent communication protocols?

Handling failure in multi-agent communication protocols involves explicit refuse, failure, and not-understood acts combined with timeout strategies and cancellation procedures. Recovery patterns guide agents through cleanup protocols, preventing deadlocks when coordination fails or autonomous workers become unresponsive.

How do I build complex agent interactions from FIPA communicative act primitives?

Building complex agent interactions uses compositional action expressions to combine small FIPA primitives like query-if and confirm into higher-level patterns such as subscribe or Contract Net interactions. This compositional approach enables structured protocol design from reusable messaging components.

Can I use FIPA communicative acts for agent federation and message routing?

FIPA communicative acts support agent federation and message routing through proxy, propagation, and store-and-forward patterns for scenarios where agents are not directly reachable. These routing strategies ensure message delivery across distributed autonomous agent networks despite connectivity gaps.

When should I use refuse versus failure acts in multi-agent protocol design?

Use the refuse act when an agent cannot or will not attempt a requested action due to unmet preconditions, and the failure act when an attempted action was performed but did not succeed. Distinguishing these acts allows orchestrators to implement appropriate fallback and retry strategies.

How do I design an orchestrator protocol for heterogeneous autonomous agents?

Designing an orchestrator protocol for heterogeneous autonomous agents requires combining request acts with explicit refuse handling, timeout strategies, and duplicate work prevention patterns. Rational effect modeling ensures the orchestrator tracks agent commitments and mental states throughout task delegation.