subject-folder-scope
Approve the selected working set for subject sorting by separating selected files, non-selected candidates, and mandatory context needed for the five destination folders.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- subject-folder-scope
- description
- Approve the selected working set for subject sorting by separating selected files, non-selected candidates, and mandatory context needed for the five destination folders.
03 SKILL.md 正文
Approve the Subject Sorting Working Set
Use this stage before any document moves. Its job is to freeze which files are in scope for sorting into LLM, trapped_ion_and_qc, black_hole, DNA, and music_history, reduce duplicate scanning, and preserve later review and traceability.
Inputs
Read:
workflow/subject_intake_checkpoint.jsonworkflow/subject_continuation_gate.json
Take task_root from the intake checkpoint and keep the same path style already used there.
Write workflow/subject_working_set_record.json
Build one approved working record with these exact keys:
{
"task_root": "string",
"selected_candidates": [
{
"path": "string",
"extension": "string",
"pending_subject_folder": ""
}
],
"non_selected_candidates": [
{
"path": "string",
"exclusion_reason": "string"
}
],
"mandatory_context_paths": [
"string"
],
"required_subject_folders": [
"LLM",
"trapped_ion_and_qc",
"black_hole",
"DNA",
"music_history"
],
"working_set_status": "approved_pending_continuation"
}
Selection rules:
- Put every in-scope
.pdf,.docx, and.pptxfile that still needs subject sorting intoselected_candidates. - Keep each selected file exactly once.
- Leave
pending_subject_folderempty at this stage unless the intake checkpoint already carries a decisive folder assignment that should be preserved without reclassification. - If a document's subject is not yet obvious, keep it selected and pending here instead of excluding it.
- Put only truly out-of-scope files into
non_selected_candidates, with a shortexclusion_reason. - Do not exclude continuation records, task-local operational notes, or other local context that later classification or completion stages still need. Keep those in
mandatory_context_paths. mandatory_context_pathsshould include the two input workflow records and any real local references needed later to classify or verify the five subject folders, such as task-local test or instruction files when present.- Do not move or rename files in this stage.
Common exclusions:
- subject folders already created for output structure
- workflow sidecars that are not part of the document set
- unsupported extensions
- helper scripts and benchmark tests
Write workflow/subject_scope_summary.json
Write this exact shape:
{
"selected_count": 0,
"non_selected_count": 0,
"counts_by_extension": {
".pdf": 0,
".docx": 0,
".pptx": 0
},
"scope_reason": "standardize approved sorting set and preserve later review/traceability",
"next_required_stage": "subject-folder-binder"
}
Count only selected_candidates in counts_by_extension. Always include all three extension keys, even when a count is zero.
Continue With Subject Folder Binder
Use the approved scope artifacts as the only authoritative inputs:
subject-folder-binder workflow/subject_working_set_record.json workflow/subject_scope_summary.json
Stop Condition
Stop when both workflow files exist, selected_candidates and non_selected_candidates are explicitly separated, working_set_status is approved_pending_continuation, the five required folder names are present exactly as listed above, the summary counts match the approved working record, and no selected file has been moved or renamed.
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.