SKILLEMALL.ai
GitHub ↗ RU Sign in

BD 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/claude-flow Claude Code author: ruvnet MIT 1 file body ≈ 346 tokens Open the sourcegithub.com↗ analyzed 31 h ago

Show AGNTCY/SLIM/CASA integration status — whether upstream AGNTCY packages are installed, which transport (local vs SLIM) is active, and whether CASA…

As a process D 39/100 · Unfinished process — References files that are not bundled: ../../docs/adrs/ADR-380-agntcy-outshift-runtime-integration.md

IntegrationInfrastructureSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: ../../docs/adrs/ADR-380-agntcy-outshift-runtime-integration.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/adrs/ADR-380-agntcy-outshift-runtime-integration.md

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: ../../docs/adrs/ADR-380-agntcy-outshift-runtime-integration.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/adrs/ADR-380-agntcy-outshift-runtime-integration.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 5 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 346 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +4Structure: 0 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 287: enough signal without eating the budget
  • +3Step-by-step instructions: 5 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.