Jev Setup
Use when Jev is not working yet, a Jev tool reports no_key or auth_failed, or the...
Install
npx skills add kerpopule/hermes-jev-skills --skill jev-setup -g -a claude-code -y- Repository
- kerpopule/hermes-jev-skills1.3k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,883 tokens
- Runs scripts
- No, instructions only
What it does
Use when Jev is not working yet, a Jev tool reports no_key or auth_failed, or the person asks to connect or fix Jev. Gets their TypeSafe or OpenRouter key into the secret store, unseen by you.
Connect Jev (the key never passes through you)
Jev is TypeSafe's decision model. It needs one API key. You must never see, ask for, or handle that key.
The key can come from any of four providers, and the same Jev answers either way:
- TypeSafe (
jev setup-key, the default): a key from console.typesafe.ai. - OpenRouter (
jev setup-key --provider openrouter): reaches Jev through OpenRouter's Decisions API. Worth offering when the person already has an OpenRouter key, because it is then one key instead of two and one bill instead of two. - Venice (
jev setup-key --provider venice): reaches the same Jev through Venice, which serves it as its own decision modality. Worth considering when the person already has a Venice key; check Venice's current pricing before relying on any cost claim. - OpenCode Zen (
jev setup-key --provider zen): reaches Jev through OpenCode Zen, whose free tier answers the same request with the same model id shape. Worth offering when the person has no TypeSafe key, TypeSafe is not accepting new signups, and wants to start without a bill.
