# Skippy Metrics

> Use this skill when working on skippy telemetry attributes, OTLP emission, benchmark metric names, runtime lifecycle telemetry, or separating telemetry/reporting ownership from stage runtime serving.

- Skill: `mesh-llm/skippy-metrics` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mesh-llm/skippy-metrics`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mesh-llm/skippy-metrics/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mesh-llm (https://skillmd.com/u/mesh-llm)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mesh-llm/skippy-metrics

---


# skippy-metrics

Use this skill for telemetry attributes, lifecycle instrumentation, and
benchmark/report integration.

## Ownership

`crates/skippy-metrics` owns shared attribute names. Stage servers may emit
OTLP/telemetry, but request-path serving must not block on telemetry export.
`crates/metrics-server` owns benchmark/debug telemetry ingest, SQLite storage,
run lifecycle, and canonical report export.

Mesh API runtime status is not a telemetry dump. Keep public runtime status
backend-neutral and stable; expose backend details only when intentionally part
of the status shape.

## Validation

```bash
cargo test -p skippy-server --lib
cargo test -p mesh-llm --lib
```

Keep canonical benchmark report export in `metrics-server` rather than inside
stage serving.