One-click install
npx skills add https://github.com/aaronjmars/aeon --skill skill-freshness-aaronjmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-freshness
Source: https://github.com/aaronjmars/aeon/tree/main/skills/skill-freshness
Command: npx skills add https://github.com/aaronjmars/aeon --skill skill-freshness-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Prevents autonomous skill chains from consuming outdated upstream files without any visible failures by auditing on-disk freshness and surfacing consumer-ready warnings.

Core Features & Use Cases

  • Dependency freshness auditing: Compares file mtimes against freshness thresholds derived from producer cadence in aeon.yml.
  • Explicit and implicit dependency tracking: Uses chains: consume edges for deterministic dependencies and greps enabled skills’ SKILL.md for best-effort implicit references.
  • Deduped reporting and notifications: Writes daily reports and memory state, suppressing repeated alerts when the flagged set hasn’t changed.

Quick Start

Run the fleet audit with no scope override by invoking skill-freshness with an empty var value so it audits every enabled consumer skill in aeon.yml.

Frequently Asked Questions about skill-freshness

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

FAQPage Schema
How do I detect silent staleness in autonomous workflows before downstream failures occur?

Detect silent staleness by auditing on-disk file mtimes against cadence-derived freshness thresholds defined in aeon.yml. This prevents autonomous skill chains from consuming outdated upstream files without visible failures by surfacing consumer-ready warnings.

What is the best way to track upstream dependency freshness for scheduled jobs?

Track upstream dependency freshness by auditing explicit consume edges and parsing implicit references from SKILL.md files. This mechanism scores dependency chains for scheduled jobs, comparing local file mtimes against producer cadence thresholds to generate a decision-ready report.

How do I audit file mtime freshness for autonomous agent reliability?

Audit file mtime freshness by running a local-only discovery process that checks enabled consumer skills scheduled in aeon.yml. It performs mtime-based freshness checks with cadence-derived thresholds to ensure agent reliability and outputs deduped notifications.

Does this freshness auditing approach work with implicit dependencies parsed from markdown?

Yes, freshness auditing works with implicit dependencies by using best-effort references parsed directly from each consumer SKILL.md. It combines these parsed implicit references with deterministic consume edges to comprehensively track explicit and implicit dependency chains.

How do I stop repeated staleness alerts when the flagged outdated files haven't changed?

Stop repeated staleness alerts through deduped reporting and notifications that write daily reports and memory state. This mechanism suppresses repeated alerts when the flagged set of outdated upstream articles or outputs hasn't changed, reducing notification fatigue.

What are the limitations of local-only staleness detection for distributed memory artifacts?

Local-only staleness detection is limited to on-disk file discovery and mtime checks within the local environment. It cannot validate freshness for distributed memory artifacts or remote outputs unless they are locally synced and discoverable by the file mtime auditing process.