skill-analytics

Generates fleet-level analytics ranking scheduled skills by run count, success rate, and anomaly flags.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill skill-analytics-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-analytics
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/skill-analytics
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill skill-analytics-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operators running many scheduled automation skills lack a single ranked, fleet-wide view: per-run heartbeats show only binary ok/not-ok, and per-skill health checks audit one skill at a time, so silent skills, failure streaks, and skip-heavy behavior go unnoticed. ## Core Features & Use Cases - Fleet-wide ranking: Pulls GitHub Actions run history via a skill-runs script and ranks every skill by run count and success rate over a configurable window (default 7 days). - Anomaly detection: Flags silent scheduled skills, all-fail runs, consecutive failure streaks, low success rates, all-skip behavior, and duplicate runs using a priority-ordered taxonomy. - Exit taxonomy mining: Greps daily logs for markers like SKIP_UNCHANGED and NEW_INFO to distinguish healthy-quiet skills from silently broken ones. - Use Case: An operator with 80 scheduled skills runs this weekly to produce a Markdown report, a dashboard JSON spec, and a significance-gated notification only when anomalies exist. ## Quick Start Run the skill-analytics skill to generate a 7-day fleet report ranking all scheduled skills by runs, success rate, and anomaly flags.

Frequently Asked Questions about skill-analytics

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

FAQPage Schema
How do I monitor success rates across many scheduled GitHub Actions workflows?▼

Run this skill to pull workflow run history via gh api and rank every skill by run count and success rate over a configurable window. It produces a Markdown report and dashboard JSON summarizing the entire fleet in one view.

How to detect scheduled cron jobs that silently stopped running?▼

The skill cross-references aeon.yml cron schedules against actual run history and flags any enabled cron skill with zero runs in the window as SILENT. Skills with workflow_dispatch or reactive schedules are exempt since they fire on demand.

Can I change the analytics time window from 7 days?▼

Yes, pass an integer number of hours as the var parameter, such as 72 for a three-day window. The window defaults to 168 hours and is capped at 720 hours to keep gh api pagination fast.

Why does the skill send no notification some weeks?▼

Notifications are significance-gated: if zero anomalies are detected, the skill exits QUIET and sends nothing. The Markdown article and dashboard JSON are still written so the dashboard reflects current fleet state.

What happens when the run history fetch fails or returns empty?▼

The skill logs SKILL_ANALYTICS_NO_DATA and stops without writing a report or notifying. It never synthesizes data from cron-state alone, since that would produce a misleading fleet view.