fleet-state

Synthesize fork-cohort, release, and contributor data into a weekly fleet-state digest.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill fleet-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-state
Source: https://github.com/anajuliabit/aeon/tree/main/skills/fleet-state
Command: npx skills add https://github.com/anajuliabit/aeon --skill fleet-state

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Fleet operators waste time stitching together multiple weekly agent outputs to understand how the overall fork “fleet” is changing (health buckets, releases, and the current contributor spotlight).

Core Features & Use Cases

  • Weekly synthesis digest: Combines fork-cohort status, release activity, and contributor spotlight into one consistent “state of the fleet” narrative with week-over-week deltas.
  • Graceful degradation: Produces partial output when one or two source state/artifact files are missing, while avoiding hard failures when upstream skills haven’t run.
  • No new data collection: Reads authoritative inputs from existing memory/topics and latest articles, composing insights without re-querying fork repositories.
  • Operator-ready transitions: Extracts movement highlights (bucket transitions), release highlights, and the spotlight summary from recent articles to make Monday readouts actionable.

Quick Start

Run fleet-state with no extra var to generate a weekly digest and notification from the latest fork-cohort, fork-release, and contributor-spotlight data for the parent repo.

Frequently Asked Questions about fleet-state

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

FAQPage Schema
How do I automate weekly status reporting for GitHub fork cohorts?

Automate weekly status reporting by synthesizing existing fork-cohort bucket totals, release activity, and contributor spotlights into a single digest with week-over-week deltas. The process reads memory/topics and latest articles to generate an operator-ready overview without manual stitching.

What is a fleet state digest and when do I need it for release tracking?

A fleet state digest is a weekly synthesis of fork-cohort health buckets, release activity, and contributor spotlights. You need it when operators require an at-a-glance view with consistent week-over-week deltas instead of stitching together multiple agent outputs manually.

How do I generate a weekly digest without re-querying fork repositories?

Generate a weekly digest without re-querying by reading authoritative inputs from existing memory/topics and latest articles. The process composes fork release activity and contributor spotlight insights from these sources, computing week-over-week deltas and outputting articles/fleet-state.md files.

Can I produce a weekly digest if upstream fork-release or contributor-spotlight data is missing?

Yes, the weekly digest supports graceful degradation by producing partial output when one or two source state or artifact files are missing. This avoids hard failures when upstream skills haven't run, ensuring you still get a usable fleet overview.

What's the best way to track week-over-week trend deltas across a fork fleet?

The best way to track week-over-week trend deltas is synthesizing existing fork-cohort bucket totals and release activity into a single state-of-the-fleet narrative. This approach computes deltas automatically and gates notifications based on verdict and source availability.

What are the limitations of community monitoring digests that rely on existing memory topics?

The main limitation is that these digests do not perform new data collection, relying entirely on existing memory/topics and latest articles as sources of truth. If upstream skills haven't populated these inputs, the digest can only provide partial output through graceful degradation.