skill-analytics

Aggregate Aeon skill run snapshots into weekly fleet analytics reports.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill skill-analytics-aaronjmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-analytics
Source: https://github.com/aaronjmars/aeon/tree/main/skills/skill-analytics
Command: npx skills add https://github.com/aaronjmars/aeon --skill skill-analytics-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It converts raw per-run skill outcomes into a single weekly, fleet-level report so operators can quickly see what’s running most, what’s failing most, what’s quietly skipping, and which scheduled skills never fired.

Core Features & Use Cases

  • Fleet-wide ranking: Produces a ranked view of every skill with runs in the selected time window, including success/failure counts and last status.
  • Silent scheduled detection: Detects cron-enabled skills that appear active in configuration but have zero runs in the window.
  • Exit taxonomy distribution: Mines daily logs to surface how often skills end in ok/quiet/skip/new-info/skip/partial/error buckets, distinguishing degraded “quiet correctness” from true failures.
  • Anomaly-first reporting: Flags anomalies using significance gating and prioritizes the strongest verdict for operator attention, writing both an article and a dashboard JSON spec.

Quick Start

Run the skill with the default 7-day window to generate a fleet analytics report covering your latest skill runs and anomalies.

Frequently Asked Questions about skill-analytics

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

FAQPage Schema
How do I detect silent failures in scheduled GitHub Actions workflows?

Fleet monitoring detects silent failures by aggregating run snapshots and cron scheduling expectations, identifying cron-enabled skills with zero runs in the selected time window. This flags scheduled skills that appear active but never actually fired.

What is exit taxonomy distribution in skill observability?

Exit taxonomy distribution mines daily logs to categorize skill outcomes into buckets like ok, quiet, skip, partial, and error. This distinguishes degraded quiet correctness from true failures, revealing how frequently skills end in skip-class outcomes versus hard errors.

How do I generate a weekly fleet-level analytics report for Aeon skills?

Run the analytics skill with the default 7-day window to aggregate run snapshots, cron streak signals, and exit taxonomy data. It produces a ranked top-runner view, failure-rate breakdown, and anomaly-gated verdict written to articles and dashboard JSON outputs.

Can I diagnose degraded success rates across a fleet of scheduled skills?

Yes, fleet-wide ranking produces a view of every skill with runs in the window, including success and failure counts plus last status. Anomaly-first reporting applies significance gating to flag degraded success rates and prioritizes the strongest verdict for operator attention.

What's the best way to monitor cron schedule streaks and detect missed runs?

Aggregate cron-state streak signals alongside run snapshots to detect scheduled skills with zero runs in the window. This best-effort approach compares expected cron schedules against actual execution frequency to surface missed or silently failing runs.

Why do some scheduled skills show as active but have no run history?

Silent scheduled detection identifies cron-enabled skills that appear active in configuration but have zero runs in the window. This occurs when skills are misconfigured, blocked, or failing to trigger, requiring aggregation of cron scheduling expectations against actual run snapshots.