langchain-common-errors
Diagnose and fix common LangChain errors and exceptions. Use when encountering LangChain errors, debugging failures, or troubleshooting integration issues. Trigger with phrases like "langchain error", "langchain exception", "debug langchain", "langchain not working", "langchain troubleshoot".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill langchain-common-errors88
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
89%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-structured skill description with strong completeness and excellent trigger term coverage. The explicit 'Use when' and 'Trigger with phrases' sections make it highly actionable for skill selection. The main weakness is that the capabilities could be more specific about what types of LangChain errors it handles.
Suggestions
Add specific error types or scenarios handled, such as 'resolve import errors, fix chain configuration issues, debug memory/callback problems, troubleshoot API integration failures'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (LangChain errors) and general actions (diagnose, fix, debug, troubleshoot), but doesn't list specific concrete actions like 'resolve import errors', 'fix chain configuration issues', or 'debug memory problems'. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix common LangChain errors and exceptions') and when ('Use when encountering LangChain errors, debugging failures, or troubleshooting integration issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'langchain error', 'langchain exception', 'debug langchain', 'langchain not working', 'langchain troubleshoot'. These are realistic phrases users would type when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on LangChain errors and debugging. The explicit LangChain-specific triggers make it unlikely to conflict with general Python debugging or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality error reference skill that excels at providing concrete, actionable solutions for common LangChain errors. The content is appropriately concise and well-organized. The main weakness is the lack of a systematic debugging workflow that guides users through a diagnostic process with validation steps.
Suggestions
Add a 'Diagnostic Workflow' section at the top with a numbered sequence: 1. Check error type, 2. Verify environment/keys, 3. Check versions, 4. Enable debug mode, 5. Trace with LangSmith - with explicit validation at each step
Include a brief troubleshooting decision tree or flowchart description to help systematically narrow down error categories before diving into specific solutions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting error messages directly with minimal explanation. It assumes Claude knows what API keys, imports, and rate limiting are, focusing only on the specific solutions. | 3 / 3 |
Actionability | Every error includes executable, copy-paste ready code solutions. Commands are specific (pip install langchain-openai), and code examples are complete with proper imports and context. | 3 / 3 |
Workflow Clarity | While individual error solutions are clear, there's no explicit debugging workflow or validation sequence. The 'Debugging Tips' section lists tools but doesn't provide a systematic troubleshooting process with checkpoints. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Authentication, Import, Rate Limiting, etc.). External resources are linked at the end, and the structure allows quick navigation to specific error types. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 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.