Jev Question Translator
lawve-ai/awesome-legal-skills
Turns a legal question, a set of draft questions, or source material such as a statute, jury instruction, rubric, contract checklist, or coding manual into a battery of narrow questions that…
Ask every independent TypeSafe Jev question in one POST /v1/systemone (speculative fan-out).
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cobusgreyling/Jev jev-fanout --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/jev-fanout .claude/skills/jev-fanout && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .claude/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanoutType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cobusgreyling/Jev jev-fanout --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/jev-fanout .agents/skills/jev-fanout && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .agents/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cobusgreyling/Jev jev-fanout --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/jev-fanout .cursor/skills/jev-fanout && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .cursor/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cobusgreyling/Jev.git --path skills/jev-fanout--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cobusgreyling/Jev jev-fanout --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/jev-fanout .gemini/skills/jev-fanout && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .gemini/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cobusgreyling/Jev jev-fanoutInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/jev-fanout .github/skills/jev-fanout && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .github/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/Jev --skill jev-fanout -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cobusgreyling/Jev jev-fanout --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/Jev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/jev-fanout .opencode/skills/jev-fanout && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jev-fanout" agent skill from https://github.com/cobusgreyling/Jev/tree/main/skills/jev-fanout into .opencode/skills/jev-fanout/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jev-fanout", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
jev-fanoutAsk every independent TypeSafe Jev question in one POST /v1/systemone (speculative fan-out).
Jev Fanout is an agent skill from cobusgreyling/Jev. Ask every independent TypeSafe Jev question in one POST /v1/systemone (speculative fan-out). Use for parallel questions, smart-home or compound commands, one-call turn assessment, or when the user runs /jev-fanout. Do not fire one HTTP call per question.
Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Unofficial TypeSafe Jev showcase — System One decisions, not chat. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 77b65c6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.typesafe.aiFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jev Fanout loads about 603 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 187 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from cobusgreyling/Jev at commit 77b65c6, republished under its MIT licence (© cobusgreyling). 187 words, ~603 tokens.
.claude/skills/jev-fanout/SKILL.md (or your agent's skills folder).Ask every independent judgment over the same state in one POST /v1/systemone. Questions run in parallel and cannot see each other's answers. Code consumes the ones that apply.
Primitives and auth: skills/jev/SKILL.md. Official pattern: https://docs.typesafe.ai/patterns/fan-out
questions with complete instructions. Write the speculative premise into the question (If this is a light command, …). Question IDs are not sent to the model.choice, score, and noul in that one request. Pin jev-1.13.0 once thresholds are tuned; jev-latest moves.{
"state": "I've been trying to connect Stripe for 3 days. I'm losing sales. Help ASAP.",
"model": "jev-latest",
"questions": {
"department": {
"type": "choice",
"instructions": "Which team should handle this message?",
"criteria": {
"billing": "Payments, invoicing, refunds",
"technical": "Bugs, outages, integrations",
"other": "Neither fits"
}
},
"frustration": {
"type": "score",
"instructions": "How frustrated does the author appear?",
"criteria": ["Calm, just stating facts", "Frustrated but civil", "Very angry, strong language"]
},
"is_urgent": {
"type": "noul",
"instructions": "Does the message convey urgency or time-sensitivity?"
}
}
}examples/04_parallel_fanout.py — Choice + Score + Noul in one calljev_lab/home.py and /home — ~13 speculative questions, then the dispatcher actspackages/js/src/turn.ts — npx jev turn (route + input guard, one call)docs/smart-home.md© cobusgreyling, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/jev-fanout of cobusgreyling/Jev.
Open the folder on GitHubat commit 77b65c6
Jev Fanout next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jev Fanout this skillcobusgreyling/Jev | 136 | — | ~603 | Automated safety check: Pass | MIT | |
| Jev Question Translatorlawve-ai/awesome-legal-skills | 847 | — | ~6.9k | Automated safety check: Pass | Apache-2.0 | |
| Moai Ref Jev Question Designmodu-ai/moai-adk | 1.2k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Jev Socialsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Jev Usesickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Omh Jev Askrlaope/oh-my-hermes | 3.2k | — | ~673 | Automated safety check: Pass | MIT |
lawve-ai/awesome-legal-skills
Turns a legal question, a set of draft questions, or source material such as a statute, jury instruction, rubric, contract checklist, or coding manual into a battery of narrow questions that…
modu-ai/moai-adk
Question-design reference for the gated TypeSafe System One judgment capability.
sickn33/agentic-awesome-skills
Run read-only, browser-grounded Instagram, TikTok, or LinkedIn research through Jev routing and socai CLI, returning source-linked evidence and reports.
sickn33/agentic-awesome-skills
Route enumerable judgment steps - did it work, which option, how risky, is this safe to run - to the Jev judgment model through the jevjudge and jevgate MCP tools, batched into one call per state.
rlaope/oh-my-hermes
[omh] User named Jev for yes/no or pick-one probabilities: Jev ask: typed yes/no, pick-one, or scored questions to Jev with your own key; returns probabilities, never prose.
brycewang-stanford/Auto-Empirical-Research-Skills
Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.
cobusgreyling/Jev
Use TypeSafe Jev for typed judgments (Choice, Score, Noul) instead of asking a chat model to classify.
cobusgreyling/Jev
Route with TypeSafe Jev — map Choice plus confidence to act/confirm/human, or pick a coding-agent model tier.
cobusgreyling/Jev
Screen LLM input and output with TypeSafe Jev Noul hazard batteries plus a harm Score; policy in code returns pass, review, or block.
Ask every independent TypeSafe Jev question in one POST /v1/systemone (speculative fan-out). Jev Fanout is an agent skill from cobusgreyling/Jev. Ask every independent TypeSafe Jev question in one POST /v1/systemone (speculative fan-out).
Jev Fanout fits situations like: parallel questions; compound commands; one-call turn assessment; the user runs /jev-fanout.
Run `npx skills add cobusgreyling/Jev --skill jev-fanout -a claude-code`. Or copy the skill folder (skills/jev-fanout in cobusgreyling/Jev) into .claude/skills/jev-fanout in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cobusgreyling/Jev --skill jev-fanout -a codex`. Or copy the skill folder (skills/jev-fanout in cobusgreyling/Jev) into .agents/skills/jev-fanout in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cobusgreyling/Jev --skill jev-fanout -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jev-fanout, .gemini/skills/jev-fanout, .github/skills/jev-fanout and .opencode/skills/jev-fanout in your project.
Going by SKILL.md and its folder, Jev Fanout needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: docs.typesafe.ai. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Jev Fanout is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 603 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jev Fanout: Jev Question Translator (lawve-ai/awesome-legal-skills, 847 stars), Moai Ref Jev Question Design (modu-ai/moai-adk, 1.2k stars), Jev Social (sickn33/agentic-awesome-skills, 47k stars) and Jev Use (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cobusgreyling (a GitHub user) maintains it in cobusgreyling/Jev, which has 136 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 10, 2026.
Source: cobusgreyling/Jev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.