Case study · located work
TypeSafe Agent Skills
TypeSafe's own published Claude Code plugin and skills.sh package that teaches coding agents to design and wire up Jev workflows.
ObservedTypeSafe (vendor)
- Problem
- TypeSafe's own published Claude Code plugin and skills.sh package that teaches coding agents to design and wire up Jev workflows.
- Jev’s role
- The skill's entire purpose is composing typed Jev judgments (Choice, Score, Noul) into agent-written code.
- Architecture
- Agent skill install (plugin marketplace or skills.sh) → SKILL.md instructions → agent composes TypeSafe API calls in the user's codebase.
- Why it matters
- Vendor-authored, so it demonstrates TypeSafe's own recommended integration pattern rather than independent adoption evidence.
Code boundary
Jev answers the bounded questions described above. Thresholds, retries, side effects, and anything that must be reproducible stay in the surrounding application code. The research record does not capture this project’s exact question set or threshold values; read the linked source before copying the architecture.
Sources
Limitations
- A located repository or demonstration does not establish production reliability or independent validation.
Reusable pattern and related records
- Decision quorum PlausibleMultiple typed judgments are aggregated through voting or confidence-aware stopping.
- Agent Loop Stopper Authored HypothesisA loop controller deciding continue, retry differently, verify, ask, or stop after every step.
- Jev exposes constrained decision primitives for Boolean probability, choice distributions, and ordered scores. DemonstratedThe public API documentation defines `noul`, `choice`, and `score` response shapes.
- Decision sidecar PlausibleA typed judgment service sits beside ordinary code; code owns effects and safety boundaries.