augustus
SolidUse when placing typed probabilistic judgment (Jev-class System One / decision models) with mathematical, logical, or algorithmic mental models — in AI, software, business, knowledge work, or life, not only SWE; deciding where a fast cheap categorization/classification/scoring model belongs versus generation, exact policy/code, or proof; applying expected utility, selective classification/abstention, calibration, cost-sensitive thresholds, value of information, MCDA, signal detection, search/control substitutions, or Leveson-style org/safety; using NATM/snap-fit/Norman as design intuition; designing mixed architecture (decision model + LLM writing); auditing an existing system, PR, workflow, or non-software practice for judgment-shaped holes and code smells; debugging a question that hovers near 0.5, clusters mid-scale, or hides two judgments; placing agent self-supervision gates (pre-action, output judge, done-check, stuck-detector, context sieve); coupling a typed judge as an optimizer metric (Ax, DSPy); ch
Install
Quality Score: 82/100
Skill Content
Details
- Author
- 24601
- Repository
- 24601/Augustus
- Created
- 1 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
jev
Use when writing or improving Jev programs — the TypeSafe judgment model behind POST /v1/systemone. Covers primitive selection (noul, choice, score), instruction and criteria writing, minimal state and token budgets, the raw HTTP API, confidence-gated composition, speculative fan-out, and the symptom-to-fix revision table. Triggers: jev, judgment model, typesafe, systemone, noul, choice, score, confidence floor, jaggedness.
jev-judgment-design
How to hand over judgments and decide accept/reject when moving closed judgments an LLM used to make (is this source relevant, is it new, how strong is the evidence) to TypeSafe's Jev. Putting what the judgment is made against into state, the bottom tier of a Score, Jev answers and code decides, the unit of judgment, sources that must pass (canary), calling from Pydantic AI. Use when — "I want to replace the LLM's judgment with Jev", "build a relevance judgment with Jev", "Jev's judgment lets everything through", or before designing Jev into screening / triage / rerank. NOT for — Jev's API, docs, or general guidance on choosing primitives (→ plugin skill `typesafe:typesafe-ai`; read that first), the Claude Code skill-selection hook (→ `jev-skill-router`), designing an LLM as the judge (→ `llm-as-judge`).
jev-agent-toolkit
Build with Jev, TypeSafe's System One model, as a bounded judgment layer alongside general-purpose agents. Use when calling the TypeSafe API or SDKs, when designing Choice, Score or Noul questions, when classifying, routing, ranking or filtering with confidence thresholds, or when the user mentions Jev, TypeSafe, System One, or bounded semantic judgment. Also covers capability-driven orchestration of external tools (browser research, MCP servers, Blender, Unreal Engine) and multi-agent delegation with sequential fallback.