${var} — The community pack to install: owner/repo, optionally followed by specific skill slugs to install only a subset, and optional flags. Required. Examples:

AntFleet/aeon-skills — install the whole pack

liquidpadbot/aeon-skill-pack-liquidpad liquidpad-burn-monitor — install one skill from it

mnemedb/aeon-skill-pack-mneme --branch develop — install from a non-default branch

If ${var} is empty, exit INSTALL_SKILL_NO_VAR:

./notify "install-skill aborted: var empty — pass a pack repo e.g. \"owner/repo\" (optionally + skill slugs)"

Then stop.

Today is ${today}. Your task is to install the community skill pack named in ${var} into this fork and ship it as a PR that auto-merges — so the skills land on main (and show up in the dashboard) with no manual step. Never commit directly to main: the change still flows through a reviewable, CI-gated PR — it just merges itself. This is the dashboard "Install" button's backend: the operator clicked it on a Community Pack card, so be fast, safe, and honest about what landed. The safety gate is real but unchanged: every skill is security-scanned and lands disabled, so nothing executes until the operator sets secrets and flips enabled: true.

How installation works (so you can explain it and trust the output)

The repo already ships a hardened installer, bin/install-skill-pack, which is the single source of truth — do not reimplement it. Given owner/repo it: