openloomi
GitHub作为OpenLoomi技能型代理的入口，用于在缺乏插件机制的环境中引导用户完成本地API配置、记忆搜索、连接器管理及Loop状态检查，确保工作正确路由至桌面运行时。
触发场景
安装
npx skills add melandlabs/openloomi --skill openloomi -g -y
SKILL.md
Frontmatter
{
"name": "openloomi",
"description": "OpenLoomi entrypoint for skill-only agent runtimes without a plugin mechanism. Use when the user mentions OpenLoomi or Loomi, wants first-use setup guidance, wants to use local OpenLoomi memory, connectors, Loop, knowledge base, RAG search, or asks how to install OpenLoomi skills in runtimes such as WorkBuddy or other skill-capable agents."
}
OpenLoomi Skills Entrypoint
Use this skill as the front door for OpenLoomi in agents that can load skills but do not support OpenLoomi plugins.
OpenLoomi remains the runtime owner. The desktop app owns memory storage, connector credentials, Loop execution, model/provider settings, local API routes, and secret handling. Skills only explain how to route work into that local runtime.
First Step
When readiness is unknown, start with openloomi-setup. It guides the user
through installing or opening OpenLoomi Desktop, confirming the local API, and
finishing the session/token setup. Do not ask the user to paste API keys,
OAuth tokens, connector secrets, or OpenLoomi auth tokens into chat.
Route Requests
Use the narrow OpenLoomi skill that matches the task:
| User intent | Use |
|---|---|
| First-use setup, install guidance, readiness checks | openloomi-setup |
| Search memory, knowledge base, documents, insights | openloomi-memory |
| Connect platforms, list accounts, check connector status, send replies | openloomi-connectors |
| Use third-party OAuth apps such as Slack, Gmail, GitHub, Notion, Linear, or Jira | composio, paired with openloomi-connectors |
| Inspect Loop state, run a tick, manage decisions, preferences, channels, or rules | openloomi-loop |
| Answer backend route, local API, auth, RAG, integrations, or workspace questions | openloomi-api |
| Explain OpenLoomi concepts, product capabilities, or user workflows | openloomi-feature-guide |
Common Flows
Use these examples to route common requests without reimplementing OpenLoomi logic in the agent:
- Search memory: start with
openloomi-setupif readiness is unknown, then useopenloomi-memoryto search memory, knowledge base documents, or insights. - Post to Slack: start with
openloomi-setup, useopenloomi-connectorsto check connector/account readiness, then usecomposiofor the OAuth-backed Slack action when the user asks to send or post. - Draft an email: start with
openloomi-setup, useopenloomi-memoryfor relevant context, then usecomposioor connector guidance for the mail surface the user has authorized. - Summarize a Notion page: start with
openloomi-setup, usecomposiofor the authorized Notion access path, then hand useful context toopenloomi-memoryoropenloomi-apiwhen the user wants it saved, searched, or grounded in the local knowledge base.
Boundaries
- Do not depend on Codex or Claude plugin files.
- Do not call plugin bridge scripts such as
loomi-bridge.mjs. - Do not duplicate OpenLoomi business logic inside the agent.
- Do not invent connector behavior. Use the connector and Composio skills for platform-specific flows.
- If OpenLoomi Desktop is missing or the local API is unavailable, use
openloomi-setupto provide official installation and recovery guidance.
版本历史
- 17e808c 当前 2026-07-31 06:48
