CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-rate-limits

Implement Ideogram rate limiting, backoff, and request queuing patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Ideogram. Trigger with phrases like "ideogram rate limit", "ideogram throttling", "ideogram 429", "ideogram retry", "ideogram backoff", "ideogram queue".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A strong, executable recipe skill with lean code and clear actionability, but it lacks validation checkpoints for its batch workflow and keeps all material inline rather than progressing to reference files.

Suggestions

Add an explicit validation/verification checkpoint to the batch flow — e.g., after batchGenerate, require inspecting the errors array and confirming success count before declaring the batch done — to lift workflow clarity.

Move the longer reference patterns (e.g., the TokenBucket limiter and full batch-with-progress example) into a references/ file linked from a concise overview, so SKILL.md stays a quick-start overview with one-level-deep navigation.

Clarify when to choose each of the four patterns (backoff vs queue vs token bucket vs batch) so the sequence reads as a guided decision rather than four parallel recipes.

DimensionReasoningScore

Conciseness

The body is code-forward with brief intros and tables, assuming Claude's competence (no explanation of what a 429 or backoff is); every section earns its place.

3 / 3

Actionability

All four steps provide fully executable TypeScript (withBackoff, PQueue, TokenBucket, batchGenerate) with concrete values like concurrency: 8 and a 50-prompt example — copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly labeled (Step 1-4) and the Error Handling table plus batchGenerate try/catch give some error handling, but this batch-operation skill lacks an explicit validate→fix→retry checkpoint, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Content is well-sectioned but ~180 lines are entirely inline with no one-level-deep reference files splitting the four patterns; for a skill this size, content that could be separate stays inline.

2 / 3

Total

10

/

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 distinguishes the skill with an explicit Use-when clause. It is concise without fluff and uses an appropriate imperative voice.

DimensionReasoningScore

Specificity

"Implement Ideogram rate limiting, backoff, and request queuing patterns" lists three distinct concrete actions, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers what ("Implement Ideogram rate limiting, backoff, and request queuing patterns") and when ("Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput"), with explicit triggers.

3 / 3

Trigger Term Quality

Six natural trigger phrases ("ideogram rate limit", "ideogram throttling", "ideogram 429", "ideogram retry", "ideogram backoff", "ideogram queue") give good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Every trigger is prefixed with "ideogram", carving a clear niche unlikely to fire for unrelated skills.

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.