operator-scorecard

Synthesizes agent health, community growth, and economic activity into weekly verdict scorecards.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon-bd --skill operator-scorecard-aaronjmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: operator-scorecard
Source: https://github.com/aaronjmars/aeon-bd/tree/main/skills/operator-scorecard
Command: npx skills add https://github.com/aaronjmars/aeon-bd --skill operator-scorecard-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operators of an autonomous agent fleet must open multiple report files (skill-health analytics, heartbeat logs, tweet-allocator totals, repo-pulse deltas) to assemble a weekly picture of whether the agent's work was worth it. This Skill consolidates those scattered signals into a single scorecard, ops day-recap, or push deep-dive with a clear OK/WATCH/DEGRADED verdict. ## Core Features & Use Cases - Weekly operator scorecard: Synthesizes agent health, community growth, and economic activity from existing skill output files into a three-paragraph verdict article, dashboard JSON spec, and notification. - Ops day recap: Summarizes one day of agent activity — what shipped, what failed, what needs a human decision — with deduplication, silent-failure detection via cron-state, and a mandatory TL;DR. - Push recap: Reads commit diffs and merged PRs from watched GitHub repos, classifies commits as user-visible/internal/infra, ranks impact, and suppresses quiet days. - Use Case: On Monday morning, run the default scorecard mode to receive a notification with the week's fleet success rate, star/fork growth, $AEON distribution totals, and a worst-of-three verdict, without opening four separate report files. ## Quick Start Run the operator-scorecard skill with an empty argument to generate this week's scorecard, or pass 'ops' for a daily operational recap or 'push' for a commit-level push recap.

Frequently Asked Questions about operator-scorecard

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

FAQPage Schema
How do I generate a weekly agent activity scorecard?▼

Run the skill with an empty argument to synthesize the last 7 days into a scorecard covering agent health, community growth, and economic activity. Pass an integer like 336 to override the window in hours, or prefix with dry-run to skip the notification.

How to recap what an autonomous agent shipped in one day?▼

Use the ops branch by passing 'ops' as the first token, optionally with a date like 'ops 2026-06-30'. It reads the day's activity log and cron-state, deduplicates repeat runs, demands a URL on every shipped item, and leads with a one-sentence TL;DR verdict.

Does the scorecard work if upstream skills never ran?▼

Yes, it degrades gracefully. Missing source files mark the matching lane as INSUFFICIENT_DATA rather than fabricating numbers, and if every lane lacks data it exits with OPERATOR_SCORECARD_NO_DATA without overwriting the article.

Can I recap pushes for only one GitHub repository?▼

Yes, pass a repo scope after the push keyword, such as 'push owner/repo', to restrict the recap to that repository. With an empty argument it recaps all repos listed in memory/watched-repos.md.

Why did the push recap send no notification?▼

The push branch has a significance gate: after filtering bot commits, if no meaningful pushes remain across watched repos it logs PUSH_RECAP_QUIET and stops without notifying. This prevents quiet days from flooding the channel.