game-match-checkpoint
Freeze the financial data analysis request into a stable intake checkpoint before any workbook analysis or PDF extraction begins.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- game-match-checkpoint
- description
- Freeze the financial data analysis request into a stable intake checkpoint before any workbook analysis or PDF extraction begins.
03 SKILL.md 正文
Game Match Checkpoint
Purpose
Create the first canonical task record for financial-modeling-qa before any workbook analysis or PDF extraction begins. This freezes the live source files, the odd-versus-even game rule, and the number-only /root/answer.txt requirement so the next stage inherits one stable request definition instead of re-deriving scope.
Required Inputs
/root/data.xlsx/root/background.pdf- odd-numbered games belong to Player 1 and even-numbered games belong to Player 2
- pair games as
1 vs 2,3 vs 4, and so on /root/answer.txtmust contain only the number
Required Outputs
Write both artifacts under workflow/:
workflow/game_match_intake_checkpoint.jsonworkflow/game_match_continuation_gate.json
Output Contract
workflow/game_match_intake_checkpoint.json must be valid JSON with exactly these top-level keys:
{
"task_id": "financial-modeling-qa",
"input_files": ["/root/data.xlsx", "/root/background.pdf"],
"player_assignment_rule": "...",
"pairing_rule": "...",
"target_output": "/root/answer.txt",
"output_format": "...",
"checkpoint_status": "frozen_for_downstream_review"
}
Populate it so that:
player_assignment_rulestates that odd-numbered games belong to Player 1 and even-numbered games belong to Player 2pairing_rulestates that games are compared as1 vs 2,3 vs 4, and continue in orderoutput_formatstates that/root/answer.txtmust contain only the number
workflow/game_match_continuation_gate.json must be valid JSON with exactly these top-level keys:
{
"current_record": "workflow/game_match_intake_checkpoint.json",
"next_skill": "game-match-scope",
"continuation_reason": "...",
"scope_freeze_notes": "..."
}
Populate it so that:
continuation_reasonexplains that the frozen source set and answer contract must be reviewed before workbook extraction or answer calculationscope_freeze_notessays both source files remain mandatory, the odd/even pairing rule is fixed, and/root/answer.txtmust stay number-only
Procedure
- Do not inspect workbook contents or extract the PDF in this stage.
- Create
workflow/game_match_intake_checkpoint.jsonwith the frozen request definition. - Create
workflow/game_match_continuation_gate.jsonthat promotesworkflow/game_match_intake_checkpoint.jsonas the current record and pointsnext_skilltogame-match-scope. - Keep this stage limited to source identity, pairing logic, answer-file format, and downstream continuation gating.
Continuation Command
Run game-match-scope using workflow/game_match_intake_checkpoint.json and workflow/game_match_continuation_gate.json.
Stop Condition
Stop only after both workflow artifacts exist with the exact keys above, checkpoint_status is frozen_for_downstream_review, current_record points to workflow/game_match_intake_checkpoint.json, next_skill is game-match-scope, and no answer calculation has started.
Routing-Depth Continuation
After this stage's local outputs are complete, read the game-match-scope skill before continuing. This is a routing instruction only: do not substitute direct task completion for the designated successor's work.
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.