langsmith-fetch

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./langsmith-fetch/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with copy-paste-ready commands and clear workflow sequences, but it is a long monolithic file with redundant sections and no progressive disclosure to reference files. Batch workflows also lack explicit validation checkpoints.

Suggestions

Add explicit verification steps to batch/export workflows (e.g. after Workflow 3, verify the exported file count matches before reporting success) to lift workflow clarity above the destructive/batch cap of 3.

Move Advanced Features, Troubleshooting, and the long mock response-format examples into one-level-deep reference files (e.g. TROUBLESHOOTING.md, EXAMPLES.md) linked from SKILL.md to improve progressive disclosure.

Remove redundant sections — the Quick Reference, Output Format Guide, and Notes for Claude largely restate commands and guidance already shown in the workflows — to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Commands are lean and actionable, but the body carries several padded sections — long mock response-format examples in each workflow, a duplicated Quick Reference that restates earlier commands, an Output Format Guide that repeats flags shown elsewhere, and a 'Notes for Claude' section restating obvious guidance.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (e.g. 'langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty') covering the common debugging cases with concrete flags and examples.	5 / 5
Workflow Clarity	Workflows have clear 'When user asks → Execute → Analyze and report' sequences, but batch operations like Workflow 3 (exporting 50 traces / 20 threads) and Workflow 4 lack explicit validation/verification checkpoints, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Good section headers provide structure, but with no bundle files the entire ~480-line body is inlined in SKILL.md — content like Advanced Features, Troubleshooting, and detailed mock examples could live in one-level-deep reference files but none are signaled.	3 / 5
	Total	14 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill does and when to use it, with concrete trigger phrases and a well-defined niche. Trigger terms are slightly abstract but generally natural.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fetching execution traces', 'debugging agent behavior', 'investigating errors', 'analyzing tool calls', 'checking memory operations', 'examining agent performance' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (debug agents by fetching execution traces from LangSmith Studio) and 'when' ('Use when debugging agent behavior, investigating errors, analyzing tool calls...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('debugging agent behavior', 'investigating errors', 'checking memory operations') but the terms lean technical/abstract and lack common synonym variations, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — LangChain/LangGraph agent debugging via LangSmith traces — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: langsmith-fetch/SKILL.md
Commit: be2a406

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.