langsmith-fetch

Retrieve and analyze LangSmith execution traces to debug LangChain and LangGraph agents.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/nferrer-dev/claude-dotfiles --skill langsmith-fetch-nferrer-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/nferrer-dev/claude-dotfiles/tree/main/skills/langsmith-fetch
Command: npx skills add https://github.com/nferrer-dev/claude-dotfiles --skill langsmith-fetch-nferrer-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires langsmith-fetch.

What problem does it solve?

This skill resolves the difficulty of troubleshooting complex agentic workflows by providing direct access to execution traces, tool call logs, and memory operations within LangSmith.

Core Features & Use Cases

  • Trace Analysis: Retrieve and inspect specific execution traces to identify failure points or performance bottlenecks.
  • Error Categorization: Automatically aggregate and categorize errors to pinpoint recurring issues in agent reasoning or tool invocation.
  • Session Export: Capture full execution history into local directories for offline review or collaborative debugging.

Quick Start

Use the langsmith-fetch skill to retrieve the last five execution traces from your project to identify recent agent errors.

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 failures using execution traces?

Debug LangChain agent failures by retrieving execution traces from LangSmith to investigate tool call failures, memory state inconsistencies, and latency issues within complex reasoning chains.

What is the best way to find the cause of a LangGraph agent error?

Find the cause of a LangGraph agent error by retrieving and inspecting specific execution traces to pinpoint failure points and performance bottlenecks in the application.

How do I aggregate recurring errors in LangChain tool invocations?

Aggregate recurring errors in LangChain tool invocations by automatically categorizing them from execution traces to pinpoint issues in agent reasoning or tool invocation.

Can I export LangSmith execution history for offline debugging?

Export LangSmith execution history to capture full execution traces into local directories, enabling offline review and collaborative debugging of agent workflows.

Do I need a LangSmith API key to retrieve agent traces?

A valid LangSmith API key and project configuration are required to interface with the LangSmith platform and retrieve agent execution traces for debugging.