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
Pending
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 request management), provides explicit 'Use when' guidance, and includes well-chosen trigger phrases. It follows third-person voice correctly and is concise without being vague. The only minor improvement would be mentioning file types or code patterns if applicable, but for this domain the description is comprehensive.
| 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 request 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. The 'fireflies' prefix on all trigger terms makes it very unlikely to conflict with generic rate limiting or other API skills. | 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 spectrum of Fireflies.ai rate limiting concerns. The rate limit reference tables and error handling decision matrix add significant value. The main weakness is that the content is somewhat long for a SKILL.md overview, with the full DailyBudgetTracker implementation potentially better suited to a referenced file.
Suggestions
Consider moving the DailyBudgetTracker implementation to a separate reference file and keeping only a brief description with a link in the main skill.
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 somewhat verbose for what it accomplishes. The rate limit reference tables earn their place though. | 2 / 3 |
Actionability | Fully executable TypeScript code with concrete implementations for rate limit detection, exponential backoff with jitter, request queuing via p-queue, and daily budget tracking. Code is copy-paste ready with specific API endpoints, headers, and error handling patterns. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence from detection to queuing to budget tracking. The error handling table serves as a decision matrix for different scenarios. Each step builds on the previous one, and the retry logic includes explicit feedback loops (detect rate limit → backoff → retry → throw if exhausted). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference to an external skill (fireflies-security-basics) and external docs. However, the inline code is quite lengthy (~130 lines of code) and some components like the DailyBudgetTracker could be referenced from a separate file rather than fully inlined. | 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
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.