openpets
FeaturedUse when the user asks to install, configure, verify, troubleshoot, or understand OpenPets; install or select a pet; connect Claude Code, OpenCode, Cursor, Codex, or MCP clients; configure a project to use a specific pet; or debug openpets_status, openpets_react, or openpets_say.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- alvinunreal
- Repository
- alvinunreal/openpets
- Created
- 4 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
openpets
Use whenever the user wants to build, extend, debug, test, validate, locally load, package, or publish an OpenPets plugin; work with the OpenPets Plugin SDK v3, plugin manifest, plugin permissions, sandbox, plugin UI, storage, schedules, assets, or local plugin development. Also use for installing or configuring OpenPets, pets, optional coding-agent integrations, or local MCP controls. Prioritize the local-first plugin authoring experience; agent integrations are optional.
pets-setup
Wire pets into this machine's Claude Code config, or say how to install the binary. Use when the user types /pets-setup or asks to set pets up.
pet
Show, hide, or switch the Pipsqueak desktop pet