jev
Write and improve programs that call Jev, TypeSafe's System One model. Use when designing TypeSafe questions (Choice, Score, Noul), structuring state, composing answers in code, setting confidence thresholds, or diagnosing a Jev question that answers wrong or with low confidence.
dbreunig · Owner publication
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add https://github.com/dbreunig/building-with-jev-skill/tree/04fe3666c6b8b8abfec1271c0e581c823a181f6d/skills/jev --skill "jev"About this skill
name: jev description: Write and improve programs that call Jev, TypeSafe's System One model. Use when designing TypeSafe questions (Choice, Score, Noul), structuring state, composing answers in code, setting confidence thresholds, or diagnosing a Jev question that answers wrong or with low confidence.
Writing and improving Jev programs
Jev is a judgment model. It reads one state, answers every question in the request independently and in parallel, and returns a probability distribution over the answers you defined. It does not reason in steps and it does not generate text. Code owns the control flow, the arithmetic, and the policy. Jev owns the snap judgments.
A good Jev question is one a knowledgeable person answers in a second, given the right context. "Does this message convey urgency?" fits. "Analyze this message and decide what to do" does not fit. Break that task into small questions and compose the answers in code.
This guidance applies to jev-1.13. The docs mark several limits as likely to improve in later versions, so recheck the jaggedness page when the model changes.
Workflow
- List the decisions your code must make. Write each as a branch, a threshold, or a ranking.
- Write one question per judgment. Split any question that weighs two properties.
- Pick the primitive whose answer your code acts on directly.
- Build the smallest state that answers every question. Compute in code whatever code can compute.
- Put every question that shares the state into one request, including questions that matter for only some inputs.
- Combine the answers in code: branches, weights, and confidence gates.
- Test against labeled examples. Read
probabilitieson the misses, then revise one or two questions at a time.
Choose the primitive
| Primitive | Use it when | Returns | Code acts on it with |
|---|---|---|---|
| Choice | The answer is one of a known set with no order | choice, probabilities, confidence | a branch per option |
| Score | The answer is a position on a spectrum you can describe in steps | score, probabilities, confidence, legend | a threshold, a rank, or a weight |
| Noul | The answer is a clean yes or no and the probability is the signal | noul, from 0 to 1 | an if on a threshold |
- Add an
otherornone of the aboveoption to a Choice whose list may not cover every input. - A Noul of 0.5 means Jev is unsure. It does not mean "medium". Use a Score to measure a degree.
- A Noul needs a crisp condition. "Is this candidate strong in Python?" is vague. "Does the resume state that the candidate used Python at work?" is crisp.
- Use a Choice or several Nouls when the answer has no in-between.
Write the instructions
- State the exact condition. Jev answers the words you wrote. It reads scoping words, negations, and implied conditions at face value.
- Ask one property per question. Hidden second judgments lower accuracy and confidence.
- Name the part of the state the question judges, with a backticked path:
`ticket.messages[0].text`. - Write directly. Avoid double negatives, a property of a property, and any question that needs several hops.
- Keep numerals that stand for levels out of the instructions. "Rate from 0 to 2" gives Jev nothing to match.
- Write the full question in
instructions. The question ID never reaches the model. - Keep decision policy out of the question. "A shared address cannot override a name conflict" belongs in code.
- When you explain what you really meant after a wrong answer, that explanation is the missing half of the instruction. Add it.
Instructions accept a string, an object, or an array. Use an object when the question has labeled parts or needs supporting data. Pass a schema, taxonomy, or row as JSON. Do not serialize it into a string template.
"instructions": {
"question": "Does the `message` ask the recipient to disclose a sensitive credential?",
"inspect": "message",
"focus": "Look for a request to send the credential itself, not a request to change or reset it."
}
Useful keys from the docs: question, focus, inspect, note, compare (a list of state paths), and field (a name, type, unit, description record that several questions share).
Write the criteria
Treat criteria as an extension of the instruction. The two must ask for the same thing, in the same direction. A Noul whose true side describes "no" performs worse.
Choice. Map each option to a description. Make the descriptions contrastive when options sit close together:
"billing": {
"what": "Charges, invoices, refunds, or subscriptions",
"not_for": "Order tracking or account access",
"examples": ["I was charged twice", "Where is my refund?"]
}
Score. List the levels from low to high. Use two to ten levels, and only as many as you can describe distinctly.
- Describe situations. "Broken feature, but a workaround exists" works. "Moderately severe" does not.
- Make each level stand alone. Jev judges each level separately and sees neither its number nor its neighbors. "Worse than the previous level" means nothing to it.
- Keep each Score to one dimension. "Punctual and smart and experienced" measures three things.
- Give a rare extreme its own level when your code must treat it differently.
- A level may be an object:
{"summary": "One change, clearly stated", "signals": ["A single fix or feature", "..."]}.
Noul. Criteria are optional. Add true and false sides, each with what and examples, when the boundary is subtle. Put the neighboring case in the description of the side it belongs to.
Examples. Write short concrete instances, such as "I was charged twice". Do not write a description of an instance, such as "a message about a billing problem".
Build the state
- Send only the fields the questions need. Unrelated detail lowers accuracy, and a large state hides which input caused a wrong answer.
- Retrieve and filter in c