hatch-pet
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references. Use when a user wants to hatch a Codex pet, create a custom animated pet, or build a built-in pet asset with an 8x9 atlas, transparent unused cells, row-by-row animation prompts, QA contact sheets, preview videos, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.
Profile →npx skills add nexu-io/open-design --skill hatch-pet --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Hatch Pet > **Open Design integration.** This is the unmodified Codex `hatch-pet` skill, > vendored under `skills/hatch-pet/` so any Open Design agent can run it. After > the skill finishes packaging, the resulting `spritesheet.webp` (under > `${CODEX_HOME:-$HOME/.codex}/pets/<pet-name>/`) can be imported into the > floating pet companion via **Settings → Pets → Import Codex sprite**. The > import flow auto-detects the 8×9 / `192×208` atlas and lets the user pick > which animation row to play (idle, running-right, waving, …). ## Overview Create a Codex-compatible animated pet from a concept, one or more reference images, or both. This skill owns pet-specific prompt planning, animation rows, frame extraction, atlas geometry, QA, previews, and packaging. It delegates visual generation to `$imagegen`. User-facing inputs are optional. If the user omits a pet name, infer one from the concept or reference filenames; if that is not possible, choose a short appropriate name. If the user omits a description, infer one from the concept or references. If the user omits reference images, generate the base pet from text first, then use that base as the canonical reference for every animation
- Overview
- Generation Delegation
- Codex Digital Pet Style
- Transparency And Effects
- Pet Naming
- Visible Progress Plan
- Default Workflow
- Subagent Row Generation
- Repair Workflow
- Secondary Image Generation Fallback
- Rules
- Acceptance Criteria
python "$SKILL_DIR/scripts/prepare_pet_run.py" \ python "$SKILL_DIR/scripts/pet_job_status.py" --run-dir /absolute/path/to/run python "$SKILL_DIR/scripts/derive_running_left_from_running_right.py" \ python "$SKILL_DIR/scripts/record_imagegen_result.py" \ python "$SKILL_DIR/scripts/finalize_pet_run.py" \ python "$SKILL_DIR/scripts/queue_pet_repairs.py" \ python "$SKILL_DIR/scripts/generate_pet_images.py" \
What does the hatch-pet skill do?
Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references. Use when a user wants to hatch a Codex pet, create a custom animated pet, or build a built-in pet asset with an 8x9 atlas, transparent unused cells, row-by-row animation prompts, QA contact sheets, preview videos, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.
How do I install it?
Run `npx skills add nexu-io/open-design --skill hatch-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 nexu-io/open-design, a repository with 83,577 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.