langchain-rate-limits
Implement LangChain rate limiting, retry strategies, and backoff. Use when handling API rate limits, controlling request throughput, or implementing concurrency-safe batch processing. Trigger: "langchain rate limit", "langchain throttling", "langchain backoff", "langchain retry", "API quota", "429 error".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly defines its scope (LangChain rate limiting and retry strategies), provides explicit 'Use when' guidance, and includes a comprehensive set of natural trigger terms. It uses proper third-person voice and is concise without being vague. The description effectively distinguishes itself from both general LangChain skills and general rate-limiting skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rate limiting', 'retry strategies', 'backoff', 'controlling request throughput', and 'concurrency-safe batch processing'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement rate limiting, retry strategies, backoff) and 'when' (handling API rate limits, controlling request throughput, batch processing) with an explicit 'Use when' clause and explicit trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'langchain rate limit', 'langchain throttling', 'langchain backoff', 'langchain retry', 'API quota', '429 error'. These are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: LangChain-specific rate limiting and retry logic. The combination of 'LangChain' + 'rate limit/retry/backoff' creates a very specific domain unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering multiple rate limiting strategies in both TypeScript and Python. Its main weaknesses are the inclusion of time-sensitive provider rate limit data, the lack of explicit decision-making guidance for choosing between strategies, and the absence of validation/monitoring steps to confirm rate limiting is working correctly. The content could benefit from splitting advanced implementations into separate files.
Suggestions
Add a brief decision tree or guidance for when to use each strategy (e.g., 'Start with Strategy 1; if processing >50 items, use Strategy 2; if multi-provider, use Strategy 3').
Move the custom TokenBucketLimiter and Semaphore implementations to a separate ADVANCED.md file, keeping SKILL.md as a concise overview with the built-in approaches.
Add validation/monitoring guidance, such as how to log retry attempts or verify that concurrency limits are being respected during batch processing.
Remove or move the provider rate limits table to a separate reference file, as these values are time-sensitive and tier-dependent.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The provider rate limits table contains time-sensitive data that may become stale and adds bulk. The content is generally efficient but includes some unnecessary elements like the 'Next Steps' section and the rate limits table that Claude could look up. The five strategies are well-presented but the semaphore implementation is verbose when LangChain's built-in batch already handles this. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript and Python with proper imports, concrete configuration values, and copy-paste ready patterns. Each strategy includes complete, runnable code with clear parameter explanations inline. | 3 / 3 |
Workflow Clarity | The strategies are clearly presented as escalating options, and the error handling table provides good troubleshooting guidance. However, there's no explicit workflow for choosing between strategies or validation steps (e.g., how to verify rate limiting is working, how to monitor for 429s during batch processing, or feedback loops for adjusting concurrency). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression from simple to complex strategies. However, the custom rate limiter and semaphore implementations could be split into a separate advanced file, and the inline content is quite long (~180 lines) for a SKILL.md overview. External references are limited to provider docs rather than companion skill files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.