langsmith-fetch

Fetch and analyze LangSmith Studio execution traces for LangChain and LangGraph agents.

145|36|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill langsmith-fetch-w95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/w95/awesome-claude-corporate-skills/tree/main/08-it-engineering/langsmith-fetch
Command: npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill langsmith-fetch-w95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the debugging of LangChain and LangGraph agents by directly fetching and analyzing execution traces from LangSmith Studio, allowing for quick identification and resolution of agent behavior issues.

Core Features & Use Cases

  • Fetch Recent Traces: Automatically retrieve recent agent execution logs.
  • Analyze Errors & Performance: Identify failures, execution times, and token usage.
  • Deep Dive Specific Traces: Investigate individual trace details for root cause analysis.
  • Export Debug Sessions: Save traces and threads for offline review and sharing.
  • Use Case: When an agent behaves unexpectedly, use this Skill to quickly pull the last 5 traces, identify any errors, and pinpoint the exact tool call or reasoning step that led to the issue.

Quick Start

Debug your agent by fetching the last 5 traces from LangSmith.

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 agents using LangSmith traces?

Debug LangChain agents by fetching recent execution traces from LangSmith Studio to analyze agent behavior, identify failures, and review tool calls or memory operations. Retrieve logs to pinpoint exact reasoning steps causing unexpected behavior.

How do I investigate a specific LangGraph agent error?

Investigate specific LangGraph errors by deep diving into individual execution traces. Fetch the relevant trace from LangSmith Studio to perform root cause analysis on the exact tool call, memory operation, or reasoning step that triggered the failure.

Do I need a LangSmith API key to fetch agent execution logs?

Yes, fetching agent execution logs requires the `langsmith-fetch` CLI configured with a valid LangSmith API key and project environment variables. These credentials allow the Skill to securely retrieve and analyze your execution traces.

What is the best way to analyze token usage and execution times for LangChain agents?

Analyze token usage and execution times by fetching recent traces from LangSmith Studio. This Skill assesses performance metrics, allowing you to review agent execution logs and identify performance bottlenecks in tool calls and reasoning steps.

Can I export LangSmith debug sessions for offline review?

Yes, you can export debug sessions by saving fetched traces and threads from LangSmith Studio. This allows you to store execution logs locally for offline review, root cause analysis, and sharing with your team.