mcpField
A
agntcy-status

agntcy-status

github.com/ruvnetAgent workflows80.0k42 installsUpdated today
Repository

About agntcy-status

agntcy-status is an unimplemented scaffolding skill intended to report AGNTCY and SLIM configuration, coordination, and observability status. Until the required packages are available, it must report that the feature is not configured rather than imply a healthy state.

Key features

  1. 01Scaffolding stub, not implemented
  2. 02Planned package availability checks
  3. 03Planned transport and policy status
  4. 04Planned coordination and telemetry status

Use cases

  1. 01Identify whether AGNTCY packages are available
  2. 02Check planned transport and CASA policy state
  3. 03Review planned coordination events and identity telemetry

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ruvnet/ruflo --skill agntcy-status

After installing, type/agntcy-statusin Claude Code to confirm it loaded.

Details

From the project README

Scaffolding stub — not yet implemented. This skill will report, once ruflo-agntcy ships real logic (see ADR-380):

  1. Package availability — whether @claude-flow/agntcy (TS) and/or the Rust ruflo-agntcy crate are installed as optionalDependencies, or absent (the expected default today — no such upstream package exists yet publicly).
  2. Active transport — local in-process (default) vs SLIM (opt-in, per ADR-380 §2), and which swarms/hive-mind sessions are on which transport.
  3. CASA enforcement state — enabled/disabled, and for enabled tenants, the compiled intent envelope's allow/deny/budget_usd/expires_at currently in force (ADR-380 §3).
  4. IOC coordination events — whether optional Layer 9 semantic events (ADR-380 §4) are wired on top of hive-mind_broadcast/hive-mind_consensus.
  5. Identity/observability — whether AGNTCY OTel span attributes (agent.identity, coordination.episode, authorization.decision, etc., ADR-380 §5) are being emitted through ruflo-observability.

Until upstream AGNTCY/SLIM packages exist, this status check MUST report "not configured — see ADR-380" rather than fabricate a healthy status. No network call to AGNTCY infrastructure (Directory, SLIM broker) is safe to make from this skill until a real client library is available.

Comments

Markdown supported