release-metrics

Name: release-metrics
Availability: InStock
Author: Lodekeeper

Compare beta and stable release metrics using Grafana and Prometheus data.

4|1|Updated Feb 20, 2026

Search Tags:#performance #monitoring #stability #metrics #release #lodestar #release candidate

Ready to run

npx skills add https://github.com/lodekeeper/dotfiles --skill release-metrics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-metrics
Source: https://github.com/lodekeeper/dotfiles/tree/main/skills/release-metrics
Command: npx skills add https://github.com/lodekeeper/dotfiles --skill release-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, data-driven approach to evaluating the readiness of Lodestar release candidates by comparing their performance and stability metrics against established baselines.

Core Features & Use Cases

Comparative Analysis: Compares key performance indicators (KPIs) of release candidates (RCs) against stable versions.
Automated Health Checks: Covers node health, validator performance, resource utilization, and network quality.
Use Case: Before deploying a new RC to mainnet, use this Skill to analyze its performance over a 72-hour period on beta nodes, ensuring it meets or exceeds the stability and efficiency of the current stable release.

Quick Start

Evaluate the release candidate metrics by comparing the 'beta' group against the 'stable' group over the last 7 days.

Frequently Asked Questions about release-metrics

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

FAQPage Schema

How do I evaluate Lodestar release candidate readiness before mainnet deployment?▼

Evaluate Lodestar release candidate readiness by comparing beta and stable node groups over a 72-hour period. This Skill queries Grafana and Prometheus monitoring stacks to analyze health checks, performance, memory, and networking metrics for data-driven release decisions.

What metrics should I monitor for Ethereum consensus client release stability?▼

Monitor node health, validator effectiveness, memory utilization, networking quality, and PeerDAS metrics for Ethereum consensus client release stability. This Skill extracts these KPIs from Prometheus and Grafana data to compare release candidates against stable baselines.

Can I use Grafana and Prometheus data to compare beta and stable Lodestar nodes?▼

Yes, you can use Grafana and Prometheus data to compare beta and stable Lodestar nodes. This Skill requires access to the Lodestar monitoring stack to query and analyze comparative performance, stability, and resource utilization metrics between node groups.

How do I analyze validator effectiveness and PeerDAS metrics for a release candidate?▼

Analyze validator effectiveness and PeerDAS metrics by querying the Lodestar monitoring stack over a specified time window. This Skill processes Prometheus data to compare these networking and performance indicators against the current stable release baseline.

What are the limitations of using automated health checks for release candidate evaluation?▼

A limitation of using automated health checks for release candidate evaluation is the requirement for an active Lodestar monitoring stack with Grafana and Prometheus. Without this infrastructure deployed on beta nodes, the Skill cannot retrieve the data needed for comparative analysis.