Individual skill
jev-anything
Use when the user wants to add Jev (TypeSafe's System One decision model) to anything: a classifier, router, scorer, guardrail, extractor, or any "smart if-statement" in their code or workflow. Triggers include "add jev", "jev classifier", "route/score/classify/grade/guardrail with jev", "put a decision layer in", or "jev-anything". Works even when the user does not understand Jev yet: this skill makes you interrogate, educate, and plan with them first, then scaffold a working Jev layer through TypeSafe's direct API or OpenRouter.
SKILL.md
Source commit 448461f01a5abb8b7026e2b2c222611ed18d2415
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- Yes
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 41
- Repository last updated
- Sep 24, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skill Repository topic
- claude-code Repository topic
- codex Repository topic
- decision-making Repository topic
- jev Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
CHANGELOG.mddoc · 4,545 bytesEXAMPLE-PROMPTS.mddoc · 5,873 bytesLICENSEasset · 1,094 bytesPLAN-TEMPLATE.mddoc · 2,642 bytesPROVENANCE.mddoc · 1,634 bytesREADME.mddoc · 4,329 bytesSKILL.mdcore · 12,462 bytesSTART-HERE.mddoc · 4,878 bytesreferences/01-what-jev-is.mddoc · 3,193 bytesreferences/02-openrouter-decisions-api.mddoc · 7,002 bytesreferences/03-fit-limits-cost-time.mddoc · 7,286 bytesreferences/04-measure-and-optimize.mddoc · 5,780 bytesscaffolding/.env.exampleasset · 232 bytesscaffolding/evaluate.pyruns · 9,058 bytesscaffolding/examples/email_triage.pyruns · 1,451 bytesscaffolding/examples/guardrail.pyruns · 1,022 bytesscaffolding/examples/pr_risk_score.pyruns · 1,200 bytesscaffolding/jev_client.pyruns · 4,579 bytesscaffolding/jev_client.tsruns · 2,919 bytesscaffolding/make_rating_sheet.pyruns · 2,746 bytes
Read excerpt
# jev-anything
You are helping a user put a Jev decision layer into their software, even if they
do not understand Jev well. Your job is NOT to immediately write code. Your job is
to first understand Jev correctly, then work out with the user what they actually
need, then scaffold it through TypeSafe's direct API or OpenRouter.
## Step 0: Read the references before you say anything technical
Do not describe Jev, quote its cost, or write a call from memory. Read these first:
- `references/01-what-jev-is.md` - what Jev is and is not, the three decision
primitives, how it actually works.
- `references/02-openrouter-decisions-api.md` - current TypeSafe direct access,