langsmith-fetch

Fetch LangSmith traces to debug LangChain and LangGraph agents.

27|2|Updated Dec 24, 2025

Search Tags:#performance #debugging #langchain #agent #memory #langsmith #trace-analysis

Ready to run

npx skills add https://github.com/OthmanAdi/langsmith-fetch-skill --skill langsmith-fetch-othmanadi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/OthmanAdi/langsmith-fetch-skill/tree/main
Command: npx skills add https://github.com/OthmanAdi/langsmith-fetch-skill --skill langsmith-fetch-othmanadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug LangChain and LangGraph agents by fetching execution traces directly from LangSmith Studio in your terminal, enabling rapid diagnosis of failures, performance issues, and memory problems.

Core Features & Use Cases

Automatic Debugging: Claude fetches and analyzes traces autonomously
Error Detection: Identifies failures and root causes
Performance Analysis: Tracks execution time and token usage
Memory Operations: Checks LTM recall/store operations
Tool Call Analysis: Reviews which tools were called and why
Session Export: Saves debugging sessions for later review
Multi-Agent Support: Debugs orchestration decisions
Use Case: When an agent misbehaves, ask Claude to fetch recent traces and provide actionable insights.

Quick Start

Install the langsmith-fetch CLI and configure LANGSMITH_API_KEY and LANGSMITH_PROJECT to begin debugging.

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?▼

Debugging LangChain agents involves fetching LangSmith traces to detect errors, analyze tool calls, and investigate memory operations. This skill retrieves execution traces to identify root causes and diagnose agent misbehavior.

What is the best way to analyze LangGraph agent performance and token usage?▼

Analyzing LangGraph agent performance requires fetching LangSmith traces to track execution time and token consumption. This skill extracts trace data to evaluate agent efficiency and pinpoint performance bottlenecks across runs.

Do I need a LangSmith API key to fetch execution traces for debugging?▼

Yes, you need a LangSmith API key and a configured LangSmith project environment variable to fetch execution traces. You must also install the langsmith-fetch CLI before retrieving any debugging data.

Can I review multi-agent orchestration decisions and LTM memory operations from LangSmith?▼

Yes, you can review multi-agent orchestration decisions and long-term memory operations by fetching LangSmith traces. This skill examines LTM recall and store operations alongside orchestration logic to debug complex agent workflows.

How do I export LangSmith debugging sessions for later review?▼

You can export LangSmith debugging sessions for later review by fetching and analyzing traces within your terminal. This skill supports saving debugging sessions to document agent failures and performance issues.