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".
67
82%
Does it follow best practices?
Impact
—
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 trigger guidance with a 'Use when' clause, and lists natural trigger terms users would actually search for. It uses proper third-person voice and is concise without being vague. The explicit mention of '429 error' is a particularly good touch for catching real-world user queries.
| 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' (explicit 'Use when' clause covering API rate limits, request throughput, batch processing) with explicit trigger terms listed separately. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'langchain rate limit', 'langchain throttling', 'langchain backoff', 'langchain retry', 'API quota', and '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 limiting/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 skill provides highly actionable, executable code examples covering multiple rate-limiting strategies in both TypeScript and Python, which is its strongest quality. However, it's somewhat verbose with time-sensitive provider rate limit tables and lengthy custom implementations that could be offloaded to bundle files. The workflow clarity would benefit from explicit decision criteria for choosing between strategies and validation steps for batch operations.
Suggestions
Add a brief decision matrix or flowchart at the top (e.g., 'Use Strategy 1 for simple calls, Strategy 2 for batch < 100 items, Strategy 4 for fine-grained control') to improve workflow clarity.
Move the provider rate limits table to a separate reference file or remove it entirely since these values change frequently and Claude can look them up.
Extract the custom TokenBucketLimiter and Semaphore implementations into bundle files, keeping only usage examples inline to improve progressive disclosure and conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The provider rate limits table with specific 2026 numbers is time-sensitive information that adds bulk and will become stale. The Python equivalent section adds value but the overall content is somewhat long for what could be more tightly organized. The error handling table and resources are useful but the skill could be tighter. | 2 / 3 |
Actionability | All five strategies include fully executable, copy-paste ready TypeScript code with clear comments. The Python equivalent section provides concrete working code as well. The error handling table maps specific errors to specific fixes. | 3 / 3 |
Workflow Clarity | The strategies are clearly presented as escalating options (simplest to most complex), but there's no explicit guidance on when to choose which strategy, no validation/verification steps after implementing rate limiting, and no feedback loop for confirming the rate limiting is working correctly. For batch operations (Strategies 2, 4, 5), there's no mention of verifying results or handling partial failures beyond a single table row. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression of strategies, but it's a monolithic file with no bundle files to offload detailed content. The custom rate limiter and semaphore implementations could be in separate referenced files, keeping the main skill leaner. The reference to 'langchain-security-basics' at the end is a nice touch but the inline content is heavy. | 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
a04d1a2
- 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.