How do I install the Agntcy Status skill?

Run npx skillmds@latest add ruvnet/agntcy-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agntcy Status safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agntcy Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agntcy Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agntcy Status?

ruvnet (@ruvnet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agntcy Status by ruvnet — Agent Skill

Name: Agntcy Status
Rating: 4.2 (5 reviews)
Author: ruvnet

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?".

ruvnet eeda81c 1.7 KB Updated Sep 9, 2026

File contents

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 Rust ruflo-agntcy crate are installed as optionalDependencies, 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_at currently 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 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.

Frequently asked questions