pedestrian-traffic-counting-wob-k3-prep-producer
Combine frozen WOB workflow roles while preserving the producer-to-packet boundary.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- pedestrian-traffic-counting-wob-k3-prep-producer
- description
- Combine frozen WOB workflow roles while preserving the producer-to-packet boundary.
02 资源文件 2
03 SKILL.md 正文
Combined WOB Workflow Stage
Execute component roles below in order. A component instruction that routes to another component in this same skill is an internal checkpoint: continue directly to the next component and do not read a separate skill. Do not reinterpret a sealed non-self binding or replace the packet consumer's responsibility.
Combined role: pedestrian-traffic-counting-intake-checkpoint
Stage 1 — Pedestrian checkpoint
Run exactly:
python3 /root/.codex/skills/pedestrian-traffic-counting-wob-k3-prep-producer/scripts/build_checkpoint.py
This helper is the only authority for artifacts/pedestrian-traffic-counting/workbook-checkpoint.json. Do not count videos or create count.xlsx here. Do not hand-write a checkpoint. On success, stop and proceed to pedestrian-traffic-counting-resolved-workbook-state.
Combined role: pedestrian-traffic-counting-resolved-workbook-state
Stage 2 — Pedestrian resolved state
Require the checkpoint from stage 1. Run exactly:
python3 /root/.codex/skills/pedestrian-traffic-counting-wob-k3-prep-producer/scripts/build_resolved_workbook_state.py
The helper performs the task-native video analysis and writes artifacts/pedestrian-traffic-counting/resolved-workbook-state.json. Do not invent counts, write the workbook, build a packet, or modify its state manually. On success, stop and proceed to pedestrian-traffic-counting-count-packet.
Count-Study Continuation
After this stage's local outputs are complete, read pedestrian-traffic-counting-count-packet 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.