JevForAgents中文English
MCP 与 Skills · 工具选择

Eng Khairallah Jev Skills Workflow

这是 Khairallah AL-Awady 公开的项目资料。本站按原始来源展示项目信息,用中文说明适用场景和阅读边界;项目名、源帖与代码保持原样,便于逐项核对。

这条案例记录了什么

场景

MCP 与 Skills、工具选择

以可调用工具的形式返回结构化判断。

证据

社区公开项目或作者演示

原始来源:Original post on X by @eng_khairallah1。作者自述,本站未独立复现。

时间与作者

Khairallah AL-Awady

记录日期:2026-09-20。日期与身份应以原始资料为准。

怎样核对这个项目

  1. 先打开原始来源,确认作者、日期与 Jev 在项目中的具体用途。
  2. 如果提供仓库,再检查代码、运行要求和许可证;仓库存在不代表本站已经运行成功。
  3. 对速度、成本、准确率和规模数字,查看原文的任务、环境和计算口径。
  4. 真实调用入口和参数。
  5. 密钥及权限边界。
  6. 工具失败时的行为。
  7. 工具列表和版本。

原始文字与技术细节

以下内容保留原语言,供核对事实。中文页的场景说明是阅读提示,不是逐句翻译或实测结论。

展开英文项目摘要与原帖

项目摘要

10 分钟 Jev 上手指南,从访问和安装到拿到第一个决策结果。

来源原文

how to setup and use Jev in 10 minutes from nothing to a call that returns a decision 1. get access join the waitlist at typesafe, people report getting in within a day don't want to wait, it's already hosted in two places: → vercel ai gateway as typesafe-ai/jev, no waitlist → cloudflare workers ai as typesafe/jev 2. install the skill so your agent writes the call correctly npx skills add typesafe-ai/skills --skill typesafe-ai on claude code it's two commands: - claude plugin marketplace add typesafe-ai/skills - claude plugin install typesafe@typesafe-ai then in your prompt just say "use the typesafe skill" 3. learn the shape before you write a line the body is a state and a map of questions. the state is your context, whatever you would have pasted into a prompt. the questions are typed three types, that's the entire api: → Noul returns a raw 0 to 1 → Choice picks one from up to 255 options you define → Score places it on a 2 to 10 level scale every Choice and Score comes back with a confidence from 0 to 1 4. make the first call a real one pick a decision already living in your code as an llm call that never writes text. the "which of these" one how to do it: - build the option list in your own code, not in the prompt - send your existing context as the state, unchanged. don't rewrite it yet - ask your question plus three more you're curious about, they run in parallel against the same state and output tokens are free - log the answer, the confidence, and what your old call said - leave the old call running. delete nothing on day one 5. put a limit on it before it touches anything read confidence on every response, never just the answer low limit for reading and sorting. 0.85+ for anything you cannot undo. everything under the limit falls through to the old call that fallback is four lines, and it's the reason you can ship this on a tuesday instead of planning it for q4 the 10 minutes is real. the hour after is the actual work: you, a log of answers and confidences, deciding where your lines go start in the playground in the console, and paste a real state from your own product, not the sample one

原记录的限制

  • Implementation details are based on the author's public post on X.
  • Performance figures and benchmarks are author-reported community claims.
  • Production deployments may require custom calibration and policy thresholds.

继续浏览

返回中文案例目录 · 阅读相关应用场景