dashboard

Displays RedSkills operational metrics from GitHub issues and local AFK worker state.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill dashboard-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dashboard
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/dashboard
Command: npx skills add https://github.com/reddb-io/red-skills --skill dashboard-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams using RedSkills lack a single view of process health: open Specs, running autonomous workers, issue flow, and delivery metrics are scattered across GitHub and local machine state. This Skill aggregates them into one operational dashboard. ## Core Features & Use Cases - Operational Dashboard: Calls the dashboard tool on the rs_dev MCP to present issue, Spec, AFK worker, and PR flow metrics in a structured TOON result. - DORA-Proxy Metrics: Reports release frequency, lead time for changes, change-failure-rate proxy, and MTTR proxy derived from issue labels and dates. - Worker Visibility: Shows global running workers (issues labelled running) plus live, stale, and total local AFK worker state files on the current machine. - Use Case: A team lead asks "show me this week's RedSkills metrics" and gets open Specs, cycle time, PR lead time, and due-date tracking for the selected period in one report. ## Quick Start Ask the assistant to show the RedSkills dashboard for the last 14 days, or invoke /dashboard with a period argument such as --period 14d.

Frequently Asked Questions about dashboard

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

FAQPage Schema
How do I see RedSkills process metrics and running workers?▼

Invoke /dashboard or ask for RedSkills process metrics. The Skill calls the dashboard tool on the rs_dev MCP and presents open Specs, issues, running workers, cycle time, and DORA-proxy metrics for the selected period.

How to track DORA metrics from GitHub issues?▼

The dashboard computes DORA proxies from GitHub issue data: release frequency, lead time for changes, change-failure rate, and MTTR. These depend on labels like type:bug, regression, incident, and blocked:validation, and are explicit proxies rather than compliance claims.

Can I change the dashboard reporting period?▼

Yes, pass a period argument such as --period 14d or --period 30. The dashboard tool accepts a periodDays parameter that defaults to 30 days and controls issue closure and flow metric windows.

Why is the dashboard not showing any metrics?▼

The dashboard requires the rs_dev MCP to be reachable. If it is unreachable, the Skill reports the failure and directs repair of the daemon or plugin load; there is no fallback implementation of the report.

What are the limitations of the DORA proxy metrics?▼

The DORA values are proxies, not compliance claims. Change failure rate and MTTR only work when issues carry labels such as type:bug, bug, regression, incident, type:incident, or blocked:validation.