Agent skill · Design & Presentation

openloomi-pet

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.

melandlabsgithub.com/melandlabsGitHub ↗
claude-coderead-onlyApache-2.0
Install
npx skills add melandlabs/openloomi --skill openloomi-pet --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Allowed tools: Bash(node${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs*)
Path: plugins/claude/skills/openloomi-pet/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 764
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# OpenLoomi Pet Sub-skill 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) | ## Available commands - `node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs pet <state>` — synchronous, returns JSON; use only when the user explicitly asks. - Hooks call `state <name>` automa

What's inside
Steps it walks through
  1. Available commands
  2. Help the user customize their pet's appearance
  3. Decision tree
  4. What the bridge can and can't do
  5. Filename conventions to communicate
  6. Override JSON shape to communicate
  7. Common pitfalls to surface
  8. What NOT to do from Claude
  9. See also
More from openloomi
All skills →
About this skill
What does the openloomi-pet skill do?

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.

How do I install it?

Run `npx skills add melandlabs/openloomi --skill openloomi-pet --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From melandlabs/openloomi, a repository with 764 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going