DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to sort a mailbox into lanes with Jev with Hermes Jev Skills

Sort an inbox export into needs-reply, updates, promotional, sales and spam lanes.

Who it is forA person with a backlog of email who wants a quick first sort with per-message cost known in advance.

The problemA long inbox takes time to scan, and most messages do not need a person's attention.

The outcomeA summary of counts per lane, the messages Jev was unsure about, and what the run cost.

What you need first

  • Python 3.9 or newer (no dependencies)
  • A TypeSafe key from console.typesafe.ai
  • Hermes, Claude Code or Codex installed on the machine (the installer finds them)

Steps

  1. Run jev setup-key, paste your key into the page it opens, then run jev doctor.
  2. Export your messages to inbox.json; the README does not give the file format, so check the expected structure with jev mail --help before exporting. (inferred, check the README)
  3. Run jev mail --file inbox.json to sort the mailbox into lanes.
  4. Run jev mail --file inbox.json --summary for counts per lane and the cost.

Prompt for your agent

Using the hermes-jev-skills repo from kerpopule, sort the file <inbox.json> with `jev mail --file <inbox.json>` and then `--summary`. Report the count per lane, the messages Jev was unsure about and the total cost. Verify the lane counts add up to the number of messages in the file.

Caveat. The README does not say how mail content is redacted before it goes to the Jev cloud API, so test with non-sensitive messages first.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page