Agent Skills
› melandlabs/openloomi
› openloomi-install
openloomi-install
GitHub用于协助用户在本地安装、配置及排错 OpenLoomi。通过 loomi-bridge 检测状态，引导完成桌面应用安装、源码构建、Codex 运行时切换及 AI 提供商配置，严格遵循安全规范处理密钥与确认流程。
Trigger Scenarios
用户希望安装 OpenLoomi
需要配置或初始化 OpenLoomi
诊断 INSTALL_REQUIRED 或 SOURCE_FOUND_APP_NOT_BUILT 错误
设置 AI 提供商或解决会话初始化问题
Install
npx skills add melandlabs/openloomi --skill openloomi-install -g -y
SKILL.md
Frontmatter
{
"name": "openloomi-install",
"description": "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` \/ `AI_PROVIDER_REQUIRED` \/ `SESSION_INITIALIZATION_REQUIRED` after running setup-status. Triggers: install openloomi, configure openloomi, setup openloomi, openloomi not installed, openloomi not finalized, install_required, install missing, AI provider setup, guest session.",
"allowed-tools": "Bash(node $SKILL_DIR\/..\/..\/scripts\/loomi-bridge.mjs *)"
}
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 "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status- Based on
nextAction/reason:
| Reason / nextAction | Action |
|---|---|
install_openloomi / INSTALL_REQUIRED |
OpenLoomi Desktop is not on this machine. Call install-instructions to show the platform plan. Only call install-openloomi --confirm after the user explicitly approves installation. |
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 apps/web/src-tauri/README.md 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. |
open_openloomi_ai_provider_setup / AI_PROVIDER_REQUIRED |
Prefer the Codex runtime path first: call codex-runtime-info, guide the user through the platform-specific runtime switch, then verify /api/native/providers. If the user chooses a separate AI provider fallback, walk them through configure-ai-provider. Never pass an API key in argv. Secret entry must happen in OpenLoomi-owned UI / interactive CLI surfaces. |
AI_PROVIDER_STATUS_UNAVAILABLE |
The local OpenLoomi API is not reachable, so the bridge cannot confirm whether provider settings are saved. Ask the user to open OpenLoomi Desktop and re-run setup-status. |
run / READY_SESSION_BOOTSTRAP_PENDING |
Nothing to install. OpenLoomi is ready; the local API will mint a guest session on the next Codex handoff or runtime call. |
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:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" codex-runtime-info
Reminder: secrets contract
- The bridge never reads AI provider env vars. Provider readiness comes from the OpenLoomi runtime's
/api/preferences/ai. The bridge only sees presence booleans (configured / not configured), never key values. - 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-keyas an argv flag. The bridge has no such flag, by design. - The bridge does not auto-install. Always require an explicit user confirmation before calling
install-openloomi --confirm.
Version History
- 23e340f Current 2026-07-19 17:58
