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

How to filter a social feed with a Jev classifier with Awesome Jev Use Cases

Adapt a listed feed-filter demo to score posts as you scroll.

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

Who it is forA developer building a personal feed filter who wants to hide low-quality posts without a slow model call.

The problemKeyword filters miss tone and quality, and a full text model may be too slow or costly for every post.

The outcomeA function that takes a post and returns a Jev typed answer, such as keep or hide, with a confidence value.

What you need first

  • A TypeSafe Jev API bearer key
  • Network access to https://api.typesafe.ai/v1/systemone
  • A copy of this repo or its docs folder, including docs/api-quickstart.md

Steps

  1. Open Content and growth and read the entries for the real-time slop detector and the doomscroll filter.
  2. Read Patterns to see how the working demos are put together.
  3. Read Limits of Jev 1.13 and note that accuracy drops with irrelevant state, so send only the post text.
  4. Send a POST to https://api.typesafe.ai/v1/systemone with your bearer key, using docs/api-quickstart.md.
  5. Test on 50 saved posts and record how many decisions you would change by hand.

Prompt for your agent

Using the repo walidboulanouar/awesome-jev-use-cases, read the Content and growth section and the Patterns section, then write a function that sends one post text from <posts-file> to the Jev API and returns a keep or hide decision with a confidence value. Verify by running it on 50 saved posts and confirming every result is keep or hide.

Caveat. The README lists the demos but does not say how any of them handle platform terms, so check that before you run a filter on a live feed.

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