ha-pet-import

Import, validate, and activate desktop pets in Hope Agent from any source.

1.6k|149|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/shiwenwen/hope-agent --skill ha-pet-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-pet-import
Source: https://github.com/shiwenwen/hope-agent/tree/main/skills/ha-pet-import
Command: npx skills add https://github.com/shiwenwen/hope-agent --skill ha-pet-import

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Installing a desktop pet in Hope Agent from arbitrary origins (websites, zip archives, chat attachments, cloud files) is risky and error-prone: packages may be malformed, sources may push unsafe installers, and manual file copying bypasses Hope's validation. This Skill routes every pet package through Hope's official validator and atomic installer so imports are safe and consistent.

Core Features & Use Cases

  • Universal source resolution: Accepts local folders with pet.json, zip archives, standalone PNG/WebP sprite atlases, chat attachments, repository or cloud files, direct HTTPS artifact URLs, and even ordinary download pages whose HTML is inspected to find the real package bytes.
  • Preview-confirm-commit workflow: Runs hope-agent pet preview to show display name, dimensions, validation warnings, and package hash, then commits only after explicit user confirmation with hash verification.
  • Select and enable installed pets: Lists installed pets, resolves exact petRef matches, and activates a pet on the desktop via the authenticated Pet API without exposing credentials.
  • Use Case: A user finds a pet on a community download page. The Skill inspects the page, extracts the actual zip or manifest plus sprite, previews it through Hope's validator, and after confirmation imports and optionally enables it.

Quick Start

Ask the assistant to import a pet into Hope Agent from a given URL, zip file, or folder, for example: "Import this pet package into Hope and enable it."

Frequently Asked Questions about ha-pet-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import a desktop pet into Hope Agent?

Provide any package source such as a zip file, a folder with pet.json and its sprite, a standalone atlas image, or a direct HTTPS URL. The Skill runs hope-agent pet preview for validation, shows you the result, and commits only after your confirmation.

What pet package formats does Hope Agent support?

Hope accepts folders containing pet.json or legacy avatar.json with a sprite, zip archives, pet.json with a relative PNG/WebP sprite, and standalone 1536x1872 or 1536x2288 PNG/WebP atlases. Loose manifest and sprite files can be passed together as repeated sources.

Can I import a pet from an ordinary download page?

Yes. The Skill inspects the page's HTML, scripts, and referenced resources to locate the real zip, manifest, or sprite bytes and feeds those to Hope. It never runs the site's installer or treats the page itself as the package.

How do I enable or switch to an already installed pet in Hope?

The Skill lists installed pets with hope-agent pet list, resolves the exact petRef, and calls hope-agent pet activate to enable it on the desktop. Activation is desktop-only because the running Tauri process owns the native pet window.

Why does pet import fail with pet_cli_local_source_unavailable_to_host?

This error means the local source file exists only inside an isolated exec environment and cannot reach the host. Materialize the package durably in the conversation workspace or use a direct HTTPS artifact URL instead.

Does importing a pet automatically enable it?

No. Import only adds the package to Hope's library. The active desktop pet changes only when you explicitly ask to enable, use, activate, select, or switch to it, and enablement runs as a separate activation step.