MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
OpenLoomi Pet sprite & state helper for Claude Code. An agent skill from melandlabs/openloomi.
$ npx skills add melandlabs/openloomi --skill openloomi-pet -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install melandlabs/openloomi openloomi-pet --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/claude/skills/openloomi-pet .claude/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .claude/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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/claude/skills/openloomi-petType 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-pet -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install melandlabs/openloomi openloomi-pet --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/claude/skills/openloomi-pet .agents/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .agents/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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-pet -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install melandlabs/openloomi openloomi-pet --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/claude/skills/openloomi-pet .cursor/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .cursor/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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/claude/skills/openloomi-pet--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-pet -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install melandlabs/openloomi openloomi-pet --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/claude/skills/openloomi-pet .gemini/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .gemini/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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-petInstalls 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-pet -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/claude/skills/openloomi-pet .github/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .github/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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-pet -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-pet --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/claude/skills/openloomi-pet .opencode/skills/openloomi-pet && 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-pet" agent skill from https://github.com/melandlabs/openloomi/tree/main/plugins/claude/skills/openloomi-pet into .opencode/skills/openloomi-pet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openloomi-pet", 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.
openloomi-petOpenLoomi Pet sprite & state helper for Claude Code. An agent skill from melandlabs/openloomi.
Openloomi Pet is an agent skill from melandlabs/openloomi. OpenLoomi Pet sprite & state helper for Claude Code. Use when the user wants to change their Loomi Pet state, switch theme, drop in a custom character, override individual sprites, or ask Claude to mirror its lifecycle onto the pet. Triggers: pet state, /openloomi:pet, set pet, loomi pet, pet to happy, pet to working, pet to thinking, fox sprite, capybara sprite, custom pet theme, pet-custom, pet-config, override pet sprite.
Its SKILL.md is about 1.9k 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 Agent Workflows. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 2aca101. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
nodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Openloomi Pet loads about 1.9k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 830 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.
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.
The full file from melandlabs/openloomi at commit 2aca101, republished under its Apache-2.0 licence (© melandlabs). 830 words, ~1,894 tokens.
.claude/skills/openloomi-pet/SKILL.md (or your agent's skills folder).The Loomi Pet has 9 universal state names. The plugin ships the fox
(loomi-*) sprite set for branding; the OpenLoomi runtime's
state-resolution watcher renders the matching sprite for whichever
theme you have active (fox or capybara, or any folder under
~/.openloomi/pet-custom/). State set:
| State | When to use |
|---|---|
happy | A task just completed successfully |
idle | Loomi is waiting for the next loop tick (watcher-only — do not set from Claude) |
juggling | Multiple sub-agents are running |
needsinput | Permission prompt / elicitation dialog visible |
presenting | Fresh decision requires the user's review (watcher-only — do not set from Claude) |
sleeping | Local hour outside 6–22 with no pending work (watcher-only — do not set from Claude) |
sweeping | User dismissed a card just now (watcher-only) |
thinking | Between steps, awaiting LLM response |
working | A tool call is in progress (PreToolUse hook fires this) |
node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs pet <state> — synchronous, returns JSON; use only when the user explicitly asks.state <name> automatically (fire-and-forget, 2s timeout).Sprite set is hardcoded in the bridge — invalid state names are rejected
before any HTTP call. The endpoint POST /api/pet/state may not yet exist
in the target OpenLoomi runtime; the bridge falls back to "would have set
state to X — pending OpenLoomi endpoint" without raising an error.
The bridge only drives the state — sprite overrides and theme folders
are file-based and live outside the plugin. When the user asks to "change
the pet's look" or "add a custom character", walk them through the file
system. Do not try to write pet-config.json from the bridge; the
bridge has no such command and the runtime's file watcher does the work.
Theme → Fox / Theme → Capybara. Persisted in ~/.openloomi/pet-config.json under activeTheme. Long-press (~600 ms) is the fallback if contextmenu is swallowed by the host.~/.openloomi/pet-custom/<name>/ with PNGs named after the states. The watcher auto-discovers it within ~250 ms and the theme appears in the menu.~/.openloomi/pet-config.json's overrides map. Wins over both built-ins and custom-theme sprites for the matching (theme, state) pair.activeTheme to the custom theme's folder name.| User intent | Bridge role |
|---|---|
Flip to happy mid-task | /openloomi:pet happy — yes |
| Switch fox ↔ capybara | No — that's a menu action or pet-config.json edit; do not try the bridge |
| Add a custom character | No — direct them to ~/.openloomi/pet-custom/<name>/ and the file watcher |
| Override a single sprite | No — direct them to ~/.openloomi/pet-config.json's overrides map |
| Diagnose "the pet isn't switching themes" | Direct them to the troubleshooting section in pet docs |
| Drive the pet from their own tool | Direct them to POST /api/pet/state — see Pet API |
When guiding the user through a custom theme, surface these conventions up-front:
.gif, .webp, .apng, .lottie are silently ignored.idle.png, loomi-idle.png, capybara-thinking.png, my-pack-sweeping.png all normalize correctly (case-insensitive).idle sprite..git, .DS_Store etc.The overrides map is camelCase on the wire — activeTheme, customThemesDir. Snake_case keys silently no-op the assignment (a unit test in the runtime pins the contract). Use the exact shape:
{
"version": 1,
"activeTheme": "fox",
"customThemesDir": "~/.openloomi/pet-custom",
"overrides": {
"fox": {
"idle": "/absolute/path/to/my-fox-idle.png"
}
}
}Absolute paths only — the runtime routes them through tauri::convertFileSrc, so relative paths and ~/ prefixes will not resolve.
[loomi-pet/theme] failed to parse ~/.openloomi/pet-config.json means the JSON itself is malformed and defaults loaded. Host log line [loomi-pet/theme] failed to read <path>: <io error> means the path doesn't resolve.activeTheme, not active_theme.sleeping / sweeping rejected by /api/pet/state — those are watcher-only vocabulary; the runtime returns 400 invalid_state. Do not POST them from your tool.POST /api/pet/state with sleeping or sweeping. The API rejects them; the watcher owns them.pet-config.json from the bridge. The bridge has no command for it; the file watcher owns updates.CAPYBARA_STATES rejects them before any HTTP call.POST /api/pet/state for external tools© 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
Just SKILL.md in plugins/claude/skills/openloomi-pet of melandlabs/openloomi.
Open the folder on GitHubat commit 2aca101
Openloomi Pet 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 Pet this skillmelandlabs/openloomi | 1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
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…
melandlabs/openloomi
Create an end-to-end Continual Learning Bench task. An agent skill from melandlabs/openloomi.
melandlabs/openloomi
openloomi Memory tools - search and manage the holistic context (people, projects, decisions, knowledge base, chat insights).
melandlabs/openloomi
OpenLoomi first-use setup and readiness guidance for skill-only agent runtimes.
melandlabs/openloomi
Discover and install skills from the open agent skills ecosystem.
melandlabs/openloomi
OpenLoomi runtime integration for Claude Code. An agent skill from melandlabs/openloomi.
Categories
OpenLoomi Pet sprite & state helper for Claude Code. An agent skill from melandlabs/openloomi. Openloomi Pet is an agent skill from melandlabs/openloomi. OpenLoomi Pet sprite & state helper for Claude Code.
Openloomi Pet fits situations like: the user wants to change their Loomi Pet state; drop in a custom character; override individual sprites; ask Claude to mirror its lifecycle onto the pet.
Run `npx skills add melandlabs/openloomi --skill openloomi-pet -a claude-code`. Or copy the skill folder (plugins/claude/skills/openloomi-pet in melandlabs/openloomi) into .claude/skills/openloomi-pet in your project. Claude Code loads it when a task matches its description.
Run `npx skills add melandlabs/openloomi --skill openloomi-pet -a codex`. Or copy the skill folder (plugins/claude/skills/openloomi-pet in melandlabs/openloomi) into .agents/skills/openloomi-pet in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add melandlabs/openloomi --skill openloomi-pet -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-pet, .gemini/skills/openloomi-pet, .github/skills/openloomi-pet and .opencode/skills/openloomi-pet in your project.
Going by SKILL.md and its folder, Openloomi Pet needs the command-line tools its instructions call (node). Its frontmatter pre-approves these tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs *).
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.
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.
Openloomi Pet 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.
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Openloomi Pet: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.