Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.
Show AGNTCY/SLIM/CASA integration status — whether the optional SLIM runtime package is installed, whether a SLIM endpoint is configured, which transport is the default, and what the agntcy mod has seen this session. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?". Read-only; makes no network call.
Summarizes locally available information about AGNTCY configuration and implementation in a short table. It checks whether a SLIM endpoint is configured, whether @agntcy/slim-bindings is installed, the transport mode, and mod counters such as calls and blocked calls. Items that cannot be determined are marked unknown. It also distinguishes implemented features from unfinished work involving CASA, IOC, and identity information.
Use it to check whether you have configured AGNTCY or have the settings and package needed for SLIM. Reviewing the project's mod execution records helps you avoid treating configuration alone as proof that the entire integration is active.
Checks are read-only and make no network calls. Endpoint values are hidden; only their presence is reported. The default transport is local, and connectivity is not tested. The material describes a CASA compiler, but runtime enforcement is not connected to the CLI. Layer 9 events and OTel attributes are unimplemented.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Report what can be measured on this machine, and say "unknown" for anything that cannot. Never invent a healthy status.
test -n "$RUFLO_AGNTCY_SLIM_ENDPOINT" && echo set || echo unset. Report only set or unset; do not print the value (an endpoint can carry credentials).npm ls @agntcy/slim-bindings 2>&1 | tail -3 from the project root. (empty) or ERR! missing means not installed (the supported default: the package is an optionalDependency). Do not import() it from the shell; resolving a package runs its code.ruflo transport with no arguments only prints help, and ruflo transport use slim is a switch that contacts the configured endpoint, so do not run it just to check status. Report "local (default)" unless the user says they switched.Read .claude-flow/agntcy-mod/status.json if it exists (calls, blocked, guard, updatedMs). Missing file means the mod has not run in this project yet.src/casa), but runtime enforcement is not wired into the ruflo CLI (no CASA reference in v3/@claude-flow/*/src), and Layer 9 events and OTel attributes are design items in ADR-380 §§4-5. Report these as "compiler present, enforcement not wired in the CLI" and "not implemented"; do not report them as enabled.One short table: endpoint (set/unset), package (installed version or absent), transport (local/slim), mod counters, CASA/IOC/identity (state from step 5). If the endpoint is set but the package is absent, say the transport falls back to local and point to ADR-380 §1 for setup.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.