jev-shopper

Design and validate simulated shop windows where Jev calls best buys on streaming prices.

465|41|Updated Aug 4, 2026
One-click install
npx skills add https://github.com/autonomous-ai/openharness --skill jev-shopper-autonomous-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jev-shopper
Source: https://github.com/autonomous-ai/openharness/tree/main/store/agents/jev-shopper/skills/shopper
Command: npx skills add https://github.com/autonomous-ai/openharness --skill jev-shopper-autonomous-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It lets you design and verify a simulated live shop window in OpenHarness, where streaming product prices test whether the Jev model can correctly identify real deals versus noise-driven wobbles. ## Core Features & Use Cases - Shop Configuration: Edit shopper.json to define products, prices, drift, volatility, tick rate, budget, and deal thresholds, with the viewer updating live without restarts. - Validation: Run node "$JEV_DSH/toolchain/check.mjs" to verify shop configs for missing titles, duplicate names, out-of-range volatility, and other schema errors. - Direct Model Queries: Use toolchain/jev.mjs to ask Jev for its best-buy read on a price window before committing to a shop design, with a deterministic mock when no API key is set. - Use Case: Tune the vol parameter from 0.01 to 0.15 and watch Jev's deal-call accuracy drop from near-perfect to about half, measuring how noise degrades buying decisions. ## Quick Start Edit shopper.json to define your products and price noise, then run the check script and watch Jev call deals in the live viewer.

Frequently Asked Questions about jev-shopper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a shop window for Jev Shopper?

Edit shopper.json to set a title, at least two products with prices and drift, volatility, tick rate, budget, and a style line describing the buying strategy. The OpenHarness viewer watches the file and updates live without a restart.

How do I validate a shopper.json configuration?

Run node "$JEV_DSH/toolchain/check.mjs" from the workspace. It returns non-zero for invalid configs such as missing titles, fewer than two products, duplicate names, non-positive prices, or out-of-range vol, tickMs, cash, minDeal, or drift values.

What does the vol parameter control in price simulation?

The vol parameter sets price noise and acts as the difficulty dial. At 0.01 Jev's deal calls are right almost every time with about 16% savings; at 0.15 wobbles pass for deals, accuracy drops to about half, and savings fall to about 3%.

Can I query Jev directly without running the full viewer?

Yes, import evaluate and jev from toolchain/jev.mjs and pass a state string with price ticks plus structured questions. Without a TYPESAFE_API_KEY it uses a deterministic mock; setting the key hits the live Jev model.

Why does Jev buy wobbles instead of real sales?

High volatility makes random price wobbles look like genuine discounts below the usual price. Lower the vol value in shopper.json, and tick the option to show hidden fair prices in the viewer to confirm whether buys align with real sales.