AI SummaryThe Loomi Pet has 9 universal state names. The plugin ships the fox () sprite set for branding; the OpenLoomi runtime's state-resolution watcher renders the matching sprite for whichever
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "openloomi-pet" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/openloomi-pet && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/openloomi-pet/SKILL.md "https://raw.githubusercontent.com/melandlabs/openloomi/main/plugins/claude/skills/openloomi-pet/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
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.
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> 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. ---
Help the user customize their pet's appearance
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.
Decision tree
• "I just want the other built-in" → right-click Loomi → 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. • "I want my own character" → drop a folder at ~/.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. • "I want to change just one sprite" → edit ~/.openloomi/pet-config.json's overrides map. Wins over both built-ins and custom-theme sprites for the matching (theme, state) pair. • "I want to make my theme the default" → set activeTheme to the custom theme's folder name.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster