red-gains

Renders rsp usage-gains telemetry reports with token savings, latency percentiles, and degradation history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers whether the rsp wrapper is actually paying for itself by turning raw RedDB telemetry into a readable gains report, so you can see token savings, latency, and health trends without querying the store by hand. ## Core Features & Use Cases - Usage-Gains Report: Runs rsp gains [--since 28d] and summarizes trend, anomalies, the top token-saving command, and health degradation. - Telemetry Breakdown: Surfaces latency percentiles per command family, throughput heatmaps by hour and weekday, weekly tokens saved, and elision rates from the shared RedDB store. - Empty and Short Windows: Treats empty stores as definitive states and labels short windows (e.g. "window: 28d, data: 3d") so requested versus available history stays clear. - Use Case: After a month of running rsp-wrapped commands, invoke /red-gains to check week-over-week token savings and confirm no degradation events hurt latency. ## Quick Start Ask the agent to run /red-gains to show the rsp usage-gains report for the last 28 days.

Frequently Asked Questions about red-gains

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

FAQPage Schema
How do I check whether rsp is saving tokens?▼

Invoke /red-gains or run `rsp gains --since 28d` from the repo. The report shows weekly tokens saved, week-over-week delta, elision rate, and which wrapped command family saves the most tokens.

What metrics does the rsp gains report include?▼

The report covers latency percentiles globally and per command family, throughput per day with hour-by-weekday activity, weekly token savings with elision rate, and a degradation timeline with cold-boot and warm-hit counts.

Why does the rsp gains report show no telemetry?▼

An empty store is a definitive state, not an error, and is reported as no rsp telemetry in this window. Short windows are normal after setup or pruning, shown as requested history versus available history like window: 28d, data: 3d.

Can I change the time window of the gains report?▼

Yes, pass a --since argument such as --since 28d to the rsp gains command. The window.label value in the output distinguishes the requested history from the data actually available in the store.

Where does rsp gains read its telemetry data from?▼

It reads the rsp_telemetry_invocations_v1 and rsp_telemetry_degradations_v1 tables from the shared RedDB store and emits the results as TOON for summarization.