jev-triage
Skill2 starsChanged 53 days agoMITView on GitHub
Use when a support message, bug report, or other record needs one label such as billing, bug, or how-to, plus a harm score for a wrong label. Runs @aitofy/jev-awesome-skills. Do not send a mailbox or delete messages.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- wuyoscar/jev-skilltheir own version, first seen Sep 28, 2026
- ZephyrDeng/jev-triagetheir own version, first seen Sep 28, 2026
- WanLanglin/jev-skillstheir own version, first seen Sep 21, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- wuyoscar/jev-skill★ 665same name
- WanLanglin/jev-skills★ 1same name
- ZephyrDeng/jev-triage★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-routeSkill
- jev-verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
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
Triage
Judge records you already have. Do not connect to a mailbox, delete, reply, or move messages as part of this skill.
Preset labels are billing, bug, how_to, other, and ask_user. Replace them with the labels you and the user agreed, and keep ask_user. One record per request. Put the record text in state and run:
jev questions triage
jev --dry-run --file request.jsonShow the dry-run before a live call when the text is private. The package is @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. Proceed means apply the label in your tracker. Ask means leave it for a person.
On "source": "fallback", fail open and leave the record unlabeled. Do not invent a probability.
Template: examples/triage.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.