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".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise with clear sequencing and real feedback loops for rate-limited batch operations. Its main weakness is progressive disclosure: the skill is fairly long yet keeps all reference tables and code inline rather than splitting detailed material into bundled reference files.

Suggestions

Move the per-plan and per-operation rate-limit tables into a references/ file (e.g. RATE_LIMITS.md) and link to it from a short overview, keeping SKILL.md as a lean entry point.

Extract the longer code implementations (the retry client, queue, and budget tracker) into a scripts/ file and show only concise usage snippets inline, signaling the full source via a one-level reference.

Verify the 'fireflies-security-basics' reference in Next Steps points to an existing skill or bundle path so the cross-reference is not a dead link.

Dimension	Reasoning	Score
Conciseness	The body is lean — mostly rate-limit tables and executable TypeScript with minimal prose — and assumes Claude's competence without explaining what rate limiting or GraphQL are. The inline comments are functional, not filler.	3 / 3
Actionability	All four steps provide complete, copy-paste-ready TypeScript with real endpoints, types, and imports; the queue and budget-tracker implementations are fully executable rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1–4 are clearly sequenced, and the retry path (detect via isRateLimited → backoff → retry) plus the DailyBudgetTracker.canRequest() pre-check form explicit feedback loops for the batch/rate-limited operations the scoring notes call out.	3 / 3
Progressive Disclosure	Sections are well organized, but at ~190 lines everything — the rate-limit reference tables and all four full code implementations — lives inline in SKILL.md with no local one-level reference files to split it out, matching the anchor where content that could be separate is kept inline.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities, use conditions, and natural trigger phrases with a distinct, conflict-resistant niche. The only blemish is cosmetic: the folded YAML scalar injects blank lines between every line, slightly marring readability without affecting content quality.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'rate limiting, backoff, and request queuing' — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	It explicitly answers both what ('Implement Fireflies.ai rate limiting, backoff, and request queuing') and when ('Use when handling rate limit errors, implementing retry logic...') with explicit trigger guidance.	3 / 3
Trigger Term Quality	It supplies natural trigger phrases a user would actually say — 'fireflies rate limit', 'fireflies throttling', 'fireflies 429', 'fireflies retry', 'fireflies backoff' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Fireflies.ai-specific niche and 'fireflies'-prefixed triggers make it clearly distinguishable and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/fireflies-pack/skills/fireflies-rate-limits/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.