How do I install the Openloomi Install skill?

Run npx skillmds@latest add melandlabs/openloomi-install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openloomi Install safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openloomi Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openloomi Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openloomi Install?

melandlabs (@melandlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openloomi Install by melandlabs — Agent Skill

Name: Openloomi Install
Author: melandlabs

Openloomi Install

OpenLoomi install & first-use setup helper for Claude Code. Use when the user wants to install OpenLoomi, configure it, or troubleshoot `OPENLOOMI_NOT_INSTALLED` / `OPENLOOMI_NOT_FINALIZED` errors after running `/openloomi:setup` or `/openloomi:status`. Triggers: install openloomi, 配置 openloomi, setup openloomi, openloomi not installed, openloomi not finalized, install_required, install missing, what now, what next, first time, what can i do.

melandlabs Updated Sep 17, 2026

File contents

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

node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs setup-status --json
Based on nextAction / reason:

Reason / nextAction	Action
`OPENLOOMI_NOT_INSTALLED`	Run `loomi-bridge install [--yes]` after explicit y/N — OpenLoomi Desktop is not on this machine. For offline / corporate-proxy installs, point the user at the restricted-network guide (link below).
`OPENLOOMI_NOT_FINALIZED` / `launch_openloomi_to_finalize`	OpenLoomi.app is installed (`desktopMarker` set) but the helper binary isn't on disk yet. Tell the user to launch OpenLoomi once (macOS: `open -a "<desktopMarker>"`) so it lays down the helper, then re-run `/openloomi:setup`. Do NOT install.
`LOGIN_REQUIRED`	Ask user to open OpenLoomi Desktop to sign in. Run `setup-status` again afterwards.
`AI_PROVIDER_REQUIRED`	OpenLoomi has no authenticated Claude runtime and no per-user provider row. Point the user at running `claude auth login` (then re-run `/openloomi:setup`), or at OpenLoomi Desktop → API Settings for a custom endpoint.
`SOURCE_FOUND_CLI_NOT_BUILT`	Show the build instructions from the OpenLoomi repo's Tauri build docs (or run `loomi-bridge install-instructions`) or recommend running the bundled installer instead.
`READY`	Nothing to do.

Reminder: secrets contract

This plugin never handles AI provider API keys. AI provider configuration lives in the OpenLoomi runtime itself; the runtime detects the user's local claude CLI auth on its own.
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 — there's no such flag in the plugin, by design.

---name: openloomi-installdescription: OpenLoomi install & first-use setup helper for Claude Code. Use when the user wants to install OpenLoomi, configure it, or troubleshoot `OPENLOOMI_NOT_INSTALLED` / `OPENLOOMI_NOT_FINALIZED` errors after running `/openloomi:setup` or `/openloomi:status`. Triggers: install openloomi, 配置 openloomi, setup openloomi, openloomi not installed, openloomi not finalized, install_required, install missing, what now, what next, first time, what can i do.---# OpenLoomi Install Sub-skillThis sub-skill is auto-loaded when the user wants to install or fix OpenLoomion their machine. It composes `loomi-bridge` operations and never downloadsor executes anything outside the plugin's own scripts.## Quick workflow1. `node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs setup-status --json`2. Based on `nextAction` / `reason`:| Reason / nextAction | Action ||---|---|| `OPENLOOMI_NOT_INSTALLED` | Run `loomi-bridge install [--yes]` after explicit y/N — OpenLoomi Desktop is not on this machine. For offline / corporate-proxy installs, point the user at the restricted-network guide (link below). || `OPENLOOMI_NOT_FINALIZED` / `launch_openloomi_to_finalize` | OpenLoomi.app is installed (`desktopMarker` set) but the helper binary isn't on disk yet. Tell the user to launch OpenLoomi once (macOS: `open -a "<desktopMarker>"`) so it lays down the helper, then re-run `/openloomi:setup`. **Do NOT install.** || `LOGIN_REQUIRED` | Ask user to open OpenLoomi Desktop to sign in. Run `setup-status` again afterwards. || `AI_PROVIDER_REQUIRED` | OpenLoomi has no authenticated Claude runtime and no per-user provider row. Point the user at running `claude auth login` (then re-run `/openloomi:setup`), or at OpenLoomi Desktop → API Settings for a custom endpoint. || `SOURCE_FOUND_CLI_NOT_BUILT` | Show the build instructions from the OpenLoomi repo's Tauri build docs (or run `loomi-bridge install-instructions`) or recommend running the bundled installer instead. || `READY` | Nothing to do. |## Reminder: secrets contract- This plugin never handles AI provider API keys. AI provider configuration lives in the OpenLoomi runtime itself; the runtime detects the user's local `claude` CLI auth on its own.- 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 — there's no such flag in the plugin, by design.

Frequently asked questions