customerio-rate-limits

Implement Customer.io rate limiting and backoff. Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors. Trigger: "customer.io rate limit", "customer.io throttle", "customer.io 429", "customer.io backoff", "customer.io too many requests".

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 skill is highly actionable with complete, executable code and a clear step sequence, but it suffers from a monolithic inline body and orphaned bundle files that duplicate or conflict with it. Adding validation checkpoints and either wiring up or removing the redundant references would lift the weaker dimensions.

Suggestions

Link the references/ files from the body (or remove them) — they currently duplicate the body's content with conflicting code (Python vs TypeScript, different SDK package names), which wastes tokens and misleads.

Add an explicit validate→fix→retry checkpoint in the bulk-import and queue workflows (e.g., verify the 429/backoff path against a test burst before scaling), since batch operations should cap workflow_clarity at 2 without a feedback loop.

Move the long code blocks for the less-common strategies (queue-based, bulk import) into the references and keep the body as a concise overview pointing to them, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body itself is lean (tables plus five focused code blocks), but two bundle files duplicate the body's content with conflicting code (Python in implementation.md vs TypeScript in the body; @customerio/track vs customerio-node) and are never linked — token-wasteful redundancy.	2 / 3
Actionability	Provides fully executable TypeScript with imports, concrete rates (80/sec, 50/sec), 'npm install p-queue', and copy-paste-ready examples for each strategy.	3 / 3
Workflow Clarity	Five sequenced steps plus an error-handling table give a clear sequence, and the bulk import logs progress and counts errors, but there is no explicit validate→fix→retry checkpoint; the guideline caps batch operations at 2 without a feedback loop.	2 / 3
Progressive Disclosure	The body is a ~250-line monolith of inline code, and the two references/ files are never linked from the body and hold duplicate/conflicting material rather than well-signaled, one-level-deep supplementary detail.	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 specific, trigger-rich, and clearly scopes the skill to Customer.io rate limiting with an explicit 'Use when' clause. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'token bucket limiters, exponential backoff with jitter, queue-based processing, and 429 response handling' — rather than vague language.	3 / 3
Completeness	Explicitly answers what ('Implement Customer.io rate limiting and backoff') and when ('Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors').	3 / 3
Trigger Term Quality	A 'Trigger:' list gives natural phrasings a user would say ('customer.io rate limit', 'customer.io 429', 'customer.io too many requests') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Customer.io with distinct trigger keywords, making it unlikely to fire for unrelated rate-limiting skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 13 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 3 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.