SKILLEMALL.ai

BC query-metrics

Runs metrics queries against Axiom MetricsDB via scripts. Discovers available metrics, tags, and tag values. Use when asked to query metrics, explore metric datasets, check metric values, or investigate OTel metrics data.

openclaw/clawhub Agent Skills author: openclaw MIT 2 files body ≈ 2 559 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Runs metrics queries against Axiom MetricsDB via scripts.

As a process C 54/100 · Has gaps — References files that are not bundled: scripts/<name>, scripts/metrics-spec, scripts/setup

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
54/100
Has gaps
References files that are not bundled: scripts/<name>, scripts/metrics-spec, scripts/setup
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/<name>
  • warning missing-ref reference to a missing file: scripts/metrics-spec
  • warning missing-ref reference to a missing file: scripts/setup

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: scripts/<name>, scripts/metrics-spec, scripts/setup
  • 0Tools and files. 3 referenced file(s) missing: scripts/<name>, scripts/metrics-spec, scripts/setup
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 14 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 15 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2559 tokens
  • low The response is described with custom markup (39 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 221: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 15 items
  • +3Output format is stated explicitly
  • +4Has examples (6 code blocks)

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