Use for any question or task about tracing, monitoring or debugging LLM calls in production, including having no record of what the model saw for a bad answer, or turning production traces into eval datasets. Adds Langfuse with @observe or startActiveObservation, records metadata, cost and latency, scores traces and manages prompts as code.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Langfuse datasets are collections of (input, expected_output) items.
Build them from three sources:
synthetic-pii-generator.Shipping traces from production into a dataset, then replaying them, is
the core offline-regression workflow: item.run() links each replay
back to the dataset so the Langfuse UI can diff the run against a
baseline. See langfuse.com/docs/datasets
for the current API signature.
After running a dataset, open the Langfuse UI → Datasets → select your
dataset. Each item run should appear under the Runs tab linked to its
trace. If runs are missing, confirm dataset_id is correct and that
item.run() did not raise an exception.