evaluate-otel-maturity

Inspect telemetry data, documentation, and source code to assess OpenTelemetry maturity per dimension.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/salaboy/otel-eval --skill evaluate-otel-maturity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluate-otel-maturity
Source: https://github.com/salaboy/otel-eval/tree/main/.agents/skills/evaluate-otel-maturity
Command: npx skills add https://github.com/salaboy/otel-eval --skill evaluate-otel-maturity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate a CNCF project's OpenTelemetry maturity by inspecting telemetry data, documentation, and source code. It provides a structured per-dimension assessment using the OpenTelemetry Support Maturity Model to guide improvements.

Core Features & Use Cases

  • Evidence-based evaluation across traces, metrics, and logs from the evaluation cluster to surface concrete observations.
  • Actionable recommendations aligned with the maturity model to inform roadmaps, governance, and telemetry strategy.
  • Use Case: Teams can generate an EVALUATION.md report for stakeholders after telemetry is flowing.

Quick Start

Provide the project-name to begin the OpenTelemetry maturity evaluation.

Frequently Asked Questions about evaluate-otel-maturity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a CNCF project's OpenTelemetry maturity?

You can evaluate OpenTelemetry maturity by inspecting telemetry data, documentation, and source code to produce a structured per-dimension assessment. This generates an EVALUATION.md report with actionable recommendations aligned with the maturity model.

What is the OpenTelemetry maturity model assessment process?

The OpenTelemetry maturity model assessment inspects traces, metrics, and logs alongside documentation notes to justify each evaluated dimension. It provides evidence-based observations from the evaluation cluster to surface concrete telemetry data findings.

Do I need telemetry data flowing before assessing OpenTelemetry maturity?

Yes, telemetry must be flowing in the evaluation cluster before applying the maturity evaluation. The assessment requires traces.jsonl, metrics.jsonl, and logs.jsonl files as input evidence to justify each dimension's structured rating.

Can I generate an OpenTelemetry evaluation report for stakeholder roadmaps?

Yes, you can generate an EVALUATION.md report containing actionable recommendations aligned with the maturity model. This evidence-based assessment informs roadmaps, governance decisions, and telemetry strategy for project stakeholders.

What telemetry formats are required for OpenTelemetry maturity evaluation?

The OpenTelemetry maturity evaluation requires traces.jsonl, metrics.jsonl, and logs.jsonl files generated from the evaluation cluster. These JSON Lines files provide the concrete telemetry evidence used to justify each assessment dimension.

How does OpenTelemetry maturity evaluation handle source code and documentation inspection?

OpenTelemetry maturity evaluation inspects source code and documentation notes alongside telemetry data to justify each dimension. This comprehensive inspection aligns findings with the maturity model requirements and provides evidence for the final assessment report.