pptx-reference-scope
Approve the exact dangling-title and Reference-slide working set for /root/Awesome-Agent-Papers.pptx, including selected title slides, deduplicated paper-title collection, and unchanged content boundaries.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- pptx-reference-scope
- description
- Approve the exact dangling-title and Reference-slide working set for /root/Awesome-Agent-Papers.pptx, including selected title slides, deduplicated paper-title collection, and unchanged content boundaries.
03 SKILL.md 正文
Approve Dangling Paper Titles and Reference-Slide Working Set
Purpose
Freeze the exact working set for the dangling paper title cleanup in /root/Awesome-Agent-Papers.pptx before any PPTX write happens. This stage identifies the selected title slides, builds the deduplicated paper-title collection for the later Reference slide, and preserves the unchanged non-title-content boundary for slides 1-6.
Do not create /root/Awesome-Agent-Papers_processed.pptx in this stage.
Inputs
workflow/pptx_reference/intake_checkpoint.jsonworkflow/pptx_reference/continuation_gate.json/root/Awesome-Agent-Papers.pptx
Outputs
workflow/pptx_reference/working_set_record.jsonworkflow/pptx_reference/scope_summary.json
Approve the Exact Working Set
- Read
workflow/pptx_reference/intake_checkpoint.jsonandworkflow/pptx_reference/continuation_gate.json. Use the checkpoint identifier fromworkflow/pptx_reference/intake_checkpoint.jsonasapproved_from_checkpoint_id. If either file is missing, the checkpoint identity is unclear, or the continuation gate no longer points to dangling-title cleanup plusReferenceslide append work, stop. - Inspect
/root/Awesome-Agent-Papers.pptxonly far enough to confirm the selected dangling paper title slides and collect the paper-title text. Use raw OOXML or markdown extraction if needed. Ignore notes, comments, theme text, and duplicate occurrences outside the selected title set. - Confirm that the selected title slides are slides
2,3,4,5, and6. Each selected slide should contribute one dangling paper title paragraph that will later be restyled to Arial16, color#989596, bold disabled, widened to one line, and placed at the bottom center. If the deck does not support that exact five-slide working set, stop instead of inventing a replacement scope. - Build
reference_title_collectionfrom the selected slide titles in first-seen order and remove duplicate paper titles before recording the collection. - Create
workflow/pptx_reference/if it does not already exist, then freeze the selected versus non-selected boundary exactly once and write the artifacts. Selected candidates:title_slide_numbers:[2, 3, 4, 5, 6]title_edit_targets:["one dangling paper title paragraph per selected slide", "bottom-center title text box width expansion", "Reference slide append slot at deck end"]reference_title_collection: the deduplicated paper titles from the selected slidessupporting_ooxml_targets:["ppt/slides/slide2.xml through ppt/slides/slide6.xml", "presentation slide list for terminal append"]Non-selected candidates:["existing non-title text and media on slides 1-6", "theme assets not required for title restyling", "duplicate paper-title occurrences after deduplication"] - Set
pending_continuation_statustoapproved-working-set-pending-binder. - Write
workflow/pptx_reference/scope_summary.jsonso the next stage can continue without broad rescanning.
Output Contract
workflow/pptx_reference/working_set_record.json must contain:
{
"working_set_id": "<new working set id>",
"approved_from_checkpoint_id": "<checkpoint id from intake_checkpoint.json>",
"selected_candidates": {
"title_slide_numbers": [2, 3, 4, 5, 6],
"title_edit_targets": [
"one dangling paper title paragraph per selected slide",
"bottom-center title text box width expansion",
"Reference slide append slot at deck end"
],
"reference_title_collection": [
"<deduplicated paper title 1>",
"<deduplicated paper title 2>"
],
"supporting_ooxml_targets": [
"ppt/slides/slide2.xml through ppt/slides/slide6.xml",
"presentation slide list for terminal append"
]
},
"non_selected_candidates": [
"existing non-title text and media on slides 1-6",
"theme assets not required for title restyling",
"duplicate paper-title occurrences after deduplication"
],
"pending_continuation_status": "approved-working-set-pending-binder"
}
workflow/pptx_reference/scope_summary.json must contain:
{
"selected_slide_numbers": [2, 3, 4, 5, 6],
"duplicate_title_policy": "remove duplicate paper titles before Reference slide body is written",
"non_title_content_guard": "keep slides 1-6 non-title content unchanged",
"minimal_verification_focus": [
"one title per selected slide",
"single-line fit",
"bottom-center placement",
"deduplicated auto-numbered Reference slide body"
]
}
Continuation Command
Use workflow/pptx_reference/working_set_record.json and workflow/pptx_reference/scope_summary.json as the only scope inputs for the next binder stage. Continue from selected_candidates, non_selected_candidates, pending_continuation_status, selected_slide_numbers, duplicate_title_policy, and minimal_verification_focus without rescanning unrelated slides or theme assets.
Stop Condition
Stop and hand off when both JSON artifacts exist, the selected set is limited to slides 2-6, the paper-title collection is deduplicated, the non-title-content guard is recorded, and no processed PPTX has been written yet.
Routing-Depth Continuation
After this stage's local outputs are complete, read the pptx-reference-binder 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.