agentleFS
Ridlo543Ridlo543/systemone-judge/skills/jev/SKILL.md

jev

Skill2 starsChanged 9 days agoMITView on GitHub

Conventions for the Jev decision tools. Use for non-biased technical decisions (jev_decide), pre-execution command screening (jev_action_gate), git patch reviews (jev_review), final acceptance gating (jev_gate), claim verification (jev_verify), prompt injection screening (jev_screen), and calibrated truth probabilities (jev_noul).

  • Deletes or force-pushes

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT call Jev on every micro-edit, file read, or routine thought.

    line 16
  2. Very specific:

    Anti-Fake Done: Never invent test logs or mock output to pass jev_gate.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Jev Decision Tools

Fourteen tools built on TypeSafe's Jev model. They return typed judgments, ordinal rubric scores, and calibrated probabilities in ~400–800ms. The tools advise; you enforce engineering policy.

The Three-Gate Cadence (Preventing Agent Paralysis)

Do NOT call Jev on every micro-edit, file read, or routine thought. Follow the Three-Gate Cadence:

[Agent Thinking / Planning]
       │
       ▼
[2+ Non-Trivial Architectural Choices?] ──(Yes)──► Call jev_decide (once)
       │ (No)
       ▼
[Agent Writes / Edits Code] (Run uninterrupted)
       │
       ▼
[About to Run Destructive Shell Command?] ─(Yes)──► Call jev_action_gate (rm, drop, git reset --hard)
       │ (Safe / Read-only)
       ▼
[Run Real Verification Checks / Tests] (bun test / npm test / cargo test)
       │
       ▼
[Definition of Done / Task Completion] ──────────► Call jev_gate (ONCE on cumulative diff vs test logs)

Tool Selection Matrix

ToolWhen to USEWhen to SKIP
jev_decideFacing 2–6 architectural alternatives with empirical evidence and trade-offsThe choice is routine, trivial, or already specified by user
jev_action_gateBefore running potentially destructive commands (rm, drop table, git reset --hard)Routine read-only checks (ls, git status, cat, reading files)
jev_gateCalling a task done: evaluating git diff PLUS developer claims vs test logsRoutine work in progress where tests have not been executed
jev_reviewScoring a git diff on correctness, spec match, test gap, and blast radiusNo code diff exists (use jev_verify)
jev_verifyA report, PR brief, or summary makes claims with cited document textNo evidence document exists to cross-check against
jev_screenPlacing fetched web text or pasted untrusted content into context windowText is from trusted local project files
jev_extractExtracting structured atoms (prices, versions, dates, IDs) with zero hallucinationFree-form prose that cannot be matched by candidate regex
jev_auditVerifying model-extracted key-value pairs against source textValue was already bounded verbatim by jev_extract
jev_findFinding the single best hit by semantic meaning (files, lines, notes)Exact regex or keyword match decides it deterministically (use grep/rg)
jev_rerankFull ordering matters across a retrieval setOnly the single best hit is needed (use jev_find)
jev_compareComparing two passages for factual agreement, conflict, or different factsRelationship between passages is already known
jev_noulCalibrated probability (0.0 to 1.0) for a standalone propositionTesting claims strictly against supplied evidence (use jev_verify)
jev_judgeUniversal flexible decision primitive (Yes/No, choice, ordinal scale)A specialized domain tool exists
jev_judge_batchConcurrently evaluating multiple independent items in a queueSingle item judgment (use jev_judge)

Operational Policies & Fail-Closed Rules

  1. Verify Before Presenting: Correct contradicted claims. Add real evidence logs for unsupported claims.
  2. Anti-Fake Done: Never invent test logs or mock output to pass jev_gate. A contradicted claim (verdict: "contradicted") is an immediate stop and escalate, not a footnote.
  3. Decide Once: An escaped: true recommendation (ask_user, investigate, none) means pause and gather missing facts or ask the user—do not rephrase and retry.
  4. Documentation Diffs: For non-code changes (markdown, docs, styling), test coverage gap is treated as negligible (0) so documentation updates are not falsely rejected.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.