App collection · Routing / Scoring / Evaluation
Awesome Jev Apps
A large collection of standalone Jev applications with sample data, shared conventions, offline checks, and a machine-readable catalog.
By JustmalharExplore complete app folders with setup instructions, sample inputs, and deterministic decision policies.
What it does
Awesome Jev Apps collects runnable examples across document processing, AI infrastructure, business operations, data engineering, finance, research, moderation, and personal workflows. Each application is designed to stand alone, includes sample data, and follows a repository-wide application specification.
What you can reuse
The most useful layer is the application contract: a self-contained folder, explicit dependencies, provider configuration, copied shared client, sample data, offline tests, and a small README. The repository also keeps a machine-readable catalog.json, making the collection browsable without scraping its Markdown index.
How it fits
Each app turns a domain-specific state into one or more typed Jev questions. Ordinary Python code handles thresholds, ranking, escalation, formatting, and any exact computation. The collection repeatedly separates semantic judgment from deterministic policy.
Setup and compatibility
The documented quick start uses Python 3.11 or newer and uv. Apps can be opened with their included sample data before a user supplies personal files, although live decisions still require a configured provider key.
Limitations
This directory reviewed the collection structure, not every application. Offline tests can validate deterministic logic without establishing live inference quality. Provider compatibility, model context limits, and individual app behavior may change; inspect the selected app's own README before use.
Sources
Primary sources: Awesome Jev Apps and its application specification.
TAKE AN IDEA INTO YOUR CODE
Related copyable example
Each example states whether its question is extracted, adapted, or independently written. It is a starting point, not the whole project.
Decide if an agent needs a tool
Screen out conversational turns before selecting from a tool catalog.
Does answering this turn require calling a tool at all?