OpenParable
Skip to content
← Back to skills

Skippy Metrics

DevOps & Security
skippy-metrics

Skippy Metrics is an Agent Skill for devops & security published in the Mesh-LLM/mesh-llm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Mesh-LLM/mesh-llm/blob/HEAD/.agents/skills/skippy-metrics/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/skippy-metrics, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

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.