Reference implementation for Jev builders: a Claude Code hook that asks TypeSafe's Jev which installed skill fits eac...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if jev-skill-router belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/shimo4228/jev-skill-router && cd jev-skill-router && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf jev-skill-routerNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ jev-skill-router/ ← clones here
Reference implementation for Jev builders: a Claude Code hook that asks TypeSafe's Jev which installed skill fits each prompt and logs the answer. Run for a week and then removed; the README keeps the parts that carry over and the measurement.
Source: GitHub repository
Source check: October 11, 2026
Upstream commit: October 10, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.