openloomi-install
OpenLoomi install & first-use setup helper for Codex. Use when the user wants to install OpenLoomi, configure it, or troubleshoot `INSTALL_REQUIRED` / `SOURCE_FOUND_APP_NOT_BUILT` / `SESSION_INITIALIZATION_REQUIRED` after running setup-status. Triggers: install openloomi, configure openloomi, setup openloomi, openloomi not installed, openloomi not finalized, install_required, install missing, guest session.
git clone --depth 1 https://github.com/melandlabs/openloomi /tmp/openloomi-install && cp -r /tmp/openloomi-install/plugins/codex/skills/openloomi-install ~/.claude/skills/openloomi-installSKILL.md
# OpenLoomi Install Sub-skill This sub-skill is auto-loaded when the user wants to install or fix OpenLoomi on their machine. It composes `loomi-bridge` operations and never downloads or executes anything outside the plugin's own scripts. ## Quick workflow 1. **Always run `setup` (and the loopback checks below) outside the Codex sandbox** — the install + launch path needs writes to `/Applications`, desktop GUI launch, and `http://localhost:3414`. Default `read-only` / `workspace-write` modes will silently fail. Ask the user to drop `sandbox=workspace-write` (or move to `danger-full-access`) before invoking the bridge. 2. `node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status` 3. Based on `nextAction` / `reason`: | Reason / nextAction | Action | |---|---| | `install_openloomi` / `INSTALL_REQUIRED` | OpenLoomi Desktop is not on this machine. **Call `setup --yes` to run the end-to-end wizard in one invocation**: resolve → download → install → set `OPENLOOMI_AGENT_PROVIDER=codex` → launch the desktop app → wait for the local API → mint a guest session token. Invoking this skill counts as explicit approval to pass `--yes`. For offline / corporate-proxy installs, point the user at the restricted-network guide (link below) and call `install-instructions` first. | | `SOURCE_FOUND_APP_NOT_BUILT` | A source checkout is present but the OpenLoomi Desktop GUI app has not been built yet. Recommend either building the source per the OpenLoomi repo's Tauri build docs (or run `loomi-bridge install-instructions`) or installing the packaged Desktop release. | | `open_openloomi` / `OPENLOOMI_API_UNREACHABLE` / `SESSION_INITIALIZATION_REQUIRED` | OpenLoomi is installed but the local API or guest/session token is not ready. Ask the user to open OpenLoomi Desktop once, or run `setup` so the bridge can launch/init through OpenLoomi-owned surfaces. | | `inspect_codex_runtime` | OpenLoomi is up but the native Codex provider is not the active default agent. Have the user confirm the Codex CLI is installed (`codex --version`) and rerun `setup` so the runtime env + LaunchAgent get re-applied. | Before applying the API-unreachable row, inspect `loopbackAccessAmbiguous`. When it is `true`, the result is inconclusive because the current Codex sandbox may block host loopback traffic. Request approval and run `loopbackAccess.verification.commands` outside the sandbox. Only tell the user to restart OpenLoomi if the outside-sandbox checks also fail. ## Sandbox and installation Downloading and installing OpenLoomi can require capabilities that are blocked inside the current Codex sandbox: - GitHub release lookup and artifact download require network access. - The default installer may write to a system application directory such as `/Applications`. - Interactive installers and launching OpenLoomi Desktop require GUI/process access outside the sandbox. When an install command fails with a likely network, permission, filesystem, or GUI sandbox error, request approval and retry the same `loomi-bridge` command outside the sandbox. Do not work around the bridge by downloading or installing the artifact with unrelated commands. Do not report that the release URL is invalid or the installer is broken until the approved retry also fails. ## Codex runtime setup If the user is setting up OpenLoomi from Codex, explicitly asks to switch the desktop runtime executor to Codex, or diagnostics show a native-agent provider mismatch, call: ```bash node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" codex-runtime-info ``` ## Reminder: secrets contract - The bridge never reads AI provider env vars and never reports provider readiness from `/api/preferences/ai` — it only checks whether the native Codex runtime is active via `/api/native/providers`. Provider configuration is the OpenLoomi runtime's job, surfaced through the desktop app's own settings UI. - If the user pastes a key into chat, redact it: do NOT echo it back, and tell them to remove it from chat history. - Never pass `--api-key` as an argv flag. The bridge has no such flag, by design. - The bridge's end-to-end wizard is `setup --yes` (one-shot: install + set codex provider + launch desktop + mint guest session token). Invoke it from this skill when the user asks to install or finalize OpenLoomi. **Do not call `install-openloomi --confirm` by itself** — that only installs and leaves the desktop app unlaunched and the session token unminted. Use `install-openloomi --confirm` only when the user explicitly asks to install without launching (rare).
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.
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").
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.
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 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 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.
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 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