reply-packet-binder
Materialize strict reply packets from the approved service view and freeze send-ready rows without re-solving from raw inputs.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- reply-packet-binder
- description
- Materialize strict reply packets from the approved service view and freeze send-ready rows without re-solving from raw inputs.
03 SKILL.md 正文
Reply Packet Binder
This stage converts the approved service view into send-ready packet rows. It must reload continuity artifacts and dereference source-owned slots directly.
Prerequisite artifact
workflow/scheduling_email/continuity_note.jsonworkflow/scheduling_email/state.jsonshowingnext_required_skill = reply-packet-binder
Inputs to read
workflow/scheduling_email/continuity_note.json
Required outputs
workflow/scheduling_email/resolved_reply_packet.jsonworkflow/scheduling_email/state.json
Binding rules
- For each
approved_rowsitem, keep recipient identity from that row:to = from_email
- Resolve scheduling fields by dereferencing
source_owned_slotsusingapproved_service_view_source_request_index:date_formattedtime_rangeduration_hours_text
- Do not reopen
/root/test_input.jsonor rerun calendar solving once the continuity note is present.
Strict body template
Use this exact body scaffold (no leading indentation, preserve blank lines):
Hi,
Thank you for your meeting request.
I can be available:
Date: {date_formatted}
Time: {time_range}
Duration: {duration_hours_text} hour(s)
If this time doesn't work, please let me know your preferred alternatives.
Best regards,
SkillsBench
Packet schema
Write resolved_reply_packet.json with:
packet_rows: array ofrequest_indexsource_request_indextosubject(meeting reply subject)body
packet_created_at
State update
Set in state.json:
current_stage:reply-packet-bindernext_required_skill:dispatch-finalizerallowed_outputs: [workflow/scheduling_email/resolved_reply_packet.json,workflow/scheduling_email/state.json]status:completed
Scope ceiling (do not decide here)
- Do not send messages in this stage.
- Do not write
/root/results.json.
Stop condition
Stop after packet row count matches approved row count and each row has to, subject, and body.
Count-Study Continuation
After this stage's local outputs are complete, read dispatch-finalizer 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.