openloomi-tour

What it does

The skill conducts a hands-on, multi-phase OpenLoomi onboarding tour. It sequences phases from pre-flight checks through Phase 1 (Pet reaction), Phase 2 (Onboarding & input sources), Phase 3 (Run one Loop tick), and Phase 4 (Seed Memory). Each phase runs a set of explicit commands and checks prerequisites, providing an interactive, idempotent, and skippable experience that is non-destructive and can be navigated with next/skip/back, with the option to register additional Loop components at the end.

How it works

• Phase 0 (Pre-flight): executes three node/CLI checks via the loomi-bridge script to determine readiness, host probe, and execution provider status, then prints the user state before Phase 1.
• Phase 1 — Pet reaction: runs four pet state commands to display different sprites (happy, thinking, working, juggling) and ends with the pet in the happy state, signaling readiness.
• Phase 2 — Onboarding & input sources: offers three input paths (Native bot, Composio OAuth, Screen memory) and provides concrete commands to verify connections or memory captures. It supports a skip option with rules for Phase 3 and memory seeding implications.
• Phase 3 — Run one Loop tick: if there is at least one signal source, dispatches a background Loop tick by posting to /api/loop/tick, then (a) guides the user to discuss architecture, (b) polls for lastTickAt completion, and (c) inspects outcomes, including decisions. If a decision exists, shows its card and provides a one-tap approve command.
• Phase 4 — Seed Memory: uses the openloomi-memory tool to add tour-owned memory entries (About me, Current project, Values) with explicit add-memory commands, followed by a search-all to confirm indexing. It notes that these are tour-owned and may be overwritten on reruns and that user-authored memory paths are protected.

Commands and file names are quoted exactly as shown in the skill, such as:

• node "${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs" setup-status --json
• node "${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs" pet happy
• node "${CLAUDE_PLUGIN_ROOT}/skills/openloomi-connectors/scripts/openloomi-connectors.cjs" list-accounts
• /api/loop/tick (POST)
• MEM="${CLAUDE_PLUGIN_ROOT}/skills/openloomi-memory/scripts/openloomi-memory.cjs"
• node "$MEM" add-memory "About me: <text>" --file=tour/about-me.md

When to use it

Triggered by phrases like openloomi tour, guided tour, walk me through openloomi, end-to-end demo, first time using openloomi, what's next after setup. It is the canonical first-run experience and is designed to be interactive, idempotent, and skippable, ensuring phases are not destructive and can be revisited as needed.

What it can touch

• Scripts and endpoints under ${CLAUDE_PLUGIN_ROOT}, including:
  • scripts/loomi-bridge.mjs
  • skills/openloomi-connectors/scripts/openloomi-connectors.cjs
  • skills/openloomi-memory/scripts/openloomi-memory.cjs
• The memory tool via the command memory scripts and add-memory / search-all calls
• HTTP endpoints such as http://localhost:3414/api/loop/tick and related /api/loop/state, /api/loop/decisions

Caveats

• Phase 3 tick runs in the background and is not guaranteed to complete before Phase 4; user is guided to proceed and monitor progress.
• Phase 4 seeds tour-owned memory under ~/.openloomi/data/memory/tour/ and may overwrite tour artifacts on reruns; user-authored memory paths are protected.
• The tour is non-destructive and reversible in terms of ensuring no irreversible actions during onboarding.