Agent skill

Openloomi

by melandlabs in melandlabs/openloomi

OpenLoomi runtime integration for Claude Code. An agent skill from melandlabs/openloomi.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Openloomi

skills CLI
$ npx skills add melandlabs/openloomi --skill openloomi -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install melandlabs/openloomi openloomi --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude/skills/openloomi .claude/skills/openloomi && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openloomi
GitHub stars
1k
Token cost
~1.4k tokens
SKILL.md length
561 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
Apache-2.0

At a glance

OpenLoomi runtime integration for Claude Code. An agent skill from melandlabs/openloomi.

  • Works in 8 steps: OPENLOOMI_BIN → OPENLOOMI_HOME / OPENLOOMI_INSTALL_DIR → OPENLOOMI_REPO_DIR → …
  • The user mentions OpenLoomi
  • SKILL.md covers When to call loomi-bridge, Bridge subcommands (quick…, Secrets contract (verbatim… and Discovery chain, plus 2 more sections
  • Calls claude; needs OPENLOOMI_AUTH_TOKEN

What it does

Openloomi is an agent skill from melandlabs/openloomi. OpenLoomi runtime integration for Claude Code. Use when the user mentions OpenLoomi, wants to install/configure it, query their local memory via the Loomi runtime, change the Loomi Pet state, view LLM usage, run a one-shot task through the local runtime, or install the optional hooks that mirror Claude Code's lifecycle onto the Loomi Pet and auto-archive every Stop into OpenLoomi memory. Triggers: openloomi, loomi, /openloomi:, local memory, RAG search, insights, loop, pet state, openloomi tour, guided tour, walk…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering. The repository describes itself as: OpenLoomi is an open-source AI coworker. It connects your work tools, understands what you’re working on, and tells you what needs your attention, why it matters, and what to do… The licence is Apache-2.0.

When your agent uses it

  • The user mentions OpenLoomi
  • Wants to install/configure it
  • Query their local memory via the Loomi runtime
  • Change the Loomi Pet state

Example prompts

  • “/openloomi”

Requirements

  • A credential in OPENLOOMI_AUTH_TOKEN
  • Pre-approved tools (allowed-tools): Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *)

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. OPENLOOMI_BIN
  2. OPENLOOMI_HOME / OPENLOOMI_INSTALL_DIR
  3. OPENLOOMI_REPO_DIR
  4. PATH lookup
  5. Platform defaults — the desktop app's main binary
  6. ${CLAUDE_PLUGIN_DATA}/config.json (non-secret cached install path)
  7. bin-path explicit flag
  8. Otherwise: emit nextAction: install_openloomi

What it can do on your machine

Read from SKILL.md and the folder at commit 2aca101. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENLOOMI_AUTH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openloomi loads about 1.4k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 561 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from melandlabs/openloomi at commit 2aca101, republished under its Apache-2.0 licence (© melandlabs). 561 words, ~1,439 tokens.

Download SKILL.mdSave it as .claude/skills/openloomi/SKILL.md (or your agent's skills folder).
name
openloomi
description
OpenLoomi runtime integration for Claude Code. Use when the user mentions OpenLoomi, wants to install/configure it, query their local memory via the Loomi runtime, change the Loomi Pet state, view LLM usage, run a one-shot task through the local runtime, or install the optional hooks that mirror Claude Code's lifecycle onto the Loomi Pet and auto-archive every Stop into OpenLoomi memory. Triggers: openloomi, loomi, /openloomi:*, local memory, RAG search, insights, loop, pet state, openloomi tour, guided tour, walk me through openloomi, show me everything, 一条龙, 体验一下, 带我看一下.
allowed-tools
Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *)

OpenLoomi Claude Plugin Skill

This skill is the single entry point for the OpenLoomi ↔ Claude Code integration. It is intentionally thin: it delegates to loomi-bridge.mjs for every side effect and never duplicates OpenLoomi business logic, connector implementations, or memory storage.

When to call loomi-bridge

Call loomi-bridge.mjs whenever ANY of the following is true:

  • User says openloomi, loomi, pet, /openloomi:*, or asks about "the local AI assistant".
  • User wants to install, configure, verify, or update OpenLoomi.
  • User asks Claude Code to query their memory, look up a previous conversation, or "search my notes".
  • User wants to set the Loomi Pet to a specific state.
  • User wants today's LLM cost / usage.
  • User asks about hooking Claude Code up to "the pet" or "loop".

When the user just wants something Claude can do natively (write a file, answer a question, etc.) and OpenLoomi is not mentioned, do not invoke the bridge.

Bridge subcommands (quick reference)

SubcommandSlash commandTypical use
setup/openloomi:setupFirst-run install + status
setup-status [--json]/openloomi:statusStable JSON status
install [--yes](internal)User-approved install
login(internal)Open OpenLoomi login surface, report status
pet <state>/openloomi:petSet Pet state (9 universal states; theme-agnostic)
state <name>(internal/hook)Fire-and-forget Pet state from hook
archive(internal/hook)Archive last transcript on Stop
usage/openloomi:usageToday's LLM usage summary
install-hooks/openloomi:hooks installMerge hooks into ~/.claude/settings.json
uninstall-hooks/openloomi:hooks uninstallStrip only the plugin's hook block
hooks-status/openloomi:hooks statusReport hook merge state
loop (doorway)/openloomi:loopLoop dashboard snapshot — delegates to the openloomi-loop sub-skill
memory <query> (doorway)/openloomi:memorySearch memory + KB + insights — delegates to the openloomi-memory sub-skill
version(internal)Print plugin version

All subcommands emit JSON to stdout unless noted otherwise. All failure modes emit JSON (never bare stack traces).

Secrets contract (verbatim from plugins/codex/README.md §256–296)

Claude Code must never receive or print:

  • model provider API keys (the plugin never reads them — the runtime handles its own AI provider configuration);
  • OAuth access tokens or refresh tokens;
  • connector app secrets;
  • OpenLoomi auth tokens;
  • local secure-storage contents (e.g. ~/.openloomi/token contents).

Allowed status-only checks:

text
OPENLOOMI_AUTH_TOKEN present/missing
~/.openloomi/token present/missing
native Claude CLI authenticated / not authenticated
AI provider configured/missing
connector configured/missing
local API reachable/unreachable

The bridge may report key names and presence. It must not print values. AI provider readiness comes entirely from the OpenLoomi runtime's /api/preferences/ai response (nativeRuntime / aiProviderConfigured).

Show full SKILL.md (202 more words)Show less

Discovery chain

The bridge resolves your local OpenLoomi runtime in this order:

  1. OPENLOOMI_BIN
  2. OPENLOOMI_HOME / OPENLOOMI_INSTALL_DIR
  3. OPENLOOMI_REPO_DIR
  4. PATH lookup
  5. Platform defaults — the desktop app's main binary:
    • macOS: ~/Applications/OpenLoomi.app/Contents/MacOS/openloomi
    • Linux: /opt/openloomi/openloomi (or ~/.local/bin/openloomi, /usr/local/bin/openloomi)
    • Windows: %LOCALAPPDATA%\OpenLoomi\openloomi.exe
  6. ${CLAUDE_PLUGIN_DATA}/config.json (non-secret cached install path)
  7. --bin-path <p> explicit flag
  8. Otherwise: emit nextAction: install_openloomi

Hook events → Pet states

Claude Code hookPet state
SessionStartgreet (fallback presenting if capybara theme active)
UserPromptSubmitthinking
PreToolUse (Bash|Edit|Write|Read|Grep|Glob)working
PostToolUsethinking
Stoparchive → happy
SubagentStartjuggling
SubagentStopthinking
Notification (permission_prompt|elicitation)needsinput

idle, sleeping, sweeping, presenting are managed by the loop watcher and are not set by hooks.

Reminders for Claude

  • Never handle AI provider keys in this plugin. AI provider configuration lives in the OpenLoomi runtime; the runtime detects the user's local claude CLI auth on its own. If the user reports missing Claude CLI auth, point them at claude auth login or at OpenLoomi Desktop → API Settings for a custom endpoint.
  • Never auto-install hooks. Always require an explicit /openloomi:hooks install.
  • Always exit 0 on Stop. Archive failures are reported via stdout JSON with _openloomi.archive: "skipped", reason: ....
  • When unsure, default to running loomi-bridge setup-status --json and respond based on the structured output — don't guess.

© melandlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/claude/skills/openloomi of melandlabs/openloomi.

Open the folder on GitHubat commit 2aca101

Compare with similar skills

Openloomi next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openloomi compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openloomi this skillmelandlabs/openloomi1k—~1.4kAutomated safety check: PassApache-2.0
Agent BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
Planning With Filesjarrodwatts/claude-code-config1.1k5 repos~967Automated safety check: PassNone
Codebase Managementgiancarloerra/SocratiCode3.3k1 repos~1.8kAutomated safety check: PassAGPL-3.0
Context Compressionguanyang/open-agent-hub9772 repos~4.6kAutomated safety check: PassMIT
Looperksimback/looper710—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Agent Builder

    shareAI-lab/learn-claude-code

    Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Planning With Files

    jarrodwatts/claude-code-config

    Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.

    1.1k GitHub starsUsed in 5 repos~967 tokens
    AI & LLM EngineeringAuto-check passed
  • Codebase Management

    giancarloerra/SocratiCode

    Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.

    3.3k GitHub starsUsed in 1 repo~1.8k tokens
    AI & LLM EngineeringAuto-check passed
  • Context Compression

    guanyang/open-agent-hub

    This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization, or durable handoff summaries that preserve…

    977 GitHub starsUsed in 2 repos~4.6k tokens
    AI & LLM EngineeringAuto-check passed
  • Looper

    ksimback/looper

    Scaffold a well-designed agent loop with best-practice coaching and a cross-model review council.

    710 GitHub stars~2.7k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Docs Planner

    strands-agents/harness-sdk

    Identify documentation gaps and prioritize the docs backlog.

    8.7k GitHub stars~821 tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

More from melandlabs/openloomi

All 23 skills in this repo
  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 16 days ago
    Auto-check passed
  • Create Task

    melandlabs/openloomi

    Create an end-to-end Continual Learning Bench task. An agent skill from melandlabs/openloomi.

    1k GitHub stars~4.6k tokensUpdated 16 days ago
    Auto-check passed
  • Openloomi Memory

    melandlabs/openloomi

    openloomi Memory tools - search and manage the holistic context (people, projects, decisions, knowledge base, chat insights).

    1k GitHub stars~6k tokensUpdated 16 days ago
    Auto-check passed
  • Openloomi Setup

    melandlabs/openloomi

    OpenLoomi first-use setup and readiness guidance for skill-only agent runtimes.

    1k GitHub stars~420 tokensUpdated 16 days ago
    Auto-check passed
  • Find Skills

    melandlabs/openloomi

    Discover and install skills from the open agent skills ecosystem.

    1k GitHub stars~892 tokensUpdated 16 days ago
    Auto-check passed
  • Openloomi API

    melandlabs/openloomi

    openloomi HTTP API reference (local-first, served from the OpenLoomi Desktop app at http://localhost:3414).

    1k GitHub stars~4.2k tokensUpdated 16 days ago
    Auto-check passed

Questions about Openloomi

What does Openloomi do?

OpenLoomi runtime integration for Claude Code. An agent skill from melandlabs/openloomi. Openloomi is an agent skill from melandlabs/openloomi. OpenLoomi runtime integration for Claude Code.

When should I use Openloomi?

Openloomi fits situations like: the user mentions OpenLoomi; wants to install/configure it; query their local memory via the Loomi runtime; change the Loomi Pet state.

How do I install Openloomi in Claude Code?

Run `npx skills add melandlabs/openloomi --skill openloomi -a claude-code`. Or copy the skill folder (plugins/claude/skills/openloomi in melandlabs/openloomi) into .claude/skills/openloomi in your project. Claude Code loads it when a task matches its description.

How do I install Openloomi in Codex?

Run `npx skills add melandlabs/openloomi --skill openloomi -a codex`. Or copy the skill folder (plugins/claude/skills/openloomi in melandlabs/openloomi) into .agents/skills/openloomi in your project. Codex loads it when a task matches its description.

Can I use Openloomi in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add melandlabs/openloomi --skill openloomi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openloomi, .gemini/skills/openloomi, .github/skills/openloomi and .opencode/skills/openloomi in your project.

What does Openloomi need to run?

Going by SKILL.md and its folder, Openloomi needs the command-line tools its instructions call (claude) and credentials named OPENLOOMI_AUTH_TOKEN. Our summary lists: A credential in OPENLOOMI_AUTH_TOKEN. Its frontmatter pre-approves these tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *).

Does Openloomi access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Openloomi safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openloomi use?

Openloomi is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openloomi use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Openloomi?

Skills that share tags, products or a category with Openloomi: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Planning With Files (jarrodwatts/claude-code-config, 1.1k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars) and Context Compression (guanyang/open-agent-hub, 977 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openloomi?

melandlabs (a GitHub organization) maintains it in melandlabs/openloomi, which has 1,037 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 24, 2026.

Source: melandlabs/openloomi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.