Menu
Hand over a line so the next shift starts informed rather than discovering.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vstorm-co/agenticos --skill shift-handoverThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | Shift handover |
| description | Hand over a line so the next shift starts informed rather than discovering. |
| category | operations |
The incoming shift needs what will affect them, not a diary of what happened.
Safety — anything unsafe, isolated, or with a permit open. Running state — what is running, what is down, what is degraded and how. In progress — jobs part-complete, and where exactly they stopped. Watch items — the machine behaving oddly, the material batch running out of spec, the temperature drifting. This is the section that matters. Outstanding — work orders raised, parts on order, escalations open. Quality — holds, deviations, anything awaiting disposition.
"Line 3 infeed jamming roughly every 40 minutes since 14:00, cleared manually, maintenance notified at 15:20" is a handover. "Line 3 playing up" is not.
What the next shift must do first, and anything with a time on it.
Leave a verbal-only item, close a watch item because it stopped happening without saying when, or hand over an open permit without naming its holder.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.