New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jev

by joetawil7 in joetawil7/first-pass

Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small…

MITAuto-check: notesDevelopment

Install Jev

skills CLI
$ npx skills add joetawil7/first-pass --skill jev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joetawil7/first-pass jev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joetawil7/first-pass.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/jev .claude/skills/jev && rm -rf skills-src

Use ~/.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/

Facts

Skill name
jev
GitHub stars
95
Token cost
~1.4k tokens
SKILL.md length
726 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small…

  • Works in 5 steps: Where it stands → What the user wants → Write the config → …
  • Tasks that involve Code review
  • SKILL.md covers What leaves the machine, 1. Where it stands, 2. What the user wants and 3. Write the config, plus 2 more sections
  • Calls node; reaches api.typesafe.ai; needs TYPESAFE_API_KEY and COMPANY_A_TYPESAFE_API_KEY

What it does

Jev is an agent skill from joetawil7/first-pass. Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small fix need). Shows whether it is on for each repo, which key it uses, switches it on or off, and sends one test request. Runs only when the user types it.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. The repository describes itself as: Rules and checks that make Claude Code look around a change, not just at the lines it writes: ten questions before code, a reviewer that didn't write it, proof before done, bugs… The licence is MIT.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “/jev”

Requirements

  • A credential in TYPESAFE_API_KEY
  • A credential in COMPANY_A_TYPESAFE_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Where it stands
  2. What the user wants
  3. Write the config
  4. Check it works
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit f5bc413. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.typesafe.ai

    Also links to:

    • docs.typesafe.ai
    • console.typesafe.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TYPESAFE_API_KEY
    • COMPANY_A_TYPESAFE_API_KEY
    • COMPANY_B_TYPESAFE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jev loads about 1.4k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 726 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:76
    E_API_KEY", "file": "/abs/path/company-a/.env.local", "repos": ["/abs/path/company-a", "/abs/path/company-a-site"] },

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.

SKILL.md

The full file from joetawil7/first-pass at commit f5bc413, republished under its MIT licence (© joetawil7). 726 words, ~1,360 tokens.

Download SKILL.mdSave it as .claude/skills/jev/SKILL.md (or your agent's skills folder).
name
jev
description
Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small fix need). Shows whether it is on for each repo, which key it uses, switches it on or off, and sends one test request. Runs only when the user types it.
disable-model-invocation
true
argument-hint
<nothing, "off", "on", or what to change>

jev

Jev is TypeSafe's decision model: it picks one option from a list and says how sure it is. With the Claude Code plugin, ship-check can ask it three things about a review's findings:

  • harm: does this finding do real harm (money, data, a side effect done twice or sent wrong, security, legal, a crash, stuck work, or the change not doing its job)? Jev can make a finding real harm. It can never clear one the review named, and an answer below its confidence floor, or any failure, leaves the call to the rules.
  • priority: for the list of smaller findings, which to recommend fixing now.
  • proof: for a small fix the user picked, the least proof it needs (the repo's checks only, a unit test, a test against the real database or service, or a browser test). A real-harm fix always gets the full proof.

Without the judge, the rules make each call as written. Nothing here is needed to use first-pass.

What leaves the machine

For each finding asked about: its scenario, its worst case, who meets it and, for proof, the fix in one line, after secrets, emails and phone numbers are blanked. They go to TypeSafe's API (https://api.typesafe.ai/v1/systemone) with the key. TypeSafe charges per word sent; check the current price on its models page (https://docs.typesafe.ai/models) before telling the user a number. Its data terms: https://docs.typesafe.ai/legal.

1. Where it stands

For the current folder, and for one repo of each group the user keeps apart (two companies with separate accounts):

node "${CLAUDE_SKILL_DIR}/../../scripts/cli.mjs" jev status <repo>

It prints on or off, why, where the key comes from (a variable name and a file, never the key) and the config file's path.

2. What the user wants

From what they typed (nothing: show the status and ask; "off" or "on": do that), or ask in one message:

  • Do they have a Jev API key? If not, say where one comes from (TypeSafe's console, https://console.typesafe.ai/keys) and stop.
  • Where is it set? The name of the variable that holds it, and whether it is in the environment or in an env file (the file's path; it must be one git ignores). Never ask for the key itself; if one is pasted, don't repeat it, and say it should be rotated.
  • For which repos? One key for everything, or a key per group of repos when they belong to separate accounts (then every group is named, and a repo no entry names has the judge off).
Show full SKILL.md (316 more words)Show less

3. Write the config

The config file is the path jev status printed (first-pass/jev.json in the Claude Code config folder, ~/.claude unless CLAUDE_CONFIG_DIR says otherwise). Read it first if it exists and change only what the user asked:

One key for everything:

json
{ "keys": [{ "env": "TYPESAFE_API_KEY" }] }

A key per account:

json
{
  "keys": [
    { "env": "COMPANY_A_TYPESAFE_API_KEY", "file": "/abs/path/company-a/.env.local", "repos": ["/abs/path/company-a", "/abs/path/company-a-site"] },
    { "env": "COMPANY_B_TYPESAFE_API_KEY", "repos": ["/abs/path/company-b"] }
  ]
}
  • env: the variable's name. It is read from the environment first, then from file.
  • file: optional, an env file holding NAME=value.
  • repos: absolute paths. The deepest one that holds the folder wins, and a checkout of a named repo elsewhere (a worktree, a clean checkout in the temp folder) counts as that repo, even inside a folder named for another key. An entry without repos covers every folder, and is allowed only as the only entry: with separate accounts, a folder no entry names has the judge off, never another account's key.
  • With separate accounts, name each repo's own folder. Never name a folder that also holds another account's repos (the main folder above them all, say): a named folder covers every folder inside it, new repos included, so a repo cloned there later would get that key.
  • "off": true switches the judge off everywhere and keeps the rest. "model" pins a version (default jev-latest); pin one when you have tuned against it.
  • "url": only to send somewhere other than TypeSafe's endpoint (https, or this machine for a test server); jev status then shows it. Leave it out otherwise, and remove one the user did not ask for.
  • Before writing a file path, check git ignores it: git -C <its repo> check-ignore -q <file>. If it is not ignored, say so and don't use it.

4. Check it works

Run jev status <repo> again for each group, then once per key:

node "${CLAUDE_SKILL_DIR}/../../scripts/cli.mjs" jev test <repo>

It sends one made-up finding (no code, no customer data) and prints Jev's pick and how sure it was. A refused key or no answer prints why.

5. Report

Jev judge: <on for <repos> (key from <NAME>, in the environment | in <file>) | off, <why>>, one line per key
Verified: jev test → <Jev's pick and confidence, or the error>, one line per key
Config: <the file, and what changed>

© joetawil7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/jev of joetawil7/first-pass.

Open the folder on GitHubat commit f5bc413

Compare with similar skills

Jev 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.

Jev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jev this skilljoetawil7/first-pass95—~1.4kAutomated safety check: NotesMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Backend Code Reviewlangflow-ai/langflow155k—~3.5kAutomated safety check: NotesMIT
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0
Backend Code Reviewlanggenius/dify158k—~676Automated safety check: PassCustom licence

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Backend Code Review

    langflow-ai/langflow

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules.

    155k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Mole Bug Patterns

    tw93/Mole

    A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from joetawil7/first-pass

All 9 skills in this repo

  • Fix The Class

    joetawil7/first-pass

    Bug-fix routine that fixes the whole class of bug, not just the reported instance.

    95 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Habit Words

    joetawil7/first-pass

    Learns the words a user habitually writes to their coding agent that make its answers worse ("be 100% sure", "don't assume", "full review", "are you sure?", "all fine, right?"), from what they…

    95 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Premortem

    joetawil7/first-pass

    Run before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour.

    95 GitHub stars~2.5k tokensUpdated today
    Auto-check: notes

  • Sharpen

    joetawil7/first-pass

    Rewrites the prompt typed after the command before any work starts, then works from the rewrite.

    95 GitHub stars~1.9k tokensUpdated today
    Auto-check: notes

  • Review

    joetawil7/first-pass

    Reviews a change before it is merged, from little or no input.

    95 GitHub stars~6.3k tokensUpdated today
    Auto-check passed

  • Ship Check

    joetawil7/first-pass

    The definition of done. An agent skill from joetawil7/first-pass.

    95 GitHub stars~5.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Jev

What does Jev do?

Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small…. Jev is an agent skill from joetawil7/first-pass. Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small fix need).

When should I use Jev?

Jev fits situations like: tasks that involve Code review.

How do I install Jev in Claude Code?

Run `npx skills add joetawil7/first-pass --skill jev -a claude-code`. Or copy the skill folder (skills/jev in joetawil7/first-pass) into .claude/skills/jev in your project. Claude Code loads it when a task matches its description.

How do I install Jev in Codex?

Run `npx skills add joetawil7/first-pass --skill jev -a codex`. Or copy the skill folder (skills/jev in joetawil7/first-pass) into .agents/skills/jev in your project. Codex loads it when a task matches its description.

Can I use Jev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joetawil7/first-pass --skill jev -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, .gemini/skills/jev, .github/skills/jev and .opencode/skills/jev in your project.

What does Jev need to run?

Going by SKILL.md and its folder, Jev needs the command-line tools its instructions call (node) and credentials named TYPESAFE_API_KEY, COMPANY_A_TYPESAFE_API_KEY and COMPANY_B_TYPESAFE_API_KEY. Our summary lists: A credential in TYPESAFE_API_KEY; A credential in COMPANY_A_TYPESAFE_API_KEY.

Does Jev access the network?

SKILL.md names 3 domains. In commands or code: api.typesafe.ai; the agent is likely to contact it when it follows the instructions. As links in the text: docs.typesafe.ai and console.typesafe.ai. This is read from the text; nothing was executed.

Is Jev safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Jev use?

Jev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jev use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jev?

Skills that share tags, products or a category with Jev: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 155k stars) and Mole Bug Patterns (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jev?

joetawil7 (a GitHub user) maintains it in joetawil7/first-pass, which has 95 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: joetawil7/first-pass on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.