typesafe-ai

Compose typed AI judgments and probabilities into application code using TypeSafe System One models.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill typesafe-ai-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typesafe-ai
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/typesafe-ai
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill typesafe-ai-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning natural-language understanding into reliable application behavior usually means fragile LLM prompt-and-parse steps. This Skill guides you to replace those with TypeSafe's System One models (like Jev), which return typed judgments and probabilities that ordinary code can combine, route on, and verify. ## Core Features & Use Cases - Typed judgment primitives: Design Choice, Noul, and Score questions over structured state so code receives typed answers and probabilities instead of generated text. - Composition patterns: Apply proven shapes such as routing with argument filling, select-instead-of-generate extraction, reranking, composite scoring, verification with escalation, and state-responsive agents. - Live documentation workflow: Read the current TypeSafe docs, API references, SDK pages, and cookbooks as the source of truth before writing any integration. - Use Case: When building a support ticket router, ask branch-specific questions up front, consume only the relevant typed answers, and let code own the workflow while the model supplies the semantic judgment. ## Quick Start Ask the AI to design a TypeSafe integration that routes incoming user requests to typed handlers using Jev judgments instead of an LLM prompt-and-parse step.

Frequently Asked Questions about typesafe-ai

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

FAQPage Schema
How do I replace an LLM prompt-and-parse step with typed judgments?▼

Define one narrow judgment per question using TypeSafe primitives: Choice for selecting one option, Noul for a yes/no probability, and Score for graded dimensions. Provide relevant state as named JSON fields and let code consume the typed answers and probabilities directly.

What is the TypeSafe System One model Jev used for?▼

Jev is TypeSafe's flagship System One model that understands natural language and returns typed answers and probabilities rather than generating text. It supplies programmable common sense for routing, extraction, ranking, and verification inside application code.

Which SDKs does TypeSafe support for integrations?▼

TypeSafe provides an HTTP API plus Python and JavaScript SDKs, documented at docs.typesafe.ai. The Skill instructs reading the current API or SDK page and relevant cookbooks before writing integration code, keeping credentials server-side in web apps.

How should I handle uncertainty and confidence scores in judgments?▼

Use probabilities and confidence to guide behavior with thresholds evaluated on your own data and consequences. Choice and Score confidence reflects distribution concentration, not workflow correctness, and a Noul near 0.5 means yes and no are similarly probable.

When should I ask multiple questions in one TypeSafe request?▼

Ask independent questions over the same state together, including speculative ones, since they run in parallel and cannot see each other's answers. Use a second request only when an earlier answer is needed to fetch evidence or build new state.