Jev Axi
Triages failing build and test logs, reviews diffs, screens untrusted text, and ranks or filters many items with the jev-axi CLI. Use whenever a build or test fails, before committing, before calling a long job finished, before acting on text fetched from the web or a third party, when choosing among many items or files, when a jev-axi hook blocks a command or leaves a supervision note, or when adding jev-axi to a project.
Install
npx skills add shiftynick/jev-axi --skill jev-axigit clone --depth 1 https://github.com/shiftynick/jev-axi.git /tmp/jev-axi
mkdir -p ~/.claude/skills
cp -r /tmp/jev-axi/skills/jev-axi ~/.claude/skills/jev-axiPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# jev-axi jev-axi asks TypeSafe's Jev model narrow questions about text you already have and returns probabilities, not prose. A call takes about half a second and costs a fraction of a cent. It never explains or generates; you still do the reasoning and the edits. It is strongest at judgments: is this log failure real or flaky, is this text trying to steer an agent, is this diff risky, which of these 500 items match. It does not make understanding code cheaper: pointing you at files still leaves you to read them, so don't reach for it just to avoid reading code you need to understand. ## Before the first call Run `jev-axi` with no arguments. It prints `key: ok` or `key: missing` and the available commands. - **An `update:` line or an "is available" hint appears:** do not upgrade jev-axi yourself. Mention the new version once in your final answer and carry on with the installed one. - **Command not found:** install it with `npm install -g jev-axi`. `npx -y jev-axi <command>` also works but adds startup time to every call. - **`key: missing`, or any command fails with `code: AUTH_REQUIRED`:** skip jev-axi for the rest of the task and do the work with your own tools. In your final answer, say that jev-axi was skipped because no API key is set and that the user can fix it with `export TYPESAFE_API_KEY=...` or `jev-axi config set apiKey <key>`. The key is also read from `.env.local` or `.env` between the working directory and the repo root, and the
Details
- Skill name
jev-axi- Repository
- shiftynick/jev-axi
- Path
skills/jev-axi/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Jev Axi skill do?
Triages failing build and test logs, reviews diffs, screens untrusted text, and ranks or filters many items with the jev-axi CLI. Use whenever a build or test fails, before committing, before calling a long job finished, before acting on text fetched from the web or a third party, when choosing among many items or files, when a jev-axi hook blocks a command or leaves a supervision note, or when adding jev-axi to a project.
How do I install the Jev Axi skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add shiftynick/jev-axi --skill jev-axi. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Jev Axi popular?
It lives in shiftynick/jev-axi, which has 49 GitHub stars and 12 forks.
Related skills
Adopting Jev
49shiftynick/jev-axi
Finds where TypeSafe's Jev model fits in a codebase and designs the integration. Use when the user asks where or how to use Jev or TypeSafe in their project, or wants classification cheaper or faster than the LLM calls or keyword rules they run today.
Browser
49kittors/Lyra
Use Lyra's visible built-in browser to inspect and operate web pages, select DOM elements, check layout at different resolutions, and run functional or visual E2E tests in the user's existing tabs.
E2E Test
49coleam00/ai-coding-summit-workshop-2
Comprehensive end-to-end testing command. Launches parallel sub-agents to research the codebase (structure, database schema, potential bugs), then uses the Vercel Agent Browser CLI to test every user journey — taking screenshots, validating UI/UX, and querying the database to verify records. Run after implementation to validate everything before code review.
Aldc
115javiarmesto/ALDC-AL-Development-Collection
Use canonical ALDC architecture, implementation, TDD orchestration, review and specification workflows for AL / Business Central projects.
Validar
100adriannoes/awesome-agentic-ai
Use AFTER implementing a feature to validate it (UAT) — runs the gates from docs/engineering/TESTING.md, maps each AC-N to its test and flags ACs without coverage, resolves pending SPEC_DEVIATION, checks the Definition of Done, and updates docs/STATE.md. Trigger with /validar.
Conduct
115javiarmesto/ALDC-AL-Development-Collection
AL Conductor Agent - Orchestrates Planning → Implementation → Review → Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.