CtrlK
BlogDocsLog inGet started
Tessl Logo

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

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A well-structured, highly actionable skill with executable code and clear sequencing. The main gaps are missing validation checkpoints for batch/destructive operations and inline content that could be moved to bundle files.

Suggestions

Add an explicit validation/verification checkpoint to the batch and destructive workflows (e.g., verify each queued request succeeded before proceeding, or a retry-then-validate feedback loop) to raise workflow clarity.

Move the per-plan/per-operation rate-limit reference tables and one or more of the larger code examples into reference bundle files, linking to them from the overview, to improve progressive disclosure and reduce the inline token budget.

Trim non-essential lines from the code blocks (e.g., console.log debugging output and the verbose DailyBudgetTracker class) so every remaining token earns its place.

DimensionReasoningScore

Conciseness

The body is mostly efficient — reference tables and executable code rather than concept explanations — but four full code blocks plus a verbose DailyBudgetTracker class and console.log debug lines carry more than the lean minimum and could be tightened.

2 / 3

Actionability

Provides fully executable TypeScript with real imports, env var usage, and concrete values (intervals, delays, jitter caps); examples are copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly sequenced (detect → backoff → queue → budget), but batch operations (batchFetchTranscripts) and destructive ops (deleteTranscript) lack explicit validation/verification checkpoints, which caps this at 2 per the rubric.

2 / 3

Progressive Disclosure

Sections are well-organized, but ~190 lines of reference tables plus four large code blocks are inline content that could be split into separate files, and the only internal pointer (fireflies-security-basics) is not a real bundle file in this skill.

2 / 3

Total

9

/

12

Passed

Description

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.

A strong, specific description that clearly states capabilities, provides natural trigger phrases, and answers both what and when. No substantive weaknesses to address.

DimensionReasoningScore

Specificity

Names three concrete actions — "rate limiting, backoff, and request queuing" — tied to a specific API, matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly states what it does (rate limiting/backoff/queuing for Fireflies.ai) and when to use it ("Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput") plus explicit triggers.

3 / 3

Trigger Term Quality

Provides five natural trigger phrases ("fireflies rate limit", "fireflies throttling", "fireflies 429", "fireflies retry", "fireflies backoff") a user would plausibly say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Fireflies.ai rate-limiting niche is tightly scoped with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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