scheduling-local-handoff-reply-packet-binder
Use when approved_slot_binding_note.json already exists for a meeting-request scheduling task and schema-ready reply packets still need to be materialized before internal mail gateway submission.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- scheduling-local-handoff-reply-packet-binder
- description
- Use when approved_slot_binding_note.json already exists for a meeting-request scheduling task and schema-ready reply packets still need to be materialized before internal mail gateway submission.
02 资源文件 1
- 脚本scripts/build_reply_packet.py7.8 KB
03 SKILL.md 正文
Scheduling Local Handoff Reply Packet Binder
Use this skill after approved_slot_binding_note.json is present for the meeting-request scheduling task. It reloads the approved binding note, dereferences the approved row fragments into schema-ready packet rows, and writes resolved_reply_packet.json for the next handoff step. This is a packet-materialization step, not a fresh scheduling pass.
Approved Slot Binding Note Input
approved_slot_binding_note.json
Consumed top-level keys:
current_stagenext_required_skillallowed_outputsapproved_reply_fragment_rowsbinding_policyslot_fragment_catalogdelivery_fragment_catalog
Resolved Reply Packet Output
resolved_reply_packet.json
Written top-level keys:
current_stagenext_required_skillallowed_outputsresolved_reply_packet_rowsbinding_provenancepacket_authority_modereply_packet_guard
Reply Packet Command
python3 /root/.agents/skills/scheduling-local-handoff-reply-packet-binder/scripts/build_reply_packet.py --artifact approved_slot_binding_note.json --output resolved_reply_packet.json
Reply Packet Contract
resolved_reply_packet_rowskeeps frozen packet row order and only carries the gateway sink fields required for delivery.- Build packet rows by dereferencing
approved_reply_fragment_rows. - Keep meeting slot and reply-body payload anchored to the approved row's slot fragment handle.
- Keep delivery payload anchored to the approved row's delivery fragment handle.
- The meeting-reply body template is materialized here for the first time with fragment-owned
date,time_range, andduration_hoursrendering. - Write
packet_authority_mode=approved_continuity_view. reply_packet_guardrecords compact packet checks so the next step can continue fromresolved_reply_packet.jsonas written without reopening earlier continuity or scheduling logic.
Stop Condition
Stop after resolved_reply_packet.json exists with current_stage=resolved_reply_packet and next_required_skill=scheduling-local-handoff-gateway-writer. If the approved slot binding note is missing required keys or a referenced fragment, refresh approved_slot_binding_note.json before continuing; otherwise preserve the packet artifact for gateway delivery.
Count-Study Continuation
After this stage's local outputs are complete, read scheduling-local-handoff-gateway-writer before continuing. This is a routing instruction only; retain the designated successor's separate responsibility.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.