Name: langsmith-fetch
Author: langchain-ai

Imported from langchain-ai/lca-skills (skills/langsmith-fetch/SKILL.md) via skills.sh. Install upstream with npx skills add langchain-ai/lca-skills --skill langsmith-fetch. Copyright stays with the author.

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

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

Install langsmith-fetch and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "langchain-ai-lca-skills-langsmith-fetch", "kind": "skill", "name": "langsmith-fetch", "description": "Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls.", "publisher": "langchain-ai", "version": "1.0.0", "capabilities": { "domains": [ "observability", "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/langchain-ai/lca-skills", "path": "skills/langsmith-fetch/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/langchain-ai/lca-skills/langsmith-fetch", "key": "langchain-ai/lca-skills/skills/langsmith-fetch/SKILL.md" } }, "instructions": "# Fetching LangSmith Traces\n\nRequires `langsmith-fetch` in project dependencies and `LANGSMITH_API_KEY` in a `.env` file.\n\n## Setup\n\nFirst, find the `.env` file containing `LANGSMITH_API_KEY`:\n```bash\nfind . -name \".env\" -type f 2>/dev/null | head -5\n```\n\n## Commands\n\nUse `--env-file <path-to-.env>` with all commands:\n\n```bash\n# Fetch recent traces (uses LANGSMITH_PROJECT from .env, or specify --project-uuid)\nuv run --env-file <path> langsmith-fetch traces ./traces --limit 10\nuv run --env-file <path> langsmith-fetch traces ./traces --project-uuid <uuid> --limit 10\n\n# Fetch single trace by ID\nu", "cost": { "context_tokens": 309 } }

langsmith-fetch

About

Fetching LangSmith Traces

Setup

Commands

Output Formats

Troubleshooting Workflow

Install langsmith-fetch and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews