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

How to grade how obstructed each package is in a photo with JEV Sees

Score every detected package in a warehouse image against a rubric you define.

  • Research
  • Intermediate
  • 45 minutes
  • From the README
  • Any agent

Authorization notice. JEV Sees is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Use an environment variable for TYPESAFE_API_KEY rather than hard-coding the key in the script.

Who it is forA warehouse operations lead who reviews shelf or dock photos and needs a consistent obstruction grade for each package.

The problemChecking each package in many photos against the same standard by eye produces uneven results.

The outcomeA structured export of one score per package, with the rubric text the application supplied.

What you need first

  • Python 3.10 or newer
  • A JEV API key from console.typesafe.ai/keys
  • Internet access for the first run, unless the Florence-2 and CLIP weights are already available locally
  • Git and a terminal

Steps

  1. Clone the project with git clone https://github.com/CharlesFeng0314/JEV_sees.git.
  2. Enter the folder with cd JEV_sees.
  3. Install it with python -m pip install -e ..
  4. Set your key on macOS or Linux with export TYPESAFE_API_KEY="your-key", or in PowerShell with $env:TYPESAFE_API_KEY = "your-key".
  5. Write a short Python script that imports Sees from jev_sees and calls Sees().for_each("package").score(...) on your photo with your rubric, then sets json="output.json" to export the results. (inferred, check the README)

Prompt for your agent

In the JEV_sees repo at <repo path>, write and run a Python script that calls Sees().for_each("package").score(...) on <photo path> with the rubric 0: clear, 1: partly obstructed, 2: heavily obstructed. Expect one score per package in output.json; verify that every score is one of the three rubric levels.

Caveat. The score method is part of an experimental v0.1.0 API that the README says may continue to change, so pin the version you test.

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