القائمة
Hand the current work to another agmsg agent — write a handoff doc, send its path as one line.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when adding, closing, or pruning entries in a repository's `TODO.md`, when moving finished work into `CHANGELOG.md`, or when setting up local task tracking for a repository that has no tracker. Do not use for entrypoint-docs drift review (`docs-entrypoint-review`), for cutting a release version section or tag (the repository's release workflow), for manager-facing work reports (`work-log-maintenance`), or for commit splitting (`atomic-commit`).
JEY workspace 固有の Linear 運用ルール: issue のプロジェクト自動ルーティング、ラベル/タイトル/取引ログの書式、Asana からの移行マッピング、ガードレール。CRUD 自体は Linear MCP tools を使い、MCP が使えない環境や MCP に無い操作のみ GraphQL スクリプトへフォールバックする。Use when creating or editing Linear tasks, choosing a project or label, migrating task notes from Asana, or appending transaction logs (date/payment/price) to an existing issue.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Select and run expert review lanes for UI, forms, design specifications, accessibility, and multi-device product quality when ordinary /review or code review is too shallow.
高級モデル(Claude Fable/Opus、Codex sol)のセッションで実装作業を受けたとき、 自分で書かずに安価な Worker モデルへ委譲する Orchestrator-Worker 運用。 Use when the user asks to implement, fix, refactor, add tests, or migrate code; when a task spans multiple files or independent subtasks that could run in parallel; or when another skill needs the delegation-vs-inline decision or the model tier mapping.
Guidance for mise (mise-en-place) as task runner, tool version manager, and package manager. Use when working with mise.toml, task definitions and dependency graphs (`mise run`, depends/run), `[task_config].includes` and global-vs-repository task placement (`~/.config/mise/tasks` vs local includes), DB/env/dotenvx/secrets/tools task-family splitting, tool/package centralization (npm:/pipx:), `mise upgrade` and `minimum_release_age`, Windows settings (`run_windows`, `config.windows.toml`), `mise skills add`, `mise bootstrap` and its config sections (`[bootstrap.packages]`, `[dotfiles]`, launchd/systemd units), `mise dotfiles apply`, or migrating a Brewfile to mise bootstrap. For `~/.apm` rollout work (apm.yml, lockfile, which APM task to run), coordinate with `apm-usage`. For Home Manager / Nix Flake dotfiles, use `nix-dotfiles`.
| name | baton |
| description | Hand the current work to another agmsg agent — write a handoff doc, send its path as one line. |
| argument-hint | <recipient agent> [what the next session should focus on] |
| disable-model-invocation | true |
Pass the baton: the receiving agent gets a written handoff document plus a one-line pointer to it.
agmsg carries plain text only — never raw context or diffs (~/.agents/skills/agmsg/README.md, "What's carried on a handoff"). The doc is the payload; the message is the pointer.
Run ~/.agents/skills/agmsg/scripts/whoami.sh "$(pwd)" claude-code. Each repository is registered in exactly one team, so teams= normally holds a single name — take it and do not ask. Ask which to use only when it returns more than one, which means the repository is double-registered and the roster needs fixing.
Run ~/.agents/skills/agmsg/scripts/team.sh <team> and confirm the recipient appears in the roster. Agent names carry their runtime (-cc, -codex) because send.sh addresses by name alone, so picking the wrong suffix reaches the wrong runtime. A recipient absent from the roster means either a typo or an agent that has not run join.sh — resolve which with the user before sending.
Done when TEAM, FROM, and TO are all known-good roster names.
Read ~/.claude/skills/handoff/SKILL.md (Codex: ~/.agents/skills/handoff/SKILL.md) and follow it, with two overrides:
<repo root>/tmp/baton/<topic>.md, not the OS temp directory. Upstream assumes a same-user pickup; a baton crosses agents, so the doc lives where the peer can reach it.Both files are APM-deployed targets of mattpocock/skills — read them, never edit them.
Done when the file exists and its "suggested skills" section names skills the recipient can actually invoke.
~/.agents/skills/agmsg/scripts/send.sh <team> <from> <to> "<one-line summary> — <absolute path>"
The path must be absolute: the recipient's working directory is its own.
Done when send.sh exits zero.
Give the user the document path and the send result.