onboard

Validate Aeon fork configuration and notify checklist results.

6|2|Updated May 21, 2026

Search Tags:#onboarding #GitHub Actions #self-audit #operator guidance #setup validation #notification routing #configuration checklist

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a freshly forked or half-configured Aeon repository into a known-working state by running the onboard validator and reporting every gap with the exact command to fix it.

Core Features & Use Cases

One-shot setup checklist: Runs the onboard CLI output as the source of truth and summarizes pass/warn/fail items for fast operator review.
Operator-ready repair guidance: For each failing or warning check, includes the specific recommended fix command from the CLI (without fabricating anything).
Run-time modes: Supports manual dispatch for “is Aeon alive?” checks and optional scheduled self-audits that stay quiet when everything is healthy.

Quick Start

Run the onboard workflow validator to get a consolidated 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 my GitHub Actions setup after forking a repository?▼

You can validate your repository fork configuration by executing the onboard CLI to generate JSON output, which is then transformed into an operator-friendly checklist that highlights pass, warn, and fail items for fast review.

What is the best way to detect configuration drift in a forked repository?▼

Detecting configuration drift is best handled by scheduling self-audits that execute the onboard CLI, compare current setup states against expected configurations, and dispatch notifications only when failures or warnings occur.

How do I get operator-ready repair guidance for failing onboarding checks?▼

Operator-ready repair guidance is generated by parsing the onboard CLI JSON output, extracting the exact recommended fix command for each failing or warning check, and formatting these details into a grouped notification summary.

Can I suppress notifications when my repository setup validation passes?▼

Yes, you can suppress notifications when setup validation passes by using the --silent-on-pass flag, which ensures the system only triggers a notification dispatch via the notify command when failing or warning checks are detected.

Does the setup validation checklist support manual dispatch for quick health checks?▼

Yes, the setup validation checklist supports manual dispatch for quick health checks, allowing operators to execute the onboarding validator on-demand to verify fork configuration status and identify any immediate setup gaps.