relay-onboard

Reconciles a repo's agents and flows against a Relay board until the doctor reports zero errors.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/jeremylightsmith/relay-config --skill relay-onboard-jeremylightsmith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: relay-onboard
Source: https://github.com/jeremylightsmith/relay-config/tree/main/.claude/skills/relay-onboard
Command: npx skills add https://github.com/jeremylightsmith/relay-config --skill relay-onboard-jeremylightsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Wiring a repository to a Relay board for the first time leaves the repo's .claude/ agents and the board's flows out of sync, and fixing them node-by-node is guesswork. This Skill turns onboarding into a reconcile loop: diagnose with /relay-doctor, pick a seed/adopt/hybrid path, apply confirmed changes, and repeat until the doctor reports zero errors. ## Core Features & Use Cases - Doctor-driven reconcile loop: Runs /relay-doctor, applies one confirmed change at a time, and re-checks until zero errors, stopping on stalls instead of retrying blindly. - Three onboarding paths: Seed the shipped default factory, adopt the repo's existing agents and skills, or a hybrid — always an explicit human choice, never inferred. - Safe, idempotent mutations: Confirms every file diff and node-level flow change before applying, touches only .claude/, relay.md, .relay/executor.json, and flow documents, and resumes cleanly after interruption. - Use Case: After running bin/relay init on a new project, use this Skill to map the default Code flow's eight agent nodes onto your repo's two existing agents, replace the default verify command, and enable the flow only once the doctor is green. ## Quick Start Ask the assistant to onboard this repository to my Relay board and keep fixing things until relay-doctor reports zero errors.

Frequently Asked Questions about relay-onboard

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

FAQPage Schema
How do I onboard a repo to a Relay board for the first time?▼

Run bin/relay init to install the scaffold, set RELAY_URL and RELAY_API_KEY, then run this onboarding skill. It runs relay-doctor, lets you choose seed, adopt, or hybrid, and loops confirmed fixes until the doctor reports zero errors.

What is the difference between seed, adopt, and hybrid onboarding?▼

Seed installs the shipped default factory and adjusts its gates. Adopt keeps your repo's existing agents and remaps flow nodes onto them. Hybrid seeds the flow shape but adopts wherever the repo already has a better artifact. The human picks the path explicitly.

Can relay-onboard run unattended or from a flow node?▼

No. The skill is interactive by design: it asks which path to take, proposes node mappings, and confirms every mutation. Running it from a flow node fails because a runner has nobody to ask.

Why does relay-doctor keep failing after onboarding changes?▼

The loop applies one change at a time and re-runs the doctor to show the error delta. If two consecutive passes fail to reduce errors, the skill stops and reports what remains rather than retrying, since a stall indicates a problem needing human input.

What files does Relay onboarding modify?▼

Its blast radius is limited to .claude/ files, relay.md, .relay/executor.json, and flow documents pushed via flow-push. It never touches application code, git branches, commits, or cards.

When should I use relay-doctor instead of relay-onboard?▼

Use relay-doctor when the repo is already wired and a single node or check is broken. Use relay-onboard only for first-time setup or when the repo's factory and flows disagree wholesale and the fix is a path, not a patch.