Two public editor asks map onto a local shortlist CLI. That is a mapping, not a claim we ran their bins.
You have a pile of separately-cut scenes and you lose the original order when they hit a Premiere master. One r/VideoEditing thread is about pasting a lot of scenes into a master. binquery does not paste into Premiere, restore NLE markers, or read original sequence from the files. It takes one visual-intent sentence per scene and returns 8–15 clips (path, score, gate, reasons). You keep the query order as your sequence memory. People still watch.
Trailer work often starts from rushes / dailies, not a locked master. One r/editors thread asks whether trailer editors work from raw rushes. Index your own folder, then one trailer-intent sentence → the same shortlist. It is not an auto-cut trailer.
These are unmatched pictorial queries. Unknown sentences still run. You do not have to edit src/intents.py. We have not run this against a real ~500-clip bin. CI only builds 3 lavfi clips and runs index → doctor. A real demo needs your own folder.
export BINQUERY_INDEX=./my-box
./binquery index --input ./my-videos --index "$BINQUERY_INDEX"
./binquery doctor --index "$BINQUERY_INDEX"
# scene-sequence: one sentence per scene, keep this order yourself
./binquery query --index "$BINQUERY_INDEX" "scene 2 empty hallway lock-off"
# rushes / trailer intent: one sentence against your own rushes box
./binquery query --index "$BINQUERY_INDEX" "cold open wide empty night"
Skill install is instructions only. It does not install the Python package:
npx -y skills add jennifferweslowski-design/binquery
