gamma-rate-limits

Understand and manage Gamma API rate limits effectively. Use when hitting rate limits, optimizing API usage, or implementing request queuing systems. Trigger with phrases like "gamma rate limit", "gamma quota", "gamma 429", "gamma throttle", "gamma request limits".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 with executable TypeScript examples, but it loses points for token-wasting explanations of basics, missing validation checkpoints in the batch-queue workflow, and a monolithic single-file structure with no progressive disclosure references.

Suggestions

Remove redundant inline comments and prerequisites that explain concepts Claude already knows (e.g. "# 1000: 1 second in ms", "# HTTP 429 Too Many Requests", "Understanding of HTTP headers", "Basic queuing concepts") to tighten token efficiency.

Add explicit validation/verification checkpoints to the workflow, such as checking remaining quota before each call and a validate→retry loop around the RateLimitedQueue, so the batch operation has a clear feedback loop.

Consider moving the full withBackoff and RateLimitedQueue implementations into a scripts/ or references/ file with a concise overview and one-level-deep links in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but repeated comments like "# 1000: 1 second in ms", "# 60000: 1 minute in ms", and "# HTTP 429 Too Many Requests", plus prerequisites such as "Understanding of HTTP headers" and "Basic queuing concepts", explain concepts Claude already knows and could be trimmed.	2 / 3
Actionability	Steps 1–4 provide complete, copy-paste-ready TypeScript (withBackoff, RateLimitedQueue, getRateLimitStatus) plus a concrete error-handling strategy table, all executable rather than pseudocode.	3 / 3
Workflow Clarity	Steps are clearly sequenced (check headers → backoff → queue → monitor), but the batch queue workflow has no explicit validate→fix→retry checkpoints, and the scoring note caps workflow_clarity at 2 for batch operations missing feedback loops.	2 / 3
Progressive Disclosure	Sections are well organized, but the skill is a single monolithic file over 50 lines with no bundle files or one-level-deep references, so content that could be split (full class/queue implementations) is inline and the simple-skill exception does not apply.	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.

The description is strong: it states a concrete capability, gives an explicit Use-when clause, and lists natural Gamma-specific trigger phrases in third-person/infinitive voice. No dimension is weak enough to warrant suggestions.

Dimension	Reasoning	Score
Specificity	The Use-when clause lists three concrete activities ("hitting rate limits, optimizing API usage, or implementing request queuing systems") alongside "Understand and manage Gamma API rate limits", matching the multiple-specific-actions anchor; the mild buzzword "effectively" is not enough to drop it below 3.	3 / 3
Completeness	It answers both what ("Understand and manage Gamma API rate limits") and when ("Use when hitting rate limits, optimizing API usage...") with an explicit trigger-phrases clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Explicit trigger phrases "gamma rate limit", "gamma quota", "gamma 429", "gamma throttle", and "gamma request limits" are natural terms a user would say when rate-limited, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Gamma-scoped triggers ("gamma rate limit", "gamma 429") carve a clear niche tied to one API, making conflict with non-Gamma skills unlikely.	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
Commit: 1628598

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.