BC 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.
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio.
As a process C 63/100 · Has gaps — weak spots: when it triggers, consistency, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 4
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-shell-rcREADME.md:224Writes to a shell startup fileecho 'export LANGSMITH_API_KEY="your_key"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcREADME.md:225Writes to a shell startup fileecho 'export LANGSMITH_PROJECT="your_project"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:393Writes to a shell startup fileecho 'export LANGSMITH_API_KEY="your_key"' >> ~/.bashrc
-
medium Dangerous commands
cmd-shell-rcSKILL.md:394Writes to a shell startup fileecho 'export LANGSMITH_PROJECT="your_project"' >> ~/.bashrc
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (langsmith-fetch) differs from the folder (langsmith-fetch-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 70 steps
- 100Execution cost. Instruction body is 2608 tokens
- 100Running it twice. Mutating operations check current state
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -222 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 336: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (27 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.