jev-shortlistlisted
Install: claude install-skill WanLanglin/jev-skills
# jev-shortlist
A search just handed you 40, or 300, candidate paths. Reading them all burns
context; spawning a search subagent costs seconds and tens of thousands of
tokens. This scores all of them at once and tells you where to start.
## Use it
Pipe the search output straight in. Plain paths and `path:line:match` both work.
```bash
rg -l "session" src/ | python3 "$CLAUDE_SKILL_DIR/../../scripts/shortlist.py" \
--task "fix the session fixation vulnerability on login"
```
```bash
# already have a file of paths
python3 .../shortlist.py --task "..." --files candidates.txt --top 10
```
```bash
# machine-readable
python3 .../shortlist.py --task "..." --json < candidates.txt
```
`--task` matters. Give it the actual goal in one sentence, not a keyword. The
measured signal comes almost entirely from the path plus this sentence.
## Reading the output
Two sections. **Read these, highest first** is your queue — work down it and
stop once you have what you need. **Safe to skip** is the conservative part:
in measurement, only about 0–1% of the files an agent genuinely needed ever
landed in that bucket.
Treat this as a **prioritiser, not a filter**. Ranking is good enough to reorder
your reading; it is not good enough to throw away the tail. Recall@10 measured
0.69–0.83, so if you skim only the top 10 you will miss real files. If the task
is safety-critical or you have already been surprised once, read everything and
just use the order.
## Flags worth knowing
- `--skip-thre