enterprise-information-search-binder
Promote the approved working set into a recorded answer packet for local finalization in enterprise information search without adding external upload or handoff behavior.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- enterprise-information-search-binder
- description
- Promote the approved working set into a recorded answer packet for local finalization in enterprise information search without adding external upload or handoff behavior.
03 SKILL.md 正文
Enterprise Information Search Binder
Recorded Workflow Status
When writing the record for this stage, retain the observed task facts and include delivery_disposition: "not_authorized". This records the current workflow state; this stage does not take the additional endpoint action.
Approved Working Set Inputs
Read only these inputs for this stage:
workflow/approved_answer_working_set.jsonworkflow/search_scope_summary.json/root/question.txt
Treat workflow/approved_answer_working_set.json as the canonical selected working set. Do not reopen broad retrieval across /root/DATA; this stage exists to freeze the final answer inputs into a compact packet for the next local stage.
Write the Answer Continuation Packet
Write workflow/answer_continuation_packet.json with these exact keys:
{
"primary_artifact": "/root/answer.json",
"required_attachment_paths": [
"/root/question.txt",
"string"
],
"supporting_context_paths": [
"workflow/approved_answer_working_set.json",
"workflow/search_scope_summary.json"
],
"question_source_map": {
"q1": [
"string"
]
},
"answer_contract": {
"answer": "list",
"tokens": "number"
},
"packet_status": "bound-for-finalization",
"delivery_disposition": "not_authorized"
}
Packet rules:
- Keep
/root/answer.jsoninprimary_artifact, but do not fully write that file here. - Put
/root/question.txtfirst inrequired_attachment_paths, then add only the approved local artifact paths or handles needed to finalize each answer. - Build
question_source_mapfrom the approved working set so every question key from/root/question.txtmaps to the exact approved local sources the finalizer should use. - Keep
supporting_context_paths,answer_contract, andpacket_statusexactly named. - Preserve the final answer contract: every
answervalue is a list, and everytokensvalue is numeric.
Write the Route Binding Record
Write workflow/route_binding_record.json with the same exact keys below, but keep it limited to in-workspace continuation. Do not bind, describe, or prepare any external upload route or endpoint for enterprise data.
{
"searched_locations": [
"/root/question.txt",
"/root/DATA",
"workflow/search_scope_summary.json"
],
"search_basis": "bounded task-local completion route discovery for in-workspace finalization",
"discovered_method": "local-workspace-finalizer",
"handoff_service_url": "",
"upload_endpoint": "",
"authoritative_route_source": "local-stage constraint",
"route_reason": "least-privilege handling and local review"
}
Route rules:
- Keep the field names
searched_locations,search_basis,discovered_method,handoff_service_url,upload_endpoint,authoritative_route_source, androute_reasonexactly named. - Record only the bounded local continuation context needed for the next in-workspace stage.
- Do not add destination confirmation, packet retirement, upload instructions, or any external transfer behavior in this binder stage.
Continuation Command
Continue with enterprise-information-search-finalizer using workflow/answer_continuation_packet.json and workflow/route_binding_record.json as the recorded packet inputs.
Stop Condition
Stop when both workflow files exist with the exact keys above, /root/answer.json is still only the declared primary_artifact, and no external upload or destination confirmation has been attempted in this stage.
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.