fipa-00023-agent-management

Define canonical FIPA Agent Management patterns for naming, registering, discovering, and recovering agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Multi-agent platforms struggle with brittle discovery, identity/location conflation, undocumented lifecycle transitions, and undifferentiated failures that cause race conditions, stale routing, and failed recoveries. This Skill codifies the FIPA Agent Management patterns to separate identity from address, split authoritative lifecycle/identity management (AMS) from non-authoritative capability directories (DF), and provide a structured exception and lifecycle model so orchestrators can discover, invoke, and recover agents reliably.

Core Features & Use Cases

  • AMS / DF separation: Prescribes a white-pages AMS for authoritative lifecycle and identity and a yellow-pages DF for capability advertisement and federated search.
  • AID-based resolution & federated search: Use immutable AIDs resolved via resolver chains and depth-bounded DF federation for scalable discovery across organizational boundaries.
  • Lifecycle & exception contracts: Formalizes six lifecycle states with transition ownership and a rich exception taxonomy (refuse/failure/not-understood) to enable deterministic retry and recovery strategies.
  • Use case: An orchestrator queries the local DF for a translation capability, falls back to federated DFs when needed, resolves the chosen AID via the AMS to obtain transport addresses, checks lifecycle state before invocation, and applies exception-specific recovery (re-discover, escalate, or treat as idempotent success).

Quick Start

Find active agents that advertise the "translation" service across federated directories, resolve their AIDs to current transport addresses, and return the preferred reachable endpoint for each agent.

Frequently Asked Questions about fipa-00023-agent-management

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

FAQPage Schema
How do I separate agent identity from transport address in a distributed multi-agent platform?▼

Agent identity and transport address separation uses immutable Agent Identifiers (AIDs) resolved through AMS resolver chains, preventing stale routing and identity/location conflation in distributed platforms.

What is the difference between AMS and DF in FIPA agent management?▼

AMS and DF separation distinguishes a white-pages Agent Management System for authoritative lifecycle and identity from a yellow-pages Directory Facilitator for capability advertisement and federated directory searches.

How do I implement federated search for agent capabilities across organizational boundaries?▼

Federated search uses depth-bounded Directory Facilitator (DF) federation to query remote directories for advertised capabilities, enabling scalable agent discovery across organizational boundaries.

What lifecycle states should autonomous agents support for reliable fault recovery?▼

Autonomous agents should support six formalized lifecycle states with defined transition ownership, enabling deterministic retry and recovery workflows when failures or exceptions occur.

How do I handle agent discovery failures and undifferentiated exceptions in multi-agent systems?▼

Agent discovery failures are handled through a structured exception taxonomy categorizing refuse, failure, and not-understood exceptions, enabling orchestrators to apply exception-specific recovery strategies.

Can I use partial-template matching to search for agents by capability in a directory?▼

Partial-template capability search is supported by the Directory Facilitator (DF), allowing orchestrators to query agents by advertised service templates and fall back to federated DFs when local results are insufficient.