Skip to content

round3ai/three-dev

unversioned · d19757064e92MIT

Integrate three.dev into a codebase and work with recorded LLM traffic: route calls through the proxy, define use cases and quality metrics, investigate failure modes, and test prompt or model changes with offline experiments, using the three.dev MCP server.

three-dev-quality-metrics-setup

Sets up quality metrics for an LLM feature that three.dev already records. Decides whether a business outcome is worth tracking and, if so, wires the code that reports it; three.dev creates the metric from the first report. Use when the user wants to start tracking conversions, bookings, resolutions, escalations, accepted suggestions, or another outcome of an LLM feature, or needs a metric wired for a live experiment. Not for reading which metrics exist or how they are performing, which is the list_quality_metrics tool and the three.dev app. Not for adding three.dev to a codebase or routing calls through the proxy; that is the three-dev-setup skill. Not for investigating failure modes or reading recorded conversations; that is the three-dev-failure-modes skill. Not for running or reading offline experiments; that is the three-dev-experiments skill.

Read SKILL.md at the source

Pinned to revision d19757064e92, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.