langsmith-trace

Instruments Python and TypeScript apps to capture and query LLM execution traces.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jxtngx/dgx-lab --skill langsmith-trace-jxtngx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langsmith-trace
Source: https://github.com/jxtngx/dgx-lab/tree/main/.cursor/skills/langsmith-trace
Command: npx skills add https://github.com/jxtngx/dgx-lab --skill langsmith-trace-jxtngx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of monitoring and debugging LLM-powered applications by providing a unified interface for tracing execution flows and analyzing performance metrics.

Core Features & Use Cases

  • Automated Tracing: Easily instrument Python and TypeScript applications to capture LLM calls, tool usage, and nested logic.
  • Trace Analysis: Query, filter, and export trace data to identify latency bottlenecks, cost drivers, and execution errors.
  • Use Case: When an agentic workflow fails, use this skill to inspect the full execution tree, identify the specific step where the model hallucinated or the tool call failed, and export the trace for regression testing.

Quick Start

Use the langsmith-trace skill to list the last 10 traces from your current project and export them to a local directory for analysis.

Frequently Asked Questions about langsmith-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is LLM application observability and how does tracing work?

LLM observability monitors application performance through trace instrumentation. It captures LLM calls and nested logic in Python or TypeScript environments, providing structured trace exports that facilitate performance analysis, cost tracking, and dataset generation.

Can I instrument TypeScript applications for LLM tracing?

Yes, TypeScript applications are supported for LLM tracing alongside Python. You can instrument your code to automatically capture execution flows, query the last 10 traces from your current project, and export them to a local directory for analysis.

How do I query and export trace data to analyze cost drivers?

To export traces for regression testing, query your project's trace data to locate the specific execution step where an error occurred. You can then export the filtered traces to a local directory, generating datasets that capture the failure for future testing.

What is the best way to monitor LLM application performance and latency?

The best way to monitor LLM application performance is by instrumenting your code to capture execution flows automatically. This provides a unified interface to analyze performance metrics, track costs, and identify latency bottlenecks across complex agentic workflows.

Do I need any specific dependencies to enable LLM trace instrumentation?

No specific dependencies are required to enable LLM trace instrumentation. The skill provides comprehensive observability for Python and TypeScript applications without external components, allowing you to capture LLM calls and query trace data via CLI immediately.