langsmith-fetch

Fetch LangSmith execution traces to diagnose agent failures and behavior.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/ai-wes/glassbox-operator --skill langsmith-fetch-ai-wes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/ai-wes/glassbox-operator/tree/main/awesome-claude-skills/langsmith-fetch
Command: npx skills add https://github.com/ai-wes/glassbox-operator --skill langsmith-fetch-ai-wes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly inspect LangSmith traces so you can understand why a LangChain or LangGraph agent behaved unexpectedly, failed, or slowed down.

Core Features & Use Cases

  • Recent trace review: Pull the latest traces to see errors, durations, token usage, and tool calls.
  • Deep trace analysis: Inspect a specific trace to reconstruct the agent's goal, execution flow, and root cause.
  • Debugging workflows: Use it for missing memory, wrong tool selection, performance issues, and exportable debug sessions.

Quick Start

Ask me to fetch the latest LangSmith traces for your agent and summarize any errors, tool calls, and performance issues.

Frequently Asked Questions about langsmith-fetch

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

FAQPage Schema
How do I fetch LangSmith traces to debug a LangChain agent?

To fetch LangSmith traces for debugging a LangChain agent, you need the langsmith-fetch CLI, valid API credentials, and a configured project name to pull and inspect execution data.

What is the best way to analyze LangGraph agent failures using execution traces?

Analyzing LangGraph agent failures using execution traces involves inspecting recent trace records to detect errors, review tool calls, check token usage, and identify performance bottlenecks.

Can I use this to inspect specific tool calls within a LangChain trace?

Yes, you can inspect specific tool calls within a LangChain trace by pulling deep trace data, which reconstructs the agent's execution flow and highlights individual tool selections and memory usage.

Do I need API credentials to review recent LangSmith trace data?

Yes, you need valid LangSmith API credentials, the langsmith-fetch CLI installed, and a configured project name to securely access and review recent trace data for your agents.

What output formats are supported when extracting LangSmith traces for profiling?

When extracting LangSmith traces for performance profiling, the system supports pretty, JSON, and raw output formats to accommodate different debugging and analysis workflows.

Why does my LangGraph agent behave unexpectedly during execution?

Unexpected LangGraph agent behavior can be diagnosed by pulling the latest LangSmith traces to investigate execution flow, analyze memory issues, and pinpoint the root cause of failures.