원클릭으로 Manus에서 모든 스킬 실행

openloomi-install

스타639

포크36

업데이트2026년 7월 10일 08:32

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, claude env sync.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

melandlabs

melandlabs/openloomi

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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.
`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`	Run `loomi-bridge sync-claude-env` if `ANTHROPIC_API_KEY` / `ANTHROPIC_BASE_URL` / `ANTHROPIC_MODEL` are set; otherwise walk the user through the OpenLoomi Desktop Preferences page.
`SOURCE_FOUND_CLI_NOT_BUILT`	Show the build instructions from the OpenLoomi repo's `apps/web/src-tauri/README.md` or recommend running the bundled installer instead.
`READY`	Nothing to do.

Reminder: secrets contract

The bridge reads ANTHROPIC_API_KEY / ANTHROPIC_AUTH_TOKEN once, locally; never prints the key.
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.

이 저장소의 다른 Skills

같은 저장소

openloomi-api

melandlabs/openloomi

openloomi API documentation and reference. Use when working with openloomi backend APIs, AI, authentication, characters, messages, files, integrations, billing, or any server-side functionality. Triggers: API endpoints, backend routes, authentication, cloud API, integrations

2026-07-12639

openloomi-connectors

melandlabs/openloomi

openloomi Connectors tools - manage platform integrations (OAuth connections, list accounts, check status). Triggers: connect platform, integration status, list accounts, disconnect

2026-07-12639

openloomi-feature-guide

melandlabs/openloomi

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 Insights system?', 'How do I connect Telegram?', 'How to create automation?', '什么是 openloomi 事件?'

2026-07-12639

openloomi-loop

melandlabs/openloomi

openloomi's Loop — the proactive execution brain. Loop runs inside the main web app (apps/web/lib/loop/) and is reached through its HTTP API. Use this skill to inspect state, run a tick, schedule / cancel decision actions, and tune preferences. Triggers: 'openloomi loop', 'loop tick', 'loop schedule', 'loop inbox', 'loop run', 'proactive decisions', 'signal → decision → execute', 'pull signals', 'decision queue'

2026-07-12639

openloomi-memory

melandlabs/openloomi

openloomi Memory tools - search memory files, knowledge base, and chat insights. Triggers: memory search, knowledge base, documents, insights

2026-07-12639

openloomi-feature-guide

melandlabs/openloomi

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 Insights system?', 'How do I connect Telegram?', 'How do I create automation?', '什么是 openloomi 事件?'

2026-07-11639

name	openloomi-install
description	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, claude env sync.
metadata	{"version":"0.1.0"}
allowed-tools	Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *)

OpenLoomi Install Sub-skill

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.
`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`	Run `loomi-bridge sync-claude-env` if `ANTHROPIC_API_KEY` / `ANTHROPIC_BASE_URL` / `ANTHROPIC_MODEL` are set; otherwise walk the user through the OpenLoomi Desktop Preferences page.
`SOURCE_FOUND_CLI_NOT_BUILT`	Show the build instructions from the OpenLoomi repo's `apps/web/src-tauri/README.md` or recommend running the bundled installer instead.
`READY`	Nothing to do.

Reminder: secrets contract

The bridge reads ANTHROPIC_API_KEY / ANTHROPIC_AUTH_TOKEN once, locally; never prints the key.
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.