SKILLEMALL.ai

BF telemetry

Operate the observability stack that deploys as one unit: Prometheus scrape configuration, recording and alerting rules, relabeling, retention, and high availability; OpenTelemetry Collector pipelines (receivers, processors, exporters, sampling, trace/span correlation); and Loki ingest, LogQL, retention, and label design — with a bundled read-only telemetry-check script for Prometheus rule sanity and scrape-target reachability. Use when running, tuning, or troubleshooting a Prometheus, OpenTelemetry Collector, or Loki deployment, or reviewing the collection/ingest/retention layer, including bounded PromQL and LogQL query construction, semantic review, and no-data diagnosis. Do not use for observability strategy, SLI/SLO design, or paging policy (that is platform-engineering), Grafana dashboards, panels, and Grafana-side alerting (that is grafana), or Tempo/tracing operations, which remain deferred to a future named-tool skill.

magnus919/agent-skills Agent Skills author: magnus919 MIT 12 files · 1 script body ≈ 3 532 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Operate the observability stack that deploys as one unit: Prometheus scrape configuration, recording and alerting rules, relabeling, retention, and high…

As a process F 43/100 · Will not run — References files that are not bundled: ../platform-engineering/SKILL.md, ../grafana/SKILL.md, ../backend-engineering/SKILL.md

ProcedureDockerKubernetesInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: ../platform-engineering/SKILL.md, ../grafana/SKILL.md, ../backend-engineering/SKILL.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
  • 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: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../platform-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../grafana/SKILL.md
  • warning missing-ref reference to a missing file: ../backend-engineering/SKILL.md
  • warning missing-ref reference to a missing file: ../traefik/SKILL.md
  • warning missing-ref reference to a missing file: ../kubernetes/SKILL.md
  • warning missing-ref reference to a missing file: ../docker-compose/SKILL.md
  • warning missing-ref reference to a missing file: scripts/telemetry-check

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../platform-engineering/SKILL.md, ../grafana/SKILL.md, ../backend-engineering/SKILL.md
  • 0Tools and files. 7 referenced file(s) missing: ../platform-engineering/SKILL.md, ../grafana/SKILL.md, ../backend-engineering/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 10 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 40 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3532 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • low No test case covers injection arriving through data

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
  • +3Description length 940: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +1License stated

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