菜单
Add a one-time install task to root mise.toml to sync a hand-installed app from this machine to the other one. Use when the user says something like "I installed Vibe Island on this computer, create a task to add it to my other computer". See CLAUDE.md "One-time install lifecycle".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-install-task |
| description | Add a one-time install task to root mise.toml to sync a hand-installed app from this machine to the other one. Use when the user says something like "I installed Vibe Island on this computer, create a task to add it to my other computer". See CLAUDE.md "One-time install lifecycle". |
Create a new one-time install task in root mise.toml. The task exists so the
other machine can install the app via mise run <name> after being nudged by
a sync reminder. After running, the task self-stows to setup/mise.toml.
The user will name an app (e.g. "Vibe Island"). Claude should:
vibe-island. Confirm with the user only if ambiguous./Applications/<App Name>.app. Check with ls /Applications/ | grep -i <app>.setup/Brewfile.* instead — this
skill isn't for brew." (stop here if yes)curl ... | bash, a GitHub release
binary, etc.)?"The install source determines the branch below.
The task can't automate the install — it just directs the user to go do it. Install task and reminder task do essentially the same thing.
Task template:
[tasks."install:<name>"]
description = "Install <App Name> (manual, from App Store/etc.)"
run = """
# ...
[ -d "/Applications/<App Name>.app" ] \\
&& echo "⏭️ <App Name> already installed" \\
|| { echo "👉 Install <App Name> from <source>, then run: mise run stow <name>"; exit 1; }
"""
Note: stowing doesn't happen automatically here since install is manual. The task exits 1 so it's visible in mise output, and the user runs stow by hand after installing.
The task downloads the file and opens the containing folder in Finder so the user can run the installer/drag the app themselves.
Task template:
[tasks."install:<name>"]
description = "Download <App Name> installer"
run = """
# ...
[ -d "/Applications/<App Name>.app" ] && { echo "⏭️ <App Name> already installed"; exit 0; }
curl -fL -o ~/Downloads/<filename> "<download-url>"
open ~/Downloads
echo "👉 Install <App Name>, then run: mise run stow <name>"
"""
Same as 2a — user runs mise run stow <name> after the manual install step.
The task runs the install command itself and self-stows on success. No user
intervention needed. This is the pattern for things like curl ... | bash
installers or GitHub-release binary drops.
Task template:
[tasks."install:<name>"]
description = "Install <App Name>"
run = """
# ...
<check-command> \\
&& echo "⏭️ <App Name> already installed" \\
|| { <install-command> && mise run stow <name>; }
"""
The check command depends on what gets installed — e.g. which <name> >/dev/null
for a CLI tool, [ -d /Applications/<App Name>.app ] for an app, or a
path-specific check for custom install locations.
Reminder is the same across both branches:
[tasks."sync:<name>"]
description = "Remind to install <App Name> if missing"
run = """
# ...
[ -d "/Applications/<App Name>.app" ] \\
&& echo '⏭️ <App Name> already installed' \\
|| echo '👉 Run: mise run install:<name>'
"""
Insert both blocks among the other task definitions, before [tasks.sync].
No depends-list edits needed — sync and install use sync:** / install:**
wildcards.
Show the new blocks and confirm before committing. The user may want to tweak wording, the check command, or the download URL.
Use the commit skill. Area prefix is setup:. The commit must be pushed so
the other machine sees the reminder on its next pull.
mise run <name> on this machine. It's for the other machine.setup/mise.toml.Brewfile.*.mise run stow <name> after the manual install step completes).Port recent general tech-writing changes from the work skill (orm-claude-tech-writing) into this repo's copy of the tech-writing skill. Use when the user asks to sync, fold in, or apply recent tech-writing changes from work, update the tech-writing skill from the work one, or catch this repo's skill up to the work one.
Create git commits following the workflow and message conventions. Use whenever the user asks to commit, make a commit, save changes, or any variation of committing work. Always use this skill instead of the default commit behavior.
Guidance for writing technical prose for an engineering audience — PR descriptions, commit message bodies, design docs and RFCs, technical explanations, multi-sentence code comments, incident write-ups, and any explanation of how a system behaves. Use this skill whenever you draft or revise writing whose reader is another engineer, even if the user only says "write up X", "explain this", "draft a PR description", or "write a comment block". Also use it when asked to re-explain or clarify a confusing technical explanation — including phrasings like "I don't understand what this means", "explain this more clearly", "rewrite this so it makes sense", "explain it to me like a robot", "pretend you're a robot and explain again", or "robotify that". These robot-voice and re-explain requests should trigger the skill even when you're restating something you said earlier in the same conversation. This skill governs full-prose writing: for code comments and commit messages it applies to the prose body — a multi-sentence
Add a temporary, self-deleting mise task to root mise.toml that runs a one-time action on the *other* machine after it next pulls, then prints a reminder to delete the task. Use when a change on this machine leaves the other machine needing a one-off action that `mise run sync` / manage-symlinks won't do on its own — e.g. pruning a stale symlink left by a rename, or migrating a config file in place. The action runs once and then the task is deleted, so it's not for durable machine setup. For syncing an app install, use add-install-task instead.
Turn on (or adjust) spoken progress narration via the macOS `say` command, so the user can follow your work by ear while away from the keyboard. The user invokes this with `/say [level]` — they pass a level word as the argument (off, quiet, default, verbose) or nothing for the default level. Narration is off unless invoked. This is user-invoked only; do not trigger it on your own.
Conventions for git commands other than commit. Use whenever you are about to push, amend, or rebase. For commits, use the `commit` skill.