
Jev Search
Use after any web or API search, before opening results or spending another round.
Install
npx skills add kerpopule/hermes-jev-skills --skill jev-search -g -a claude-code -y- Repository
- kerpopule/hermes-jev-skills1.3k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,570 tokens
- Runs scripts
- No, instructions only
What it does
Use after any web or API search, before opening results or spending another round. Jev picks which results to read, whether the evidence is enough, and which query to run next from ones you wrote.
Searching with Jev
A research turn is usually three decisions and one piece of writing:
- which of the results to actually open (the other thirty are noise),
- whether what has been read answers the question, or another round is needed,
- which query to run next.
Those are picks and a yes/no. Jev answers them in about half a second for a fraction of a cent, and the expensive model is left to do the writing, which is the only part of this Jev cannot do. Jev never writes a query. You write the candidates; Jev picks one or says none of them would add anything.
jev search runs one round of that loop and hands back the decision. Use it instead of guessing, and instead of burning a frontier turn on "should I search again?".
Do this
-
Search the way you always do (
web_search, an API, a site). Give it the question, and write two to five candidate queries for the next round if this one is not enough. -
Run one round:
echo '{"question":"what does the decision API cost", "queries_tried":["decision model pricing"], "candidate_queries":["typesafe pricing page","decision api rate limits","free tier"], "round_index":1, "results":[{"id":"a","title":"...","url":"https://...","snippet":"..."}]}' | jev searchOr call the
jev_searchtool with the same fields. -
Read
decisionand do exactly that:
