Use when images (photos, illustrations, screenshots) need to become input for TypeSafe's Jev (System One) model, which reads only text -- "turn this photo into a Jev state", "describe these images for Jev", "decode images for System One", or a Jev project whose decision depends on what a picture shows. Handles 1 to about 100 images; produces a neutral, complete decode and a JSON state, checked against Jev.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Jev can't see images. Jev Lens describes them for it, neutrally and completely.
Turns images into a JSON state for Jev. In priority order:
The decode is done blind: fresh subagents that see only the cleaned images and a neutral brief, never the goal, the user's questions or their hypothesis. What a person hopes the image shows is the main source of bias, so it never reaches the decoder.
| Images | Do | Open |
|---|---|---|
| 1 to 5 | Phase 1 on all of them; that is the whole job | calibrate.md |
| 6 to about 100 | Phase 1 on 1 to 3, then Phase 2 on the rest | calibrate.md, then batch.md |
| Over about 100 | Probably the wrong skill: say it isn't optimized for bulk extraction, and offer to calibrate on a sample so the package is ready for a bulk tool |
Both phases use decode-protocol.md (how decoders are briefed and what they write) and state-rules.md (how the state is built). General rules for building with Jev, with their sources: ../shared/jev-rules.md (shared with Jevaluate).
Each subagent carries a fixed overhead (about 55k tokens in Claude Code) before it reads anything. The figures below are Claude Code measurements; other harnesses differ. Guide for 10 images:
| Light | Heavy | |
|---|---|---|
| Calibration decodes (2 images) | ~60k | ~120k |
| Extra calibration round | none | ~120k |
| Main session (reviews, state, sketch, check) | ~20k | ~35k |
| Batch decode (8 images, 1 subagent) | ~75k | ~75k |
| Agreement sample (3 images) | none | ~65k |
| Cascade on flagged fields | none | ~30k |
| Total | ~155k | ~445k |
Scale the batch lines by images / 10 per decoder. The Jev API cost is under a cent either way; jev_check.py prints it before sending anything.
Decoder model: the strongest vision model for calibration and the cascade, a cheaper one for the batch. At intake, ask whether to use the strongest for everything, and show the difference: the batch line costs about the same in tokens but at the stronger model's price.
A run folder next to the images, <name>-jev-lens/:
| Path | What |
|---|---|
images/, manifest.json | Cleaned copies (metadata stripped, renamed); the manifest maps them back and is never shown to a decoder |
package/ | brief.md, template.json, decoder-prompt.md, examples/: the calibrated package |
decodes/ | Each blind decode (a/, b/, batch/, sample/) |
agreement.md | Field-by-field agreement between decoders |
inventory/ | The reviewed decode for each calibration image |
keep.json, left-out.md | Which fields went into the state, and why the rest didn't |
state.json or states/ | The state, one per image |
questions.json, question-sketch.md | The question sketch (a sketch, not final questions) |
jev-check.md | The Jev check and the field-by-field ranking |
report.md | One page: what was seen, what was uncertain, what was left out and why, the agreement rates, and what drives the answer |
prepare_images.py and jev_check.py declare their packages inline (Pillow; typesafe-sdk), so uv run installs them; without uv, pip install pillow typesafe-sdk and use python. The other scripts use only the standard library.TYPESAFE_API_KEY for the Jev check. Without it, the skill skips the check, says so, and still delivers the decode and state.jev-1.13.0 by default; take the current one from https://docs.typesafe.ai/models.uv run installing packages, the Jev check, and a run folder outside the workspace need your approval.Rating whether a finished Jev project uses Jev well is a different job: the Jevaluate skill. Jev Lens does not need it.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when a question, review, design or claim involves Jev, TypeSafe, System One, Nouls, or Choice/Score questions, including whether something should be built with Jev, reviewing a Jev design, briefing a subagent on Jev work, or relaying a subagent's Jev finding.
日本語の概要は準備中です。原文の説明を表示しています。
Use when rating whether a project, repo, skill, workflow, plugin, agent product or post uses TypeSafe's Jev (System One) model well -- "is this a good use of Jev?", "rate this Jev integration", "jevaluate <url>", or a link to something named after Jev; also when checking whether something that calls itself Jev actually uses it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing whether the jevaluate rubric and instructions lead graders to the right answers: after a rubric or instruction change, before freezing a rubric, before publishing ratings, or when a grader's calls look wrong.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running a jevaluate rating round, re-rating after a rubric change, changing the jevaluate rubric, or publishing ratings to the jev-mode ratings folder.
日本語の概要は準備中です。原文の説明を表示しています。
Use when rating a project with Jevaluate that must stay private -- "/jevaluate-private <link or folder>", "rate this privately", "evaluate my own project", a client's or employer's code, a design doc or a local folder that isn't public, or any rating that must not reach the public ratings or the repo.
日本語の概要は準備中です。原文の説明を表示しています。