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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Rates how well something uses Jev, TypeSafe's System One model (typed questions over a JSON state, answered in parallel with calibrated probabilities). Every rating is evidence-backed, dated, tied to a commit, and logged, so the library of past ratings anchors future ones.
Follow read.md; scripts/step.py serves the rubric, the fix rows and past ratings one phase at a time. Jevaluate rates projects; it doesn't run or diagnose your own pipeline. If asked for that, say so and stop.
Run on a Sonnet-class model at medium effort, the same one every time: ratings stay comparable only if the rater doesn't change. In Codex, run on gpt-6-sol at medium effort. In another harness, pick one model and effort and keep them. Record both in the rating (rater, effort); a rating by a different model is a different rater's.
Verdicts run from 5 "Learn from it" down to the verdict-1 codes and "Can't rate yet", defined in rubric.md section 5. They come from the rules, never from averaging scores. Any verdict of 3 or below states its reasoning and the core fixes.
Ratings are logged outside this skill, in $JEVALUATE_LIBRARY if set, else ~/.claude/jevaluate-library/ if it exists (libraries made before Codex support), else ~/.jevaluate-library/; scripts/library.py creates it. Never overwrite a past rating: a re-rating is a new dated entry.
Only public sources: the docs at docs.typesafe.ai (page list: https://docs.typesafe.ai/llms.txt; append .md to any page for markdown) and the project's own public files. Credit a repo to its GitHub owner, never to its banner or branding. A project's claims about its own results are claims until the rating checks them.
Codex's default sandbox blocks the network and writes outside the workspace. Fetching a repo (gh, git) and library.py add need your approval, or run with network access and the library folder as a writable root.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。