jev-route
Skill2 starsChanged 53 days agoMITView on GitHub
Use when more than one installed skill or tool could handle the turn and you need Jev to pick one, or none, before loading it. Runs @aitofy/jev-awesome-skills. Do not load the whole skill roster into context first.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- jev-actSkill
- jev-awesome-skillsSkill
- jev-gateSkill
- jev-guardSkill
- jev-reviewSkill
- jev-triageSkill
- jev-verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Keep none and ask_user in the criteria.
- Very specific: line 21
Stop when harm.score is at or above 1.5.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Route
You list the skills that are actually installed. Jev picks one label. You load that skill and do the work.
Keep none and ask_user in the criteria. Add each real skill with its one-line description:
jev questions route --option repo-review="Inspect the diff and report file-backed findings"Presets already include none and ask_user. Put the user request and the installed names in state. Run jev from @aitofy/jev-awesome-skills. Do not write a second client.
Stop when harm.score is at or above 1.5. Proceed when the chosen label's probability is at or above 0.9 and determined.noul is at or above 0.9. Otherwise ask. Stop wins. none means answer directly. Do not load a skill the user did not install.
On "source": "fallback", fail open and pick with your own judgment. Do not invent a probability.
Template: examples/route.request.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.