菜单
Use OpenLoomi loop workflows from Codex for attention loops, prioritization, wrap-up, follow-up, and work-state routing. Trigger when users ask Loomi to plan, prioritize, monitor, loop, summarize, or follow up on work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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
openloomi Connectors tools - manage platform integrations (OAuth connections, list accounts, check status). Triggers: connect platform, integration status, list accounts, disconnect
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 事件?'
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'
openloomi Memory tools - search memory files, knowledge base, and chat insights. Triggers: memory search, knowledge base, documents, insights
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 事件?'
| name | openloomi-loop |
| description | Use OpenLoomi loop workflows from Codex for attention loops, prioritization, wrap-up, follow-up, and work-state routing. Trigger when users ask Loomi to plan, prioritize, monitor, loop, summarize, or follow up on work. |
| allowed-tools | Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *) |
Use this skill as a thin wrapper for OpenLoomi loop workflows. Do not implement loop scheduling, decision storage, connector checks, or memory logic in Codex. OpenLoomi runtime owns those behaviors.
First, load workflow guidance:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidance --workflow openloomi-loop
Then check readiness:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status
If ready: false, follow the reported nextAction and do not continue the
loop task yet. Guest/session initialization must happen through OpenLoomi-owned
surfaces. Never ask for API keys, OAuth tokens, connector secrets, or
OpenLoomi auth tokens in Codex chat.
When ready: true, wrap the user request with the taskPromptPrefix returned
by workflow-guidance, then pass that runtime-safe prompt over stdin to the
bridge:
printf "%s" "<taskPromptPrefix>\n\nOriginal user request: <user loop request>" | node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" run
Do not send wording that asks the inner runtime to invoke Codex plugins,
OpenLoomi plugins, skills, shell commands, or loomi-bridge. Keep all
persistence, connector state, memory access, and follow-up scheduling inside
OpenLoomi runtime.