v4-readiness

Audit aeon.yml, skills.json, and MEMORY.md against a v4 change manifest.

6|2|Updated May 21, 2026

Search Tags:#skill metadata #operational safety #GitHub forks #v4 upgrade #readiness audit #configuration compatibility #chain runner

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill v4-readiness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: v4-readiness
Source: https://github.com/anajuliabit/aeon/tree/main/skills/v4-readiness
Command: npx skills add https://github.com/anajuliabit/aeon --skill v4-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken upgrades by generating a per-fork v4 readiness checklist that surfaces which parts of your current configuration and customizations are safe versus likely to change or fail.

Core Features & Use Cases

Per-fork readiness audit: Reads your fork’s aeon.yml, skills.json, and MEMORY.md to detect which embedded v4 patterns are present.
Safe vs Review vs Custom vs Action-items: Produces a structured breakdown so you know what can be trusted, what needs manual inspection, and what is custom to your fork.
Optional remote survey: When given a fork slug, it audits the remote fork via GitHub CLI reads without editing anything.
Operator-first safety: Operates read-only, writes an article report, and sends at most one notification per manual run.

Quick Start

Run v4-readiness with var set to dry-run to generate the readiness article and log without sending a notification.

Frequently Asked Questions about v4-readiness

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

FAQPage Schema

How do I audit my repository configuration for a v4 upgrade before pulling changes?▼

To audit configuration for a v4 upgrade, generate a readiness checklist by reading your fork's aeon.yml, skills.json, and MEMORY.md against a v4 change manifest. This process validates enabled skills, model overrides, chain definitions, and triggers to prevent broken upgrades.

What is a v4 readiness audit and how does it identify upgrade risks?▼

A v4 readiness audit compares your local configuration files against embedded v4 change manifests to categorize components as Safe, Review, Custom, or Action-items. It surfaces which parts of your current setup are safe versus likely to change or fail during the upgrade.

Can I check v4 upgrade readiness on a remote GitHub fork without modifying files?▼

Yes, you can check v4 readiness remotely by providing a fork slug to audit the repository via GitHub API content reads. The audit operates strictly read-only, writes an article report, and never mutates the repository state.

How do I run a dry-run v4 readiness report without sending notifications?▼

To run a dry-run readiness report without notifications, execute the audit with the variable set to dry-run. This generates the readiness article and log locally, performing pre-flight validation of custom skills and configuration compatibility without alerting operators.

Does a v4 readiness audit support custom skills and model overrides?▼

Yes, v4 readiness audits explicitly support pre-flight validation of custom skills and model overrides. The audit scans your skills.json and aeon.yml configurations to detect embedded v4 patterns and flags custom elements requiring manual inspection.

What are the limitations of running a v4 upgrade readiness checklist?▼

The v4 readiness checklist operates read-only and does not mutate repository state or automatically fix configuration issues. It emits Safe/Review/Custom/Action-item report artifacts, requiring operators to manually address identified upgrade risks.