agntcy-status
Show AGNTCY/SLIM/CASA integration status — whether upstream AGNTCY packages are installed, which transport (local vs SLIM) is active, and whether CASA enforcement is enabled. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?".
Scaffolding stub — not yet implemented. This skill will report, once ruflo-agntcy ships real logic (see ADR-380):
- Package availability — whether
@claude-flow/agntcy(TS) and/or the Rustruflo-agntcycrate are installed asoptionalDependencies, or absent (the expected default today — no such upstream package exists yet publicly). - Active transport — local in-process (default) vs SLIM (opt-in, per ADR-380 §2), and which swarms/hive-mind sessions are on which transport.
- CASA enforcement state — enabled/disabled, and for enabled tenants, the compiled intent envelope's
allow/deny/budget_usd/expires_atcurrently in force (ADR-380 §3). - IOC coordination events — whether optional Layer 9 semantic events (ADR-380 §4) are wired on top of
hive-mind_broadcast/hive-mind_consensus. - Identity/observability — whether AGNTCY OTel span attributes (
agent.identity,coordination.episode,authorization.decision, etc., ADR-380 §5) are being emitted throughruflo-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.
Loading supporting files
ruvnet/claude-flow · MIT · Revision 005a0ed25e64
Be the first to comment
Share what worked or leave a question for the creator.