onboard

Runs a four-question first-run interview that seeds vault context pages and hands off to help.

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill onboard-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/src/skills/onboard
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill onboard-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users of a rubber-ducky vault start with zero context, so the assistant cannot personalize replies or remember anything useful. This Skill captures the minimum viable context in a short interview so the assistant is useful from the next conversation onward. ## Core Features & Use Cases - Lightweight intake interview: Asks exactly four one-at-a-time questions covering vault purpose, identity, vocabulary, and communication preferences. - Routed persistence: Sends each answer through /ingest-writing so it lands in the correct wiki page (about.md, vocabulary.md, preferences.md) rather than writing directly. - Completion tracking: Flips the onboard.completed setting and appends a wiki log entry so future sessions know onboarding already happened. - Use Case: A user opens a fresh vault for their boat maintenance project, answers four quick questions, optionally pastes an old maintenance log, and the assistant immediately knows the vault's purpose and how to talk to them. ## Quick Start Say "onboard me" or "help me get set up" when you first open a new vault and answer the four questions the assistant asks.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I set up a new rubber-ducky vault for the first time?▼

Open the vault in Claude Code and say hi or ask to be onboarded. The assistant checks the onboard.completed setting, runs a four-question interview about your vault's purpose and preferences, and stores the answers in the wiki context pages.

How do I re-run onboarding if my context has changed?▼

Explicitly ask to onboard again, such as saying "onboard me". Because onboard.completed is already true, the assistant will confirm whether you want a full re-run, a top-up of one section, or to skip, rather than silently restarting.

Can I paste existing documents instead of answering interview questions?▼

Yes. After the interview, if the ingest.auto_on_onboard setting is true, you are invited to paste raw material like bios, reviews, or project docs. The text is handed to /ingest-writing, which routes useful content into the right wiki pages.

Does onboarding connect external tools like Jira or Slack?▼

No. The onboarding skill deliberately avoids backend wiring and project creation. Integrations are added later on demand via the /connect skill, and tasks are created through normal conversation after onboarding finishes.

Why does onboarding skip some interview questions?▼

Question 3 about internal vocabulary is skipped when the vault is personal or non-work, and question 4 about communication style is skipped if you already gave a clear style signal earlier. The interview is capped at four questions to keep intake lightweight.