skills-status

Diagnose Skill telemetry status and recent Skill usage events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running a self-improvement loop for AI skills, you cannot tell whether telemetry is actually collecting evidence of skill usage. This Skill diagnoses the telemetry state so you know whether skills are being observed before trusting curator recommendations. ## Core Features & Use Cases - Telemetry State Diagnosis: Reports whether Skill telemetry is uninitialized, unavailable, no-op, or enabled, with a concrete remediation for each state. - Usage Event Inspection: When enabled, lists observed skills, recent events, and outcome counts from partitioned rollups. - Pre-Curator Check: Run before the report-only Skill curator to confirm evidence is being collected. - Use Case: Before asking the curator which skills to archive, run this diagnostic to verify graph mode with skill telemetry is active and events exist. ## Quick Start Ask the agent to check the Skill telemetry status and tell you whether skill usage is being observed.

Frequently Asked Questions about skills-status

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

FAQPage Schema
How do I check if Skill telemetry is enabled?▼

Run the skills-status diagnostic, which reports whether telemetry is uninitialized, unavailable, no-op, or enabled. When enabled, it also lists observed skills, recent events, and outcome counts.

How to enable Skill telemetry for the self-improvement loop?▼

If the diagnostic reports uninitialized, run memory init with graph mode and the skill-telemetry flag. For the unavailable state, the explicit skillTelemetry opt-in is off and must be turned on; no-op means graph mode is required.

Should I check telemetry status before running the Skill curator?▼

Yes. Run the diagnostic first so you know whether telemetry is collecting evidence. The Memory plugin's curator is report-only, so its recommendations are only meaningful when usage events exist.

Why does the skills-status diagnostic show no events?▼

Empty events mean telemetry is enabled but no skill use has been observed yet. This is not an error; the command is a read-only diagnostic and exits cleanly in non-enabled states too.

Can the skills-status command modify or archive skills?▼

No. The command is strictly read-only and never mutates skills. To act on archive candidates, use the dev plugin's curate workflow after reviewing the report-only curator output.