Monitoring Dashboard Audit
PassAudited by ClawScan on May 10, 2026.
Overview
This read-only monitoring audit skill is coherent and purpose-aligned, but it uses Grafana/Prometheus access and broad read queries that should be scoped carefully.
Use this skill only with authorized Grafana, Prometheus, and Alertmanager environments. Provide least-privilege read-only tokens, review broad inventory or cardinality queries before running them, and avoid sharing generated audit outputs because they may contain infrastructure and alerting details.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Using the skill may reveal a wide dashboard and monitoring inventory, and broad queries could add load if run carelessly.
The skill documents shell/API commands that can enumerate large portions of a Grafana environment. These are read-only and aligned with the audit purpose, but broad commands should be run only against intended systems.
curl -s -H "Authorization: Bearer $GRAFANA_TOKEN" \ "$GRAFANA_URL/api/search?type=dash-db&limit=5000"
Review commands before execution, run them only against authorized monitoring systems, and avoid expensive Prometheus queries during peak periods.
If an over-privileged token is used, the agent may access more monitoring or account information than needed for the audit.
The skill expects delegated Grafana access via a bearer token. This is normal for a Grafana audit, but the token controls what dashboards, alerts, and data source metadata can be read.
Grafana access — API token or service account with Viewer role minimum (`grafana_url` and `Authorization: Bearer <token>` header confirmed working)
Use a dedicated read-only Viewer service account or token, avoid admin credentials, and rotate or revoke the token after the audit if appropriate.