Evaluate trace
Skill Goodeye-Labs/truesight-mcp-skills/skills/evaluate-trace
Agent skills for the Truesight MCP. Step-by-step workflow playbooks for scoring inputs, building live evaluations, error analysis, and the review loop. Works with Claude Code, Cursor, ChatGPT, VS Code, Windsurf, and any client that supports the agent skills standard.
npx -y skills add Goodeye-Labs/truesight-mcp-skills --skill evaluate-traceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Evaluate one or more traces against an existing Truesight live evaluation. Use when a deployed live evaluation already exists and the user wants run outputs with optional handoff to review and promotion.
SKILL.md
2.4 KB, as published. Nobody here has run it
Evaluate Trace
Use this skill when the user wants to evaluate traces with an existing live evaluation endpoint.
Interactive Q&A protocol (mandatory)
<HARD-GATE> BEFORE the first scoping question, search for a structured question tool (e.g., `AskUserQuestion` or similar interactive widget) and load it. Use that tool for EVERY scoping question. Fall back to plain-text lettered options ONLY if no such tool exists in the environment. </HARD-GATE>If context does not make scope clear, ask one question at a time using the structured question tool (loaded per the HARD-GATE above).
Example question structure:
Do you want to evaluate one trace or a batch?
A) One trace now
B) Small batch (up to 25)
C) Full batch loop
Rules:
- Ask exactly one clarifying question per message.
- Use the structured question tool for every question. Structure each with a short header, 2-4 options with labels and descriptions, and place the recommended option first. Do not add "(Recommended)" or similar annotations to option labels.
- Ask a single follow-up if needed, then proceed.
Workflow
- Identify target live evaluation:
- If live evaluation id is unknown, call
list_live_evaluations. - Select
public_idand verify requiredinput_columns.
- If live evaluation id is unknown, call
- Prepare inputs:
- Ensure
inputskeys exactly matchinput_columns. - Include
media_urlfor multimodal evaluations when needed.
- Ensure
- Execute evaluation:
- Use the
run_evaltool withlive_evaluation_idandinputsfor each trace.
- Use the
- Return useful outputs:
run_id- per-judgment scores/outcomes
- brief interpretation for next action
- Optional handoff:
- If human judgment is needed, route to
review-and-promote-traces.
- If human judgment is needed, route to
Batch mode guidance
- Use deterministic trace ordering and log
run_idfor each input. - Apply retries with stable idempotency context in caller logic if needed.
- Summarize failures by category or threshold, then propose review handoff.
Scopes reference
list_live_evaluationsrequireslive-evaluations:readrun_evalrequireslive-evaluations:execute
If a scope error occurs, ask the user to create an API key with the missing scope in Truesight Settings.