scheduling-local-handoff-request-checkpoint
Use when starting a task that asks you to read meeting requests from /root/test_input.json, check them against /root/calendar_events.json, send formatted availability replies through the internal mail gateway, and save submission IDs in /root/results.json.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- scheduling-local-handoff-request-checkpoint
- description
- Use when starting a task that asks you to read meeting requests from /root/test_input.json, check them against /root/calendar_events.json, send formatted availability replies through the internal mail gateway, and save submission IDs in /root/results.json.
02 资源文件 1
- 脚本scripts/write_checkpoint.py9.2 KB
03 SKILL.md 正文
Scheduling Local Handoff Request Checkpoint
When a task asks you to schedule multiple meeting-request emails against /root/calendar_events.json, submit the replies through the internal mail gateway, and save the resulting submission IDs to /root/results.json, start here. Read /root/test_input.json and /root/calendar_events.json, freeze request order, local delivery seeds, parsed date/time constraints, and calendar scope, and write request_schedule_checkpoint.json before any compatible slot is chosen.
Inputs
- Request emails:
/root/test_input.json - Local calendar:
/root/calendar_events.json
Recommended Command
python3 /root/.agents/skills/scheduling-local-handoff-request-checkpoint/scripts/write_checkpoint.py \
--requests /root/test_input.json \
--calendar /root/calendar_events.json \
--output request_schedule_checkpoint.json
Output Contract
Write request_schedule_checkpoint.json with these top-level keys:
{
"current_stage": "request_schedule_checkpoint",
"next_required_skill": "scheduling-local-handoff-approved-slot-view",
"allowed_outputs": ["request_schedule_checkpoint.json"],
"request_reply_context": [],
"request_slot_review_set": [],
"calendar_scope": {}
}
request_reply_context keeps the frozen request order, request indexes, request handles, local delivery seeds, and reply subject.
request_slot_review_set keeps parsed candidate dates, time window bounds, duration_minutes, duration_hours, and duration_hours_rendered for each request, but not concrete compatible slot fragments.
calendar_scope keeps the normalized busy-window view needed for later slot checking from the checkpointed artifact.
The next stage should read exactly current_stage, next_required_skill, allowed_outputs, request_reply_context, request_slot_review_set, and calendar_scope.
Meeting Request Parsing Rules
- Parse date constraints, time window constraints, and meeting duration from each email into
request_slot_review_set. - Accept duration wording in the common forms used by the task inputs, including
one-hour,1.5 hour, and45-minute. - Keep the checkpoint compact: freeze request indexes, local delivery seeds, and calendar scope without copying full raw email text or send-ready reply rows.
- Preserve duration rendering for later reply formatting. For example, keep
1.0as1.0, not1. - Keep delivery seeds local at this stage. Do not introduce approved continuity bindings, gateway payload rows, or send-ready packet rows in the checkpoint.
What This Checkpoint Must Not Write
- No concrete compatible slot fragments
- No approved delivery fragments
- No reply body
- No gateway payload
- No mail gateway receipts
- No
sent_results
Stop Condition
Stop after request_schedule_checkpoint.json exists and the command output shows:
artifact=request_schedule_checkpoint.jsoncurrent_stage=request_schedule_checkpointnext_required_skill=scheduling-local-handoff-approved-slot-view
Count-Study Continuation
After this stage's local outputs are complete, read scheduling-local-handoff-approved-slot-view 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.