Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
langchain-ai avatar

Langsmith Fetch

  • 47 installs
  • 2 repo stars
  • Updated February 18, 2026
  • langchain-ai/lca-skills

Helps with ai & agent building tasks.

About

langsmith-fetch is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • langsmith-fetch
  • AI & Agent Building
  • AI-coding skill

Langsmith Fetch by the numbers

  • 47 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #7,551 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/langchain-ai/lca-skills --skill langsmith-fetch

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs47
repo stars2
Last updatedFebruary 18, 2026
Repositorylangchain-ai/lca-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Fetching LangSmith Traces

Requires langsmith-fetch in project dependencies and LANGSMITH_API_KEY in a .env file.

Setup

First, find the .env file containing LANGSMITH_API_KEY:

find . -name ".env" -type f 2>/dev/null | head -5

Commands

Use --env-file <path-to-.env> with all commands:

# Fetch recent traces (uses LANGSMITH_PROJECT from .env, or specify --project-uuid)
uv run --env-file <path> langsmith-fetch traces ./traces --limit 10
uv run --env-file <path> langsmith-fetch traces ./traces --project-uuid <uuid> --limit 10

# Fetch single trace by ID
uv run --env-file <path> langsmith-fetch trace <trace-id>

# Include metadata (timing, tokens, costs)
uv run --env-file <path> langsmith-fetch trace <trace-id> --include-metadata

Output Formats

  • --format pretty - Human-readable (default)
  • --format json - Pretty-printed JSON
  • --format raw - Compact JSON for piping

Troubleshooting Workflow

1. Find .env: find . -name ".env" -type f 2>/dev/null 2. Fetch recent traces: uv run --env-file <path> langsmith-fetch traces ./debug --limit 10 3. Find relevant trace in saved JSON files 4. Check: What tools were called? What did they return? Was it correct/expected?

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.