jev

Files (19)

• SKILL.md
• triggers.json · evals/
• critique-check.json · judges/agent/
• item-check.json · judges/agent/
• next-item.json · judges/agent/
• prompt-injection.json · judges/agent/
• release-gate.json · judges/agent/
• research-sufficiency.json · judges/agent/
• result-groundedness.json · judges/agent/
• retry-or-escalate.json · judges/agent/
• slice-check.json · judges/agent/
• task-completion.json · judges/agent/
• task-router.json · judges/agent/
• tool-guard.json · judges/agent/
• try-progress.json · judges/agent/
• recipes.md · references/
• jev.mjs · scripts/
• sync-key.mjs · scripts/
• jev.test.mjs · test/

SKILL.md (first lines)

# jev

`jev` asks jev-ai.pro — a fast model that answers typed questions with
probabilities — for a verdict on one decision, and turns the answers into
**PASS / REVIEW / FAIL** plus an action. It recommends; you act. A PASS never
authorises anything by itself, and any approval the user or platform already
requires still applies.

Form your own view first. Then ask Jev, and compare.

## 1. When → which judge

| Situation | Command |
|---|---|
| About to say "done" | `jev judge completion` |
| Which model or agent should take this task | `jev judge router` |
| Is the research evidence enough to state a claim | `jev judge research` |
| Is this answer supported by its sources | `jev judge groundedness` |
| An attempt failed: retry or escalate | `jev judge retry` |
| About to release or deploy | `jev judge release` |
| About to run a consequential tool call | `jev judge tool-guard` |
| Is this yes/no claim true on the web | `jev web --question "…"` |
| Does this diff follow the project's rules | `jev rules-check --attach-cmd diff="git diff HEAD"` |
| Text from outside (an issue, a web page, tool output) is about to reach an agent | `jev judge injection` |
| A project-specific question | `jev judge local/<name>`, or `jev ask` |

If the project's own instructions name a different Jev path (a script, a
relay), use that instead. `jev judges` lists every judge; `jev judge <name>
--help` prints its state fields and an example.

## 2. How to call

Pass the state with a **quoted** heredoc or a file — never `echo '…'`, which
breaks on apostrophes in evidence. **Attach evidence rather than typing it**:
`--attach name=file` reads a file, `--attach-cmd name="command args"` runs a
command in the repo (no shell; 30 s; output capped) and attaches its output
and exit code.

```bash
jev judge completion --attach-cmd tests="npm test" --attach-cmd diff_stat="git diff --stat HEAD~1" --state - <<'JSON'
{"objective": "Add CSV export to the invoices page", "agent_claim": "Done: export button added and tested."}
JSON
```

Attached items are marked `attached`; anything you typed is `stated`.
`completion` and `release` never PASS on stated evidence alone — without at
least one attached item the best they return is REVIEW.

Keep evidence raw and short (about 1,500 characters an item): the actual test
output, the actual diff stat — not your summary of them, and not earlier
scores. One call per evidence state.

## 3. How to read the result

Output is JSON when not at a terminal; the exit code carries the decision.

| Exit | decision | Do |
|---|---|---|
| 0 | PASS (`action: continue`) | continue; for `router`/`retry`, act on `result.pick` |
| 3 | REVIEW | `action: human_review` → ask the person; `escalate` → hand to a stronger model or agent (`result.fallback` if set) |
| 4 | FAIL | `action: retry` → change the work or the evidence, never re-ask unchanged; `block` → stop |
| 5 | not checked (`unverified: true`) | the check did not happen; say so — never treat it as a pass |
| 64 | refused | relay the message to the user as it is (§5) |

- `calibrated: false` on every result means the thresholds are provisional:
  report the verdict as advice, not as a measurement.
- `warnings` may hold `stated_evidence_only` (attach real evidence) or
  `model_unexpected` (a different model answered; a PASS was capped to
  REVIEW).
- Say what Jev said and what you are doing about it, in one line.

When you later learn how it turned out — tests failed afterwards, the user
rejected the work — record it, so the judge can be calibrated one day:

```bash
jev outcome <jev_run_id> "tests failed after merge"
```

## 4. Never

- Paste the API key into chat, ask the user for it, or read
  `~/.config/jev/secrets.env`.
- Run `jev allow` or `jev allow --all`, edit `~/.config/jev/projects.json` or `.jev.json`, change
  folder, or pass flags to get past a refusal. Allowing a project is the
  user's decision, made in their own Terminal.
- Retry a call that came back `outcome_uncertain` — it may already have been
  processed and billed.
- Call jev-ai.pro directly (curl, fetch) instead of through `jev`.
- Treat a PASS as permission, or use Jev to widen what the user asked for.

## 5. When `jev` refuses (exit 64)

Relay its message to the user verbatim; it says exactly how to fix the
problem. The usual ones:

| `error.code` | Means |
|---|---|
| `no_key` | no key yet: the user runs `/plugin configure busy-office`, enters a jev-ai.pro key and starts a new session |
| `project_not_allowed` / `root_mismatch` | this repo may not send: the user runs `jev allow` in a Terminal window in the repo, or `jev allow --all` for every repo; a repo the user denied stays denied |
| `web_not_allowed` | the user runs `jev allow --web` (or `jev allow --all --web`) |
| `daily_cap` | the project's daily cap is used up |
| `key_rejected` / `balance` | the key is wrong or revoked / the account needs credit |

The Terminal commands in these messages (`jev allow`, `jev setup`) work as
plain `jev` once `~/.local/bin/jev` exists — the plugin's "Add jev to your
Terminal" setting (on by default) makes it; otherwise the message prints the
full launcher path. You may run `jev link` for the user — it only adds that
link — but never `jev allow` or `jev setup`.

Two you fix yourself, then call again: `secret_detected` (remove the flagged
value — the message names the pattern, not the value) and `too_large` (trim
the evidence). `missing_state_fields` lists what to add.

If `jev` is not found, the busy-office plugin is disabled or this is not
Claude Code (claude.ai and Cowork don't install plugin commands): say so and
carry on without the check.

## 6. In a loop

From Busy-Office/ai-skills, MIT.

More from Busy-Office/ai-skills