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

How to triage a support ticket from the command line with Rizzo Flow

Run one decision script on a ticket file without starting a server.

Who it is forA support or operations person who has a ticket saved as a JSON file and wants a quick typed answer such as whether it is urgent.

The problemReading every ticket by hand to set priority takes time, and starting a server for one check is extra work.

The outcomeA typed decision printed for one ticket file, such as an urgency answer with its probability.

What you need first

  • Python 3.11 or newer
  • git
  • uv (https://docs.astral.sh/uv/)
  • About 4.4 GB of free disk space for the default 4B model, plus the llama.cpp runtime (about 11 MB on a Mac, 30 MB with Vulkan, about 570 MB with CUDA)
  • A machine that can run llama.cpp: an Apple, NVIDIA, AMD or Intel GPU, or no GPU at all

Steps

  1. Install Python 3.11 or newer, git and uv.
  2. Run git clone https://github.com/Rizzo-AI-Academy/rizzo-flow && cd rizzo-flow
  3. Run uv sync --locked and then uv run rizzo download.
  4. Write your ticket and its questions into a JSON file in the same format as examples/ticket.json.
  5. Run uv run rizzo decide examples/ticket.json, replacing the path with your own file.

Prompt for your agent

In the rizzo-flow repo, write a JSON file at <path-to-ticket.json> with the ticket text as state and an is_urgent question, then run `uv run rizzo decide <path-to-ticket.json>`. Return the decision and its probability. Verify that the output is a typed answer and not free text.

Caveat. The README says probabilities are uncalibrated, so treat the urgency score as a ranking aid and check it against your own tickets before relying on it.

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