Slash Command1k repo starsupdated 5d ago

tour

Walk a brand-new OpenLoomi user through the entire pipeline in one guided session — thin doorway into the openloomi-tour sub-skill

View source Repository: openloomi

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/melandlabs/openloomi/HEAD/plugins/claude/commands/tour.md -o ~/.claude/commands/tour.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

tour.md

# /openloomi:tour

Thin doorway into the [`openloomi-tour`](../skills/openloomi-tour/SKILL.md)
sub-skill. The skill runs the full first-run pipeline live with
checkpoints between phases:

1. Pre-flight (`setup-status`, `run-host-probe`, selected execution-provider readiness)
2. Pet reaction (4 sprite states cycled)
3. Connector onboarding (native bot vs Composio OAuth — user picks)
4. Run one Loop tick + inspect & approve a decision card
5. Seed Memory (`add-memory` × 3 + `search-all`)
6. Optional extensions: custom Loop channel / classifier rule / decision type

The skill is the source of truth — read it first for the exact shell
snippets per phase. This doorway just confirms the entry point.

## Steps

1. Confirm `setup: ready` (or run `/openloomi:setup` first if not).
2. Load the [`openloomi-tour`](../skills/openloomi-tour/SKILL.md) skill
   and execute its phases in order. Stop between phases for the user
   to react (`next` / `skip` / `back`).
3. On exit (`done`, `exit`, or all five phases complete), print the
   quick-reference card from the `/openloomi:setup` post-ready
   walkthrough.

## When to suggest

- "I just installed OpenLoomi, what now?" → `/openloomi:tour`
- "Show me everything OpenLoomi can do" → `/openloomi:tour`
- "Walk me through the pipeline" → `/openloomi:tour`
- "带我看一下" / "体验一下" / "一条龙" → `/openloomi:tour`

For everything _inside_ the tour (specific commands, decision card
shapes, channel registration payloads), say the trigger phrase from
the [`openloomi-tour`](../skills/openloomi-tour/SKILL.md) frontmatter
and Claude will pick the right subcommand.

More from this repository

agent-browserSkill

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

cua-driverSkill

Drive a native macOS app via the cua-driver CLI (default) or MCP server — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers").

docxSkill

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

frontend-designSkill

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

openloomi-apiSkill

openloomi HTTP API reference (local-first, served from the OpenLoomi Desktop app at http://localhost:3414). Use when working with openloomi backend routes — auth, AI, files, integrations, RAG, memory, Loop, pet, workspace, platform callbacks. Triggers: API endpoints, backend routes, /api/*, local API, port 3414, integrations REST, OAuth start, RAG search, loop state, memory search, pet state, audit logs

openloomi-connectorsSkill

openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google Calendar/Drive/Docs, GitHub, Notion, Linear, HubSpot, LinkedIn, Jira, Asana). Triggers: connect platform, integration status, list accounts, disconnect, list-accounts, status, connect, send-reply, native vs composio, 1000+ apps, list connections.

openloomi-feature-guideSkill

Use this when users ask about openloomi features, capabilities, or how to use it. Examples: 'openloomi 怎么用', '你能做什么', 'What can you do?', 'How does openloomi work?', 'Tell me about openloomi features', 'What platforms does openloomi support?', 'How do I use scheduled tasks?', 'What is Loop?', 'How does the attention agent work?', 'What is a Decision Card?', 'How do connectors work?', 'How do I extend Loop with custom types?', 'What is a classifier rule?', 'How do I plug openloomi into Claude Code / Codex?'

openloomi-memorySkill

openloomi Memory tools - search and manage the holistic context (people, projects, decisions, knowledge base, chat insights). Triggers: memory search, knowledge base, search documents, list insights, who is John, what did we decide about X, tiered memory, knowledge graph, people/projects/decisions, search-all, conversation memory