odinfree/storm-ecdsa-harness / skills/jev-second-perspective
jev-second-perspective
VerifiedUse TypeSafe's Jev as a fast, typed second opinion inside a research or optimization lane. Rank candidate levers by composite score, or check a write-up's claims against a lab log. Pair it with TypeSafe's own typesafe-ai skill, which owns the API and its docs.
Schiedsrichterli (jev-second-perspective)
Jev as a second-perspective judge
Jev returns typed judgments (Choice, Score, Noul) with probabilities; it does not reason or generate text. Code owns retrieval, arithmetic and policy; Jev supplies one narrow judgment per question. Read the typesafe-ai skill and the live docs (https://docs.typesafe.ai/llms.txt) before changing request shapes.
Client
python3 scripts/jev.py REQUEST.json [OUT.json] (POST /v1/systemone, model defaults to jev-latest) and
python3 scripts/jev.py --models. The key comes from $TYPESAFE_API_KEY or ~/.config/typesafe/api-key (mode 600);
never put it in a request file, artifact, skill or command line. Billing is per input token; output is free.
Pattern 1: lever triage (composite scoring)
State = the task, the rules (gates, time guard, editable files, cost weights) and the candidates with their ledgers. Per candidate ask two independent Scores (feasibility under the rules; share of the required gap) and one Choice over all candidates for "the next hour of work". Multiply in code. Treat it as a tie-breaker and a blind-spot detector: a candidate it rates plausible but unmeasured is the next thing to measure, cheaply. Do not trust the rating itself.
Pattern 2: citation check of a public draft
Code splits the draft into claim blocks (those with job ids or large numbers), retrieves the log entries that share the most ids/numbers, and asks one Choice per (claim, entry): supports / contradicts / says_nothing. Only confidence >= 0.8 stands on its own; route every "contradicts" to a human check. In practice most contradictions came from retrieving a neighbouring job's entry; retrieve by the claim's own id first. It still caught an actual overclaim ("twelve records" when the board's twelve include another participant's starting record).
Limits
Jev judges only the state you give it; it cannot verify soundness, run code, or invent constructions. Never let a Jev answer authorize a submission, a post, or spend: those stay with the measured gates and the user.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |