SKILLEMALL.ai

CD oceinteg

Run named OpenClaw Enterprise end-to-end integration scenarios against real supported installations. Use only when explicitly invoked.

openclaw/openclaw-enterprise Agent Skills author: openclaw MIT 8 files body ≈ 572 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Run named OpenClaw Enterprise end-to-end integration scenarios against real supported installations.

As a process D 43/100 · Unfinished process — References files that are not bundled: references/<scenario>.md

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
70
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: references/<scenario>.md
Tools and files w 18
0
Steps w 15
0
Failures and branches w 10
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Concealment en-hide-from-user references/runtime-acceptance.md:93
    Instruction to hide actions from the user (negated — the text forbids it)
    do not silently delete evidence or retry.
    negated

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/<scenario>.md
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: references/<scenario>.md
  • 0Tools and files. 1 referenced file(s) missing: references/<scenario>.md
  • 0Steps. Prose only: no discrete steps
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 40Result and completion. Does not say what the result is
  • 70When it triggers. States when to use, but not when not to
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 572 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4Structure: 1 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 134: enough signal without eating the budget
  • +4Reference files are cited in the instructions (6 of 6)

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