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

How to rank a shortlist by weighted criteria in CI with Awesome Jev

Score each item on weighted dimensions from a YAML spec and gate builds on the result.

Who it is forAn engineer or ops lead who needs a repeatable ranking of candidates inside shell scripts or CI pipelines.

The problemManual scoring of candidates is slow and inconsistent, and it is hard to enforce a threshold in automation.

The outcomeA weighted ranking produced from a YAML spec, with thresholds that fail a shell or CI step when not met.

What you need first

  • Access to Jev through the TypeSafe early-access entry point at typesafe.ai
  • A small labeled sample of your own data to check Jev answers before relying on them

Steps

  1. Open the jeff-cli repository at github.com/saembit/jeff-cli and read its YAML spec format.
  2. Write a YAML spec that lists your weighted dimensions for the items you are ranking.
  3. Run the noul, choice, or score command described in the jeff-cli README against your items.
  4. Set the threshold so a failing result returns a non-zero exit code, then wire that into your shell script or CI step.
  5. Hand-check three ranked items against the spec before trusting the ranking.

Prompt for your agent

Use the jeff-cli project at github.com/saembit/jeff-cli with a YAML spec for <target candidates>. Run its noul or score command and report the ranked list and any threshold failures as exit codes. Verify that three items match a manual check of the spec weights.

Caveat. Jev answers depend on the text you supply, so check the weighted ranking against labeled examples before using exit codes to block a release.

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