Engine Test Helper Generator
Donchitos/Claude-Code-Game-Studios
Generates engine-specific test helper libraries with assertion utilities, factory functions and mocks, placed where the engine's test runner compiles them.
OpenLoomi install & first-use setup helper for Codex. An agent skill from melandlabs/openloomi.
Apache-2.0Auto-check passed
Install Openloomi Install
$ npx skills add melandlabs/openloomi --skill openloomi-install -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install melandlabs/openloomi openloomi-install --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-install .claude/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .claude/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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/openloomi-installType 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-install -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install melandlabs/openloomi openloomi-install --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-install .agents/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .agents/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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-install -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install melandlabs/openloomi openloomi-install --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-install .cursor/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .cursor/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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-install--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-install -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install melandlabs/openloomi openloomi-install --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-install .gemini/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .gemini/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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 openloomi-installInstalls 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-install -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-install .github/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .github/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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-install -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-install --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-install .opencode/skills/openloomi-install && 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-install" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-install into .opencode/skills/openloomi-install/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-install", 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-install- GitHub stars
- 1k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 611 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
OpenLoomi install & first-use setup helper for Codex. An agent skill from melandlabs/openloomi.
- Works in 3 steps: **Always run setup (and the loopback… → node… → Based on nextAction / reason
- The user wants to install OpenLoomi
- SKILL.md covers Quick workflow, Sandbox and installation, Codex runtime setup and Reminder: secrets contract
- Calls node and codex
What it does
Openloomi Install is an agent skill from melandlabs/openloomi. OpenLoomi install & first-use setup helper for Codex. Use when the user wants to install OpenLoomi, configure it, or troubleshoot INSTALLREQUIRED / SOURCEFOUNDAPPNOTBUILT / SESSIONINITIALIZATIONREQUIRED after running setup-status. Triggers: install openloomi, configure openloomi, setup openloomi, openloomi not installed, openloomi not finalized, installrequired, install missing, guest session.
Its SKILL.md is about 1.3k 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.
When your agent uses it
- The user wants to install OpenLoomi
- Troubleshoot INSTALLREQUIRED / SOURCEFOUNDAPPNOTBUILT / SESSIONINITIALIZATIONREQUIRED after running setup-status
Example prompts
- “/openloomi-install”
Requirements
- Pre-approved tools (allowed-tools): Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- **Always run setup (and the loopback checks below) outside the Codex
- node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status
- Based on nextAction / reason
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:
nodecodex
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 Install loads about 1.3k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 611 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). 611 words, ~1,276 tokens.
Download SKILL.mdSave it as
.claude/skills/openloomi-install/SKILL.md (or your agent's skills folder).- name
- openloomi-install
- description
- OpenLoomi install & first-use setup helper for Codex. Use when the user wants to install OpenLoomi, configure it, or troubleshoot `INSTALL_REQUIRED` / `SOURCE_FOUND_APP_NOT_BUILT` / `SESSION_INITIALIZATION_REQUIRED` after running setup-status. Triggers: install openloomi, configure openloomi, setup openloomi, openloomi not installed, openloomi not finalized, install_required, install missing, guest session.
- allowed-tools
- Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *)
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
- Always run
setup(and the loopback checks below) outside the Codex sandbox — the install + launch path needs writes to/Applications, desktop GUI launch, andhttp://localhost:3414. Defaultread-only/workspace-writemodes will silently fail. Ask the user to dropsandbox=workspace-write(or move todanger-full-access) before invoking the bridge. node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status- Based on
nextAction/reason:
| Reason / nextAction | Action |
|---|---|
install_openloomi / INSTALL_REQUIRED | OpenLoomi Desktop is not on this machine. Call setup --yes to run the end-to-end wizard in one invocation: resolve → download → install → set OPENLOOMI_AGENT_PROVIDER=codex → launch the desktop app → wait for the local API → mint a guest session token. Invoking this skill counts as explicit approval to pass --yes. For offline / corporate-proxy installs, point the user at the restricted-network guide (link below) and call install-instructions first. |
SOURCE_FOUND_APP_NOT_BUILT | A source checkout is present but the OpenLoomi Desktop GUI app has not been built yet. Recommend either building the source per the OpenLoomi repo's Tauri build docs (or run loomi-bridge install-instructions) or installing the packaged Desktop release. |
open_openloomi / OPENLOOMI_API_UNREACHABLE / SESSION_INITIALIZATION_REQUIRED | OpenLoomi is installed but the local API or guest/session token is not ready. Ask the user to open OpenLoomi Desktop once, or run setup so the bridge can launch/init through OpenLoomi-owned surfaces. |
inspect_codex_runtime | OpenLoomi is up but the native Codex provider is not the active default agent. Have the user confirm the Codex CLI is installed (codex --version) and rerun setup so the runtime env + LaunchAgent get re-applied. |
Before applying the API-unreachable row, inspect loopbackAccessAmbiguous.
When it is true, the result is inconclusive because the current Codex sandbox
may block host loopback traffic. Request approval and run
loopbackAccess.verification.commands outside the sandbox. Only tell the user
to restart OpenLoomi if the outside-sandbox checks also fail.
Show full SKILL.md (294 more words)Show less
Sandbox and installation
Downloading and installing OpenLoomi can require capabilities that are blocked inside the current Codex sandbox:
- GitHub release lookup and artifact download require network access.
- The default installer may write to a system application directory such as
/Applications. - Interactive installers and launching OpenLoomi Desktop require GUI/process access outside the sandbox.
When an install command fails with a likely network, permission, filesystem, or
GUI sandbox error, request approval and retry the same loomi-bridge command
outside the sandbox. Do not work around the bridge by downloading or installing
the artifact with unrelated commands. Do not report that the release URL is
invalid or the installer is broken until the approved retry also fails.
Codex runtime setup
If the user is setting up OpenLoomi from Codex, explicitly asks to switch the desktop runtime executor to Codex, or diagnostics show a native-agent provider mismatch, call:
node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" codex-runtime-infoReminder: secrets contract
- The bridge never reads AI provider env vars and never reports provider readiness from
/api/preferences/ai— it only checks whether the native Codex runtime is active via/api/native/providers. Provider configuration is the OpenLoomi runtime's job, surfaced through the desktop app's own settings UI. - 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-keyas an argv flag. The bridge has no such flag, by design. - The bridge's end-to-end wizard is
setup --yes(one-shot: install + set codex provider + launch desktop + mint guest session token). Invoke it from this skill when the user asks to install or finalize OpenLoomi. Do not callinstall-openloomi --confirmby itself — that only installs and leaves the desktop app unlaunched and the session token unminted. Useinstall-openloomi --confirmonly when the user explicitly asks to install without launching (rare).
© 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-install of melandlabs/openloomi.
Open the folder on GitHubat commit 2aca101
Compare with similar skills
Openloomi Install 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 Install this skillmelandlabs/openloomi | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Engine Test Helper GeneratorDonchitos/Claude-Code-Game-Studios | 26k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Review Helpershashicorp/terraform-provider-aws | 11k | — | ~978 | Automated safety check: Pass | MPL-2.0 | |
| Review Tests Helpershashicorp/terraform-provider-aws | 11k | — | ~994 | Automated safety check: Pass | MPL-2.0 | |
| Qwen Code HelperQwenLM/qwen-code | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Odoo Migration Helpersickn33/agentic-awesome-skills | 47k | 2 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Review Helpers
hashicorp/terraform-provider-aws
Review Terraform AWS Provider helper code: finders, status functions, waiters, sweepers, data sources, and list resources.
- Official
Review Tests Helpers
hashicorp/terraform-provider-aws
Review Terraform AWS Provider test helpers: Exists/Destroy check functions, exportstest.go wiring, create.Error wrapping, data source tests, list resource tests (querycheck + Terraform version…
Qwen Code Helper
QwenLM/qwen-code
Answers questions about Qwen Code usage, configuration and troubleshooting from its bundled docs, and can view or change your settings.json on request.
Odoo Migration Helper
sickn33/agentic-awesome-skills
Step-by-step guide for migrating Odoo custom modules between versions (v14→v15→v16→v17).
Pagination Helper
jeremylongshore/tons-of-skills-marketplace
Configure with pagination helper operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.
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 Install
What does Openloomi Install do?
OpenLoomi install & first-use setup helper for Codex. An agent skill from melandlabs/openloomi. Openloomi Install is an agent skill from melandlabs/openloomi. OpenLoomi install & first-use setup helper for Codex.
When should I use Openloomi Install?
Openloomi Install fits situations like: the user wants to install OpenLoomi; troubleshoot INSTALLREQUIRED / SOURCEFOUNDAPPNOTBUILT / SESSIONINITIALIZATIONREQUIRED after running setup-status.
How do I install Openloomi Install in Claude Code?
Run `npx skills add melandlabs/openloomi --skill openloomi-install -a claude-code`. Or copy the skill folder (plugins/codex/skills/openloomi-install in melandlabs/openloomi) into .claude/skills/openloomi-install in your project. Claude Code loads it when a task matches its description.
How do I install Openloomi Install in Codex?
Run `npx skills add melandlabs/openloomi --skill openloomi-install -a codex`. Or copy the skill folder (plugins/codex/skills/openloomi-install in melandlabs/openloomi) into .agents/skills/openloomi-install in your project. Codex loads it when a task matches its description.
Can I use Openloomi Install 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-install -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-install, .gemini/skills/openloomi-install, .github/skills/openloomi-install and .opencode/skills/openloomi-install in your project.
What does Openloomi Install need to run?
Going by SKILL.md and its folder, Openloomi Install needs the command-line tools its instructions call (node and codex). Its frontmatter pre-approves these tools: Bash(node $SKILL_DIR/../../scripts/loomi-bridge.mjs *).
Does Openloomi Install 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 Install 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 Install use?
Openloomi Install 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 Install use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Install?
Skills that share tags, products or a category with Openloomi Install: Engine Test Helper Generator (Donchitos/Claude-Code-Game-Studios, 26k stars), Review Helpers (hashicorp/terraform-provider-aws, 11k stars), Review Tests Helpers (hashicorp/terraform-provider-aws, 11k stars) and Qwen Code Helper (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openloomi Install?
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.