onboard

Validate forked repository setup and report a remediation checklist.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill onboard-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/onboard
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill onboard-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

One-shot onboarding validator ensures a freshly forked repository is correctly configured by running the onboard CLI inside the workflow and delivering a precise remediation checklist to the operator through configured notification channels.

Core Features & Use Cases

  • Local CLI validation: The ./onboard tool analyzes the repository and outputs a structured JSON checklist describing pass/warn/fail states.
  • Notification routing: When configured, results are sent via ./notify to Telegram/Discord/Slack/Email to keep operators informed.
  • Idempotent state and logging: Results are logged in memory/logs per day and memory/history tracks progress across runs for trend analysis.
  • Scheduled and manual workflows: Supports both manual dispatch and nightly cron-audits via var to suppress notifications on good runs.
  • Guidance through fixes: The checklist includes suggested fixes (where available) to help operators remediate gaps quickly.

Quick Start

Run the onboarding workflow to validate a freshly forked repository and receive a live checklist in your 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 a freshly forked repository setup automatically?

To validate a freshly forked repository setup, this Skill runs the local ./onboard CLI inside a CI workflow to check required secrets and workflows, outputting a structured JSON checklist with pass, warn, or fail remediation steps.

What is the best way to automate onboarding checks for required CI secrets?

Automating onboarding checks for required CI secrets is done by running scheduled nightly cron-audits or manual dispatches, which verify configurations and route the validation results via the ./notify tool to Telegram, Discord, Slack, or Email.

Do I need a local CLI tool to run repository validation in CI?

You need the local ./onboard CLI in the repository root to run repository validation in CI, as the workflow consumes its JSON output to analyze the setup state and generate the remediation checklist.

Can I suppress notifications for successful repository onboarding audits?

You can suppress notifications for successful repository onboarding audits by using the optional silent mode via var, which prevents the ./notify tool from sending alerts on good runs during nightly cron-audits.

How does repository setup validation track progress across multiple runs?

Repository setup validation tracks progress across multiple runs through idempotent state logging, recording daily results in memory/logs and tracking historical trend analysis in memory/history to monitor onboarding remediation over time.