onboard

Runs capability onboarding interviews and writes typed answers to MOD.md overlay files.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill onboard-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/capability-lifecycle/skills/onboard
Command: npx skills add https://github.com/AlmogBaku/aos --skill onboard-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Installing a new capability requires collecting personalized configuration (identity, timezone, preferences, secrets) in a structured, repeatable way. This Skill standardizes that interview process so answers land in a consistent MOD.md overlay without manual file editing or lost secrets. ## Core Features & Use Cases - Typed Interview Questions: Reads a capability's ONBOARDING.md frontmatter (string, number, boolean, enum, list, path types) and conducts a conversational, batched interview rather than a rigid form. - Secret Handling: Routes secret: true answers to the harness secret store, writing only {store, key} references into MOD.md so values are never persisted in plain text. - Diff-Gated Writes: Validates every answer against deterministic rules, shows a diff for approval before writing, and preserves unchanged answers byte-identically on re-runs. - Use Case: When installing a new personal-assistant capability, run the onboarding interview to capture your timezone, sacred hours, and API tokens, producing a versioned MOD.md that survives capability upgrades. ## Quick Start Ask your agent to run the onboarding interview for the capability you just installed and write the answers to your MOD.md overlay.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I onboard a new capability in an agent harness?▼

Run the onboard skill against the capability's ONBOARDING.md file. It reads the typed question schema, conducts a conversational interview, validates answers, and writes them to the capability's MOD.md overlay after you approve a diff.

How are secrets handled during capability onboarding?▼

Answers marked `secret: true` are written to the harness secret store, and MOD.md records only a `{store, key}` reference. The actual secret value is never written to the file or repeated in output.

Can I re-run onboarding without losing existing answers?▼

Yes. Re-runs ask only unanswered questions plus any marked `re_ask: true`, while `--refresh` shows all questions with current answers as defaults. Unchanged answers stay byte-identical and are never deleted.

What answer formats does the onboarding interview validate?▼

It validates string, number, boolean, enum, list, and path types per deterministic rules: enums must match options verbatim, timezones must be IANA names, times use 24h HH:MM, and required questions must receive answers.

When should I not use the onboard skill to change capability behavior?▼

Do not use it for behavior changes no interview question covers. Unasked changes are prose statements handled by capability-evolve, and adding a new question is a source change owned by capability-contribute.