langsmith-fetch

Fetch and analyze LangSmith traces to diagnose agent behavior.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/huivrotiki/antigravity-code-workspace-copy --skill langsmith-fetch-huivrotiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/huivrotiki/antigravity-code-workspace-copy/tree/main/02-Skills/langsmith-fetch
Command: npx skills add https://github.com/huivrotiki/antigravity-code-workspace-copy --skill langsmith-fetch-huivrotiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. This skill helps you diagnose agent behavior, investigate errors, analyze tool calls, inspect memory operations, and evaluate performance by automatically fetching recent traces and analyzing execution patterns.

Core Features & Use Cases

  • Auto-fetch recent traces from LangSmith Studio and summarize agent activity, including tool usage, execution times, and token usage.
  • Deep-dive into specific traces to understand agent reasoning, tool calls, and failure points.
  • Export traces and metadata for reproducible debugging and team collaboration.
  • Cross-project comparison of traces to identify recurring patterns and bottlenecks.

Quick Start

Run a quick fetch of recent traces and review the summary to identify errors or performance anomalies.

Frequently Asked Questions about langsmith-fetch

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

FAQPage Schema
How do I debug LangChain agent errors using LangSmith traces?

Debug LangChain agent errors by fetching and analyzing LangSmith traces to diagnose agent behavior, investigate failure points, and inspect tool calls across workflows to pinpoint exactly where execution failed.

What is needed to fetch LangSmith traces from the terminal?

Fetching LangSmith traces requires the langsmith-fetch CLI to be installed, along with a configured API key and project, enabling you to pull recent execution data directly to your terminal.

Can I analyze LangGraph tool calls and memory usage from execution traces?

Yes, you can deep-dive into specific traces to understand agent reasoning, analyze tool calls, inspect memory operations, and evaluate performance by summarizing execution patterns and token usage.

Does this debugging approach work with LangSmith Studio workflows?

Yes, this approach applies to debugging agent errors and monitoring performance across LangSmith Studio and LangChain workflows, automatically fetching recent traces and summarizing agent activity.

What is the best way to compare LangSmith traces across different projects?

The best way to compare LangSmith traces across projects is to fetch recent execution data and perform cross-project comparison to identify recurring patterns, bottlenecks, and performance anomalies.