OpenPet

Virtual pet (Tamagotchi-style) game for chat platforms. Triggers on pet commands like "feed pet", "pet status", "play with pet", "name pet", "pet sleep", "new pet". Supports multi-user across Discord, WhatsApp, Telegram, etc. Each user gets their own pet that evolves based on care.

Security Scan

The skill's declared purpose (a cross-platform virtual pet) matches its instructions and requirements; it is an instruction-only skill that reads/writes local pet JSON files and asks the operator to schedule a periodic 'tick' job — no credentials, remote downloads, or surprises were found.

Purpose & Capability

Name/description align with the runtime instructions: a Tamagotchi-like game stored per user in tamagotchi/pets/{platform}_{userId}.json. The actions, evolution rules, decay schedule, and platform mappings are consistent with a multi-platform pet skill.

Instruction Scope

Instructions require creating/reading/writing JSON state files under a local tamagotchi/pets/ directory and scheduling a periodic cron job to apply decay. These behaviors are expected for the stated purpose, but note that the skill explicitly instructs system-level scheduling (cron) and local file writes — you should confirm that the agent has permission to create the directory and cron job and that this behavior is acceptable in your environment.

Install Mechanism

No install specification and no code files are included — the skill is instruction-only. There are no downloads or extraction steps to review in the registry package. (README contains an example 'openclaw skills install github:mdealiaga/openpet' command, which is informational and not part of the registry install spec.)

Credentials

The skill requests no environment variables, credentials, or external config paths. The state storage is local JSON files that contain non-sensitive metadata (user IDs, display names, pet stats). No secrets are requested or implied by the SKILL.md.

Persistence & Privilege

The skill does not request always:true and is user-invocable. It does instruct setting up a recurring cron job (openpet-tick) which grants it ongoing behavior in the system — this is expected for a time-decay mechanic but does require operator action and appropriate permissions to create the cron entry.

Assessment

This skill appears internally consistent with its stated purpose, but before installing consider: (1) The SKILL.md tells the agent to create and maintain local JSON files under a tamagotchi/pets/ directory — confirm you are okay with that data being written to the agent's working filesystem and verify retention/backup policies. (2) It asks you to set up a cron job to apply periodic decay; that requires permission to create system cron entries and is an operational action — only set it up if you trust the runtime environment. (3) The README shows an example install from a GitHub repo (mdealiaga/openpet) while the registry metadata lists no homepage/source — if you plan to fetch or run external code, verify the upstream repository and review its code. (4) Pet files include user IDs and owner names (no secrets), so privacy concerns are limited but consider whether storing platform identifiers locally is acceptable for your deployment. If you need higher assurance, request the upstream source code or an explicit install artifact to review before enabling the cron job or running any external install steps.

Virtual pet game. Each user gets one pet, tracked by {platform}_{userId}.

State

Pets stored in tamagotchi/pets/{platform}_{userId}.json:

{
  "name": "Blobby",
  "species": "blob",
  "hunger": 30,
  "happiness": 70,
  "energy": 50,
  "age": 5,
  "born": "2026-02-01T12:00:00Z",
  "lastUpdate": 1738442780000,
  "alive": true,
  "evolution": 1,
  "totalFeedings": 12,
  "totalPlays": 8,
  "ownerId": "202739061796896768",
  "platform": "discord",
  "ownerName": "mattzap"
}

Create tamagotchi/pets/ directory if missing.

Commands

Trigger	Action
pet, pet status	Show stats + ASCII art
feed pet	hunger -30, happiness +5
play with pet	happiness +25, energy -20
pet sleep	energy +40, happiness +5
name pet [name]	Set pet name
new pet	Reset (only if dead or confirm)
pet help	Show commands

New User Flow

1. Any pet command from unknown user → create egg
2. First interaction → hatch to blob
3. Show welcome message + commands

Stats Display

    ╭──────────╮
    │ (◕‿◕)    │
    │   ♥      │
    │ "Name"   │
    ╰──────────╯
    
 ❤️ Happiness: ████████░░░░  70%
 🍖 Hunger:    ███░░░░░░░░░  30%
 ⚡ Energy:    █████░░░░░░░  50%

Use sprites from references/sprites.json. Mood = happy (≥70), neutral (40-69), sad (<40).

Evolution

Stage	Requirement
egg → blob	First interaction
blob → cat	age ≥10, feedings ≥15, plays ≥10
cat → dragon	age ≥30, feedings ≥50, plays ≥40

Check evolution after each interaction. Announce with fanfare.

Death

Pet dies if: hunger ≥ 100 OR happiness ≤ 0

BUT if immortalMode: true in config, pets don't die — they just get very sad and hungry. Stats cap at 99/1 instead of triggering death. Default is immortal mode ON.

Show memorial (if death enabled), offer new pet to restart.

Decay (Cron)

Set up cron job openpet-tick every 2 hours:

• hunger +15, happiness -10, energy -5
• Clamp all stats 0-100
• Check death conditions
• Alert owner if critical (hunger >80 or happiness <20)
• Increment age daily

Platform Detection

Extract from message context:

• Discord: discord_{userId}
• WhatsApp: whatsapp_{phoneNumber}
• Telegram: telegram_{chatId}
• Signal: signal_{uuid}

Alerts

Send to user's origin platform when:

• Pet is hungry (>80): "🍖 {name} is starving!"
• Pet is sad (<20): "😢 {name} misses you!"
• Pet died: "💀 {name} has passed away..."
• Evolution: "✨ {name} evolved into a {species}!"