Score (0.0 — 1.0)
Calibrated probability for criteria where gradations matter: pattern severity, documentation quality, API elegance, rewrite confidence.
TypeSafe Jev is a judgment engine that provides calibrated probability assessments for subjective criteria. Instead of relying solely on deterministic heuristics, Jev enables skills to make nuanced judgments about quality, severity, and classification.
Score (0.0 — 1.0)
Calibrated probability for criteria where gradations matter: pattern severity, documentation quality, API elegance, rewrite confidence.
Noul (Classification)
Categorical classification for binary or few-class decisions: pass/fail, present/missing, structural/cosmetic, suspected/not_suspected.
| Without Jev | With Jev |
|---|---|
| Binary heuristics (regex, pattern matching) | Calibrated probability assessments |
| “Pattern present” or “pattern absent” | “Pattern present with severity 0.73” |
| Fixed classification | Classification with confidence level |
| Frequent false positives on edge cases | Nuanced judgments on edge cases |
Four skills in the catalog support optional TypeSafe Jev integration:
Humanizar
8 Score + 12 Noul — AI pattern severity, voice adequacy, rewrite confidence, change classification (structural/cosmetic/hybrid). Brazilian Portuguese.
Human-AI
8 Score + 12 Noul — Same structure as Humanizar, calibrated for English writing patterns and 7 different voice presets.
Slop Eval
8 Score + 16 Noul — Design tell severity, per-axis quality (color, typography, layout, motion), section classification (CLEAN/SUSPICIOUS/INFLATED/CRITICAL).
Agent Plugin Eval
7 Score + 19 Noul — UX coherence, documentation clarity, API elegance, gate classification, secret detection, quality checklist.
Each skill checks Jev availability before using it:
from typesafe import jev_available
if jev_available(): from typesafe import Score, Noul # Use Jev for subjective criteriaelse: # Fall back to heuristic scoringEach skill includes a jev_questions.json file with definitions:
{ "version": "1.0", "skill": "human-ai", "questions": { "score": [ { "id": "pattern_severity", "question": "How severe is this AI writing pattern in the context?", "context_required": ["text_segment", "pattern_type", "surrounding_text"] } ], "noul": [ { "id": "change_type", "question": "What type of change is required to fix this pattern?", "labels": ["structural", "cosmetic", "hybrid"] } ] }}When Jev is unavailable, skills use internal heuristic methods:
| Skill | Fallback without Jev |
|---|---|
| Humanizar / Human-AI | Scoring based on pattern count and weight |
| Slop Eval | Classification by tell density |
| Agent Plugin Eval | Deterministic validation + regex for secrets |
The fallback is functional but less nuanced on edge cases.
Each skill with Jev support includes:
| File | Description |
|---|---|
scripts/jev_questions.json |
Score and Noul question definitions |
references/jev-integration.md |
Integration protocol and code examples |
Section in SKILL.md |
Documentation on when and how to use Jev |
No. Jev is optional. All skills work without it using heuristic fallback methods.
See the official TypeSafe documentation for installation and configuration instructions.
Yes! Use the discovery pattern (jev_available()) and create a jev_questions.json following the documented structure. See the existing skills’ jev-integration.md files as reference.
Jev is useful for subjective criteria where gradations matter. Skills with purely deterministic evaluations (JSON validation, file existence, schema conformance) don’t benefit from Jev.