Who it is forAn agent or developer building a queue that should surface urgent messages first.
The problemUrgency is a judgement that depends on wording, not on a fixed keyword, so simple filters miss many urgent messages.
The outcomeEach message gets a noul score between 0 and 1, where values closer to 1 lean more toward Yes.
What you need first
- Python with pip to install the strands-decider package
- A machine that can run a 2B model: a CUDA GPU, an Apple-silicon Mac, or CPU
- Text inputs you want to classify, route, or score
Steps
pip install strands-deciderstrands-decider ask StrandsAgents/strands-decider-2B-qwen3.5-v1-2610 --state "Help! My payouts have been failing for 3 days! " --noul "Does this convey urgency?"(inferred, check the README)- Read the noul_0 value. Treat values near 1 as urgent and values near 0 as not urgent.
- Put messages above your chosen cutoff at the top of the queue.
Prompt for your agent
Using the strands-decider repo, run the ask command with --state set to <message text> and --noul set to "Does this convey urgency?". Return the noul value. Verify that the value is between 0 and 1 and that a clearly urgent test message scores higher than a routine one.
Caveat. The README gives no fixed cutoff for urgency, so you need to pick and test your own threshold on your own messages.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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