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.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill langsmith-fetchOverall
score
71%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly identifies the specific technology stack (LangChain/LangGraph/LangSmith), lists concrete debugging actions, includes an explicit 'Use when...' clause with multiple trigger scenarios, and maintains a distinct niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'fetching execution traces', 'debugging agent behavior', 'investigating errors', 'analyzing tool calls', 'checking memory operations', 'examining agent performance', and 'analyzes execution patterns'. | 3 / 3 |
Completeness | Clearly answers both what ('Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio') and when ('Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance'). Includes explicit 'Use when...' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'LangChain', 'LangGraph', 'agents', 'LangSmith', 'debugging', 'errors', 'tool calls', 'memory operations', 'traces', 'performance'. These are terms developers naturally use when working with these frameworks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (LangChain, LangGraph, LangSmith Studio) and clear niche (agent debugging via traces). Unlikely to conflict with general debugging skills or other document/code skills due to the specific framework focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable commands with clear executable examples, but is severely bloated with unnecessary verbosity and redundant content. The lack of progressive disclosure makes this a 450+ line monolith when it could be a concise overview with references to detailed guides. Workflow clarity is adequate but missing validation steps for operations like exports.
Suggestions
Reduce content by 60-70% by removing redundant explanations, excessive example outputs, and the 'Notes for Claude' section that states obvious things
Split into multiple files: keep SKILL.md as a quick reference (~50 lines) with links to WORKFLOWS.md, TROUBLESHOOTING.md, and USE-CASES.md
Add validation steps to workflows, e.g., verify export succeeded with `ls -la $SESSION_DIR` before reporting success
Remove the 'When to Use This Skill' emoji list - Claude can infer activation contexts from the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~450 lines with significant redundancy. Explains obvious concepts (what traces are, what errors mean), includes excessive example output formatting, and repeats similar information across workflows. The 'Notes for Claude' section tells Claude things it already knows. | 1 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific flags and options. Commands are copy-paste ready with clear examples like `langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty`. | 3 / 3 |
Workflow Clarity | Workflows are clearly numbered and sequenced, but lack explicit validation checkpoints. For example, Workflow 3 (Export) doesn't verify the export succeeded before reporting success. No feedback loops for error recovery in the workflows themselves. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. Content that should be in separate files (troubleshooting, advanced features, use cases) is all in one document. No references to external files for detailed content despite the document being extremely long. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- Reviewed
Table of Contents
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.