CD axiom-alerting
Create and manage Axiom monitors and notifiers via the v2 public API. Use when building alerting, routing notifications, validating monitor behavior, and maintaining alert configurations end-to-end.
Create and manage Axiom monitors and notifiers via the v2 public API.
As a process D 48/100 · Unfinished process — References files that are not bundled: scripts/setup, scripts/notifier-create
How to improve
- The text references files that are not there: add them or drop the references.
- 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 Exfiltration
exfil-webhook-urlSKILL.md:208Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"slackUrl": "https://hooks.slack.com/services/T.../B.../XXX"
placeholder
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/setup - warning
missing-refreference to a missing file: scripts/notifier-create
Process rating: all ten parameters 48/100
- 0Tools and files. 2 referenced file(s) missing: scripts/setup, scripts/notifier-create
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 50 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 95 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2047 tokens
- low 11 top-level sections: this looks like several domains in one skill
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 198: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 95 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.