Personal Assistant
ailabs-393/ai-labs-claude-skills
This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or…
Use local OpenLoomi from Codex. An agent skill from melandlabs/openloomi.
Apache-2.0Auto-check passed
Install Openloomi
$ npx skills add melandlabs/openloomi --skill openloomi -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install melandlabs/openloomi openloomi --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/codex/skills/openloomi .claude/skills/openloomi && rm -rf skills-srcUse ~/.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/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .claude/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add melandlabs/openloomi --skill openloomi -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install melandlabs/openloomi openloomi --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/codex/skills/openloomi .agents/skills/openloomi && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .agents/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add melandlabs/openloomi --skill openloomi -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install melandlabs/openloomi openloomi --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/codex/skills/openloomi .cursor/skills/openloomi && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .cursor/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/melandlabs/openloomi.git --path plugins/codex/skills/openloomi--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add melandlabs/openloomi --skill openloomi -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install melandlabs/openloomi openloomi --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/codex/skills/openloomi .gemini/skills/openloomi && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .gemini/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install melandlabs/openloomi openloomiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add melandlabs/openloomi --skill openloomi -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/codex/skills/openloomi .github/skills/openloomi && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .github/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add melandlabs/openloomi --skill openloomi -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install melandlabs/openloomi openloomi --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/melandlabs/openloomi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/codex/skills/openloomi .opencode/skills/openloomi && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openloomi" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi into .opencode/skills/openloomi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openloomi- GitHub stars
- 1k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 592 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Use local OpenLoomi from Codex. An agent skill from melandlabs/openloomi.
- Calls node
What it does
Openloomi is an agent skill from melandlabs/openloomi. Use local OpenLoomi from Codex. Triggers: Loomi, OpenLoomi, personal assistant, memory, workspace context, setup, install openloomi, setup openloomi, 一键装好并跑起来, finalize openloomi, fix openloomi, openloomi tour, guided tour, walk me through openloomi, show me everything, 一条龙, 体验一下, 带我看一下.
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.
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.
Example prompts
- “/openloomi”
Requirements
- Pre-approved tools (allowed-tools): Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *)
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 $SKILL_DIR/../../scripts/loomi-bridge.mjs *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
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 no API keys, tokens, secrets or passwords.
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 75 tokens; SKILL.md has 592 words of instructions outside code blocks.
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). 592 words, ~1,389 tokens.
Download SKILL.mdSave it as
.claude/skills/openloomi/SKILL.md (or your agent's skills folder).- name
- openloomi
- description
- Use local OpenLoomi from Codex. Triggers: Loomi, OpenLoomi, personal assistant, memory, workspace context, setup, install openloomi, setup openloomi, 一键装好并跑起来, finalize openloomi, fix openloomi, openloomi tour, guided tour, walk me through openloomi, show me everything, 一条龙, 体验一下, 带我看一下.
- allowed-tools
- Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *)
OpenLoomi
Use this skill when the user wants Codex to work with OpenLoomi as a local personal assistant, memory layer, or setup guide.
This skill is intentionally thin. It calls the local bridge and lets OpenLoomi own runtime execution, memory, connectors, settings, and secret storage.
Before taking action, check plugin readiness:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-statusIf the bridge returns ready: false, follow the reported nextAction. Do not
ask the user to paste API keys, OAuth tokens, connector secrets, or OpenLoomi
auth tokens into Codex chat.
When setup-status returns loopbackAccessAmbiguous: true, do not conclude
that OpenLoomi is stopped. Codex network sandboxing can block access to the
host's localhost even while the desktop API is listening. Prefer the
bridge's own auto-recovery path over manual lsof / curl paste: invoke
node $SKILL_DIR/../../scripts/loomi-bridge.mjs run-host-probefrom a Codex shell where loopback is allowed. The command probes
/api/native/providers outside the sandbox, writes the result to
~/.openloomi/codex-host-probe-cache.json (5 minute TTL), and the very next
setup-status call rebuilds its readiness decision from that cache
(ready: true, reason: "READY_VIA_HOST_PROBE_CACHE"). When setup-status
returns nextAction: "run_host_probe", run this command yourself instead of
asking the user to paste anything. Fall back to the manual
loopbackAccess.verification.commands only if the host probe itself fails.
OpenLoomi guest sessions are supported. A missing token is not a request for
account registration or manual token entry. When the bridge reports
initialize_openloomi_session or open_openloomi, initialize a guest/session
through OpenLoomi-owned surfaces:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" initialize-sessionFor installation guidance, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" install-instructionsIf the user asks to install OpenLoomi or explicitly approves installation, run the end-to-end wizard in one invocation:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup --yesThat walks the whole state machine: resolve the official release → download → install → set OPENLOOMI_AGENT_PROVIDER=codex in the GUI launchd / environment.d → launch the OpenLoomi desktop app → wait for the local API on http://localhost:3414 → mint a guest session token into ~/.openloomi/token. Invoking this skill (or the user saying "install" / "install and run" / "一键装好并跑起来") counts as explicit approval to pass --yes. Sandbox prompts for network / install to /Applications / launching the GUI will appear — that's expected; approve them and the wizard continues.
The bridge resolves the official GitHub release artifact for the current
platform and architecture automatically, downloads it, and installs it with the
default installer path when automatic installation is supported. Only pass
--artifact-url when the user explicitly provides an official allowlisted
artifact URL as an override. Add --download-only only when the user asks to
download without installing. Add --launch only when the user asks to use the
interactive installer UI instead of default automatic installation. Add
--sha256 "<official checksum>" only when the user wants to require a specific
checksum; otherwise the bridge verifies GitHub release digest metadata when
available.
Show full SKILL.md (170 more words)Show less
For bridge metadata, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" versionFor available OpenLoomi workflows, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidanceFor workflow-specific guidance, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidance --workflow openloomi-loop
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidance --workflow openloomi-memory
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" workflow-guidance --workflow openloomi-connectorsUse the thin wrapper skills when the user specifically asks for loop, memory, or connector readiness workflows. The plugin must not copy OpenLoomi connector, memory, or loop logic into Codex.
Launching the desktop app with the Codex runtime
When OpenLoomi is used from Codex, prefer the desktop Codex runtime so OpenLoomi can reuse the user's existing Codex CLI runtime for the first workflow.
When the user asks to make OpenLoomi spawn Codex as the native-agent executor, or diagnostics show that the desktop runtime is not using Codex, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" codex-runtime-infoShow the returned platform-specific guidance. The /openloomi:setup
wizard auto-restarts the desktop app after writing the env var, so if
setup was used end-to-end the new env is already in effect — just verify
/api/native/providers reports defaultAgent: "codex". If instead the
env was written via a direct set-codex-runtime-env invocation, ask the
user to Quit+Reopen OpenLoomi Desktop so the freshly forked web server
inherits the new value, then verify the same endpoint.
© 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/codex/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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openloomi this skillmelandlabs/openloomi | 1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Personal Assistantailabs-393/ai-labs-claude-skills | 455 | — | ~4.9k | Automated safety check: Pass | MIT | |
| Generic Assistantmastra-ai/mastra | 29k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Adding Warehouse Person PropertiesPostHog/posthog | 40k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Personal Assistant Reviewedonyzpc/personal-assistant | 148 | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| N8n Docs Assistantn8n-io/n8n | 207k | — | ~550 | Automated safety check: Pass | Custom licence |
Similar skills
Generic Assistant
mastra-ai/mastra
Fallback authoring playbook for building general-purpose personal assistant agents that do not fit a more specific archetype.
- Official
Adding Warehouse Person Properties
PostHog/posthog
Sync columns from a synced data warehouse table onto PostHog person or group properties, so warehouse data becomes usable anywhere person and group properties already work: feature flag targeting…
Personal Assistant Review
edonyzpc/personal-assistant
Review uncommitted or PR diffs in the personal-assistant Obsidian plugin with project-specific risk lanes, second-layer future-risk checks, severity discipline, subagent review routing, and…
- Official
N8n Docs Assistant
n8n-io/n8n
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs.
Build A Personal Skill From History
THU-MAIC/OpenMAIC
Derives a reusable personal skill for course-making from a representative sample of the user's own past classrooms and chat history, confirmed with them before saving.
More from melandlabs/openloomi
All 23 skills in this repoOpenloomi 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…
Create Task
melandlabs/openloomi
Create an end-to-end Continual Learning Bench task. An agent skill from melandlabs/openloomi.
Openloomi Memory
melandlabs/openloomi
openloomi Memory tools - search and manage the holistic context (people, projects, decisions, knowledge base, chat insights).
Openloomi Setup
melandlabs/openloomi
OpenLoomi first-use setup and readiness guidance for skill-only agent runtimes.
Find Skills
melandlabs/openloomi
Discover and install skills from the open agent skills ecosystem.
Openloomi
melandlabs/openloomi
OpenLoomi runtime integration for Claude Code. An agent skill from melandlabs/openloomi.
Questions about Openloomi
What does Openloomi do?
Use local OpenLoomi from Codex. An agent skill from melandlabs/openloomi. Openloomi is an agent skill from melandlabs/openloomi. Use local OpenLoomi from Codex.
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/codex/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/codex/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 (node). Its frontmatter pre-approves these tools: Bash(node $SKILL_DIR/../../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.6k 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: Personal Assistant (ailabs-393/ai-labs-claude-skills, 455 stars), Generic Assistant (mastra-ai/mastra, 29k stars), Adding Warehouse Person Properties (PostHog/posthog, 40k stars) and Personal Assistant Review (edonyzpc/personal-assistant, 148 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,038 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.