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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents an Aeon fork from running in a half-configured, broken, or degraded state by turning setup checks into a clear, operator-readable readiness report.

Core Features & Use Cases

  • One-shot setup validation: Runs the onboard CLI checks for workflows, auth secrets, and notification routing and reports a pass/warn/fail checklist.
  • Operator-ready fixes: For every gap, includes the exact command needed to repair setup, without auto-mutating the repo.
  • Optional quiet self-audit: Supports a silent-on-pass mode so you only get notified when something breaks during scheduled runs.
  • Use Case: After forking Aeon and setting secrets, you want a single notification that tells you whether the system is ready and exactly what to do next if anything is missing.

Quick Start

Run this skill by executing ./onboard --remote after you have set your secrets so you receive a single checklist in your configured notification channel.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I validate an Aeon fork configuration after setting secrets?

To validate an Aeon fork configuration, run the onboard CLI checks to verify workflows, auth secrets, and notification routing, generating a pass, warn, and fail readiness report. This ensures your fork avoids running in a half-configured or degraded state.

Can I run a silent self-audit that only alerts on configuration failures?

Yes, you can run a silent self-audit using the quiet mode, which suppresses notifications when checks pass and only alerts you when setup degrades. This is ideal for scheduled validation runs to monitor ongoing readiness without noise.

How does readiness reporting handle missing GitHub Actions auth secrets?

Readiness reporting identifies missing auth secrets during validation and flags them as warnings or failures. It provides operator-ready fixes by including the exact command needed to repair the setup without auto-mutating the repository.

Do I need to manually parse JSON output to check notification routing?

No, you do not need to manually parse JSON output to check notification routing. The validation process parses the onboard JSON output automatically and conditionally sends a notification via the notify command with the results.

What is the best way to fix a broken Aeon setup without auto-mutating the repo?

The best way to fix a broken Aeon setup safely is to run a configuration validation check. It reports gaps and includes the exact commands needed to repair setup, ensuring safe, non-mutating behavior that does not alter the repository.

Does configuration validation support scheduled readiness reporting for forks?

Yes, configuration validation supports scheduled readiness reporting by running as a self-audit. It logs results into memory files and uses quiet mode to alert operators only when the Aeon fork setup degrades over time.