fleet-state

Synthesize fleet cohort, release, and contributor outputs into a weekly digest with WoW deltas.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, bash, sort_by.

What problem does it solve?

Weekly “state of the fleet” reporting currently requires manually combining multiple sources (cohort health, release activity, and contributor spotlight) into a single narrative with week-over-week deltas, which is time-consuming and error-prone.

Core Features & Use Cases

  • Fleet-wide weekly synthesis: Produces a single “Fleet State” article that merges cohort bucket totals, shipped-release activity, and spotlight selection into one readable update.
  • Week-over-week deltas: Computes running totals changes (WoW) versus the prior saved snapshot so operators instantly see momentum.
  • Graceful partial availability: Degrades when one or more source topics/articles are missing, avoiding hard failure while still delivering whatever can be assembled.
  • Targeted transitions and highlights: Optionally extracts “movement” and “shipped” highlights from the constituent articles when they are recent enough, and caps entries to keep the digest concise.
  • Configurable context via var: Supports dry-run mode and optional parent repo override without changing the underlying data model.

Quick Start

Run the fleet-state skill with var set to dry-run to generate the weekly Fleet State article and update internal state without sending a notification.

Frequently Asked Questions about fleet-state

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

FAQPage Schema
How do I automate a weekly digest of fork fleet health and releases?

Automate a weekly digest of fork fleet health by synthesizing fork-cohort, contributor-spotlight, and release-tracker outputs into a single narrative article with week-over-week deltas. It merges multiple sources so operators get an immediate view of fleet momentum without manual combination.

Can I generate a state of the fleet report without sending a Telegram notification?

Yes, you can generate a state of the fleet report without sending a notification by running the skill in dry-run mode. This produces the weekly Fleet State article and updates internal state snapshots while gating notifications based on the configured verdict and source availability.

How does week-over-week delta tracking work for GitHub fork reporting?

Week-over-week delta tracking for GitHub fork reporting works by computing running total changes against the prior saved snapshot. It reads specific memory and topics JSON files to calculate momentum metrics, allowing operators to instantly see shifts in cohort bucket totals and shipped-release activity.

What happens to autonomous recurring reporting if one source article is missing?

Autonomous recurring reporting degrades gracefully if one source article is missing. The synthesis avoids hard failure by delivering whatever can be assembled from the available cohort, spotlight, and release data, ensuring operators still receive a partial fleet update.

Do I need jq and bash to compile release tracking and contributor spotlights?

Yes, you need jq and bash alongside gh and sort_by dependencies to compile release tracking and contributor spotlights. These tools parse the required JSON files, extract highlights from constituent articles, and compute the capped entries needed for the concise weekly digest.

What is the best way to merge multiple GitHub fork notifications into one readable update?

The best way to merge multiple GitHub fork notifications into one readable update is using a synthesis workflow that extracts movement and shipped highlights from constituent articles. It caps entries to keep the digest concise and optionally overrides the parent repo context without changing the data model.