fireflies-rate-limits
Implement Fireflies.ai rate limiting, backoff, and request queuing. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Fireflies.ai. Trigger with phrases like "fireflies rate limit", "fireflies throttling", "fireflies 429", "fireflies retry", "fireflies backoff".
89
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 strong skill description that clearly defines its scope (Fireflies.ai rate limiting and retry logic), provides explicit 'Use when' guidance, and includes well-chosen trigger phrases. It uses proper third-person voice and is concise without being vague. The description would allow Claude to confidently select this skill from a large pool of available skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rate limiting', 'backoff', 'request queuing'. These are distinct, well-defined technical capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement rate limiting, backoff, and request queuing for Fireflies.ai) and 'when' (explicit 'Use when' clause covering rate limit errors, retry logic, and API throughput optimization, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'fireflies rate limit', 'fireflies throttling', 'fireflies 429', 'fireflies retry', 'fireflies backoff'. These are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Fireflies.ai' as the target API and rate-limiting/backoff as the domain. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with executable TypeScript code covering the full rate-limiting workflow for Fireflies.ai. The rate limit reference tables and error handling summary table are particularly valuable. The main weakness is length—the skill could be more concise by trimming the DailyBudgetTracker or moving it to a supplementary file, and the 'Output' section adds little value.
Suggestions
Consider moving the DailyBudgetTracker class into a separate bundle file and referencing it, to keep the main SKILL.md focused on the core retry/queue pattern.
Remove the 'Output' section as it merely restates what the code examples already demonstrate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with useful reference tables and executable code, but includes some unnecessary elements like the 'Output' section that restates what the code already demonstrates, and the DailyBudgetTracker class is quite verbose for what it accomplishes. The rate limit reference tables are valuable and earn their tokens. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with concrete implementations—rate limit detection, exponential backoff with jitter, request queuing with p-queue, and daily budget tracking. The code is copy-paste ready with specific API endpoints, headers, and error handling patterns. | 3 / 3 |
Workflow Clarity | The four steps are clearly sequenced from detection → retry → queuing → budget tracking, building logically on each other. The error handling table provides explicit detection criteria and corresponding actions. The retry loop includes a clear feedback loop (detect rate limit → backoff → retry → throw if exhausted). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference to 'fireflies-security-basics' for next steps, but the skill is quite long (~150 lines of code) and could benefit from splitting the DailyBudgetTracker and batch operations into separate referenced files. No bundle files exist to offload detail into. | 2 / 3 |
Total | 10 / 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.