القائمة
Use when the user wants to update the installed yuumi skills to their latest published versions — pulls only the yuumi pack, leaving every other skill source untouched
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | yuumi:update |
| description | Use when the user wants to update the installed yuumi skills to their latest published versions — pulls only the yuumi pack, leaving every other skill source untouched |
| version | 1.6.4 |
Update only the yuumi skills to their latest published versions, without touching any other installed skill source.
The plain npx skills update refreshes every skill from every source you have installed (Vercel's packs, agent-browser, whatever else). When you only want the yuumi pack current, that's a blunt instrument. This skill scopes the update to yuumi alone.
npx skills update accepts an explicit list of skill names. So the move is: ask the CLI which yuumi skills are installed, then hand exactly those names back to update.
names=$(npx skills list -g --json | grep -oE '"yuumi:[^"]*"' | tr -d '"' | sort -u)
[ -z "$names" ] && { echo "No yuumi skills installed — run: npx skills add -g heeseon87/yuumi"; exit 0; }
echo "$names" | xargs npx skills update -g -y
The extraction matches the installed yuumi skill names (yuumi:edit, yuumi:pretty, …). The yuumi: colon form only appears in the JSON name values — install paths use the hyphen form (yuumi-edit), so this match never catches a path by accident.
The empty-name guard is not optional. If extraction returns nothing and you pipe an empty list into update, the CLI falls back to updating everything — the exact blunt behavior this skill avoids. Always confirm names is non-empty before calling update.
npx skills add -g heeseon87/yuumi — nothing is installed to update.update. It reports each skill as updated or already current.settings.json points at the stable ~/.claude/skills/yuumi-statusline-setup/assets/statusline.mjs path, and the CLI's symlink install preserves the executable bit, so a normal update needs no follow-up. Only if the HUD looks broken afterward, nudge the user to run /yuumi-statusline-setup (or /yuumi-statusline-doctor to diagnose). Skip this note entirely on other agents.-g (npx skills add -g heeseon87/yuumi), so this skill uses -g throughout. If the user installed project-locally, swap -g for -p.npx skills update is the same across Claude Code, Codex, Cursor, Hermes, and every other agent the CLI supports — this skill is not Claude Code-specific (only the optional statusline note is).Use when the Kickbacks/vibe-ads ad extension owns the Claude Code statusline and the user wants the Yuumi Tokyo Night statusline back WITHOUT removing the ad — installs a combined HUD+ad statusline and locks it against the extension's rewrites (Claude Code only; macOS/Linux)
Agree on domain, package location, responsibility, and function signatures before implementing — sketch the skeleton, record a design note, hand off code to yuumi:implement. Invoke by hand.
Use when a document carries inline {curly-brace} edit notes to apply in place, or when scattered edits across long drafts or multiple files must stay consistent — no copy-paste round-trips
Use when a file, endpoint, module, system, concept, or change (a PR, branch, or diff) needs to be genuinely understood, not skimmed — renders a single-file Anthropic-style HTML explainer that installs a mental model in one read; add a comprehension quiz when the user wants their understanding verified ("a quiz I must pass")
Use when implementing a spec whose reviewer will need the decision trail — resolved ambiguities, deviations, tradeoffs, open questions — not just the diff; keeps a running single-file HTML decision log alongside the code
Use when a plan or spec needs pressure-testing before you build it — finds the holes through an in-depth interview rather than a passive review