langfuse-monitoring — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited langfuse-monitoring (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill covers operating the data once it's in Langfuse: visualizing it (dashboards), extracting it (metrics API), analyzing eval scores (score analytics), and alerting. It does not cover emitting the data (that's instrumentation — vendored langfuse skill) or designing the scores (that's the langfuse-evaluation skill).
exact UI steps and API schemas, fetch live docs by appending .md to the page URL (e.g. https://langfuse.com/docs/metrics/features/metrics-api.md).
be on the traces to slice by them. If a needed dimension is missing, the fix is upstream (instrumentation → vendored langfuse skill), not here.
Identify the metric family — cost, latency, quality, or volume — and the dimensions to slice by (trace name/feature, user, model, tags, release). See references/dashboards.md for the metric/dimension model.
build custom widgets. references/dashboards.md.
references/metrics-api.md (use v2).references/score-analytics.md.
For a new production app, stand up the three durable dashboards (production health, cost optimization, quality/UX) from references/dashboards.md.
Disambiguate first: Spend Alerts = your Langfuse Cloud bill, not app cost. For app-level cost/latency/quality alerts, build a Metrics-API-driven check. See references/alerting.md.
model, and the three standard dashboards to build (health / cost / quality).
(view/metrics/dimensions/filters/timeDimension), and v1→v2 migration gotchas.
and judge-vs-human agreement metrics (MAE/RMSE, Cohen's Kappa/F1).
API + your own check); how to alert on cost/latency/quality.
| Need | Where |
|---|---|
| Dashboards, metrics extraction, score analytics, alerting | this skill |
| Emitting cost/latency/userId/tags on traces (instrumentation) | vendored langfuse skill |
| Designing the scores/evaluators being monitored | langfuse-evaluation skill |
| Onboarding-time spend-alert setup / production-readiness checklist | langfuse-setup skill |
| Formal judge calibration (vs lightweight score analytics) | vendored langfuse skill judge-calibration.md |
| Exact dashboard UI / metrics API schema | live docs (.md-append) |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.