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

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%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 body is lean and highly actionable with four complete, executable TypeScript patterns and a concrete error-handling matrix. Its only weakness is workflow clarity for the batch operation, which lacks an explicit validation/verification checkpoint.

Suggestions

Add an explicit validation/verification checkpoint to the batch workflow, e.g. a results-vs-errors threshold that pauses or halts the batch before continuing, to lift workflow clarity above the batch-operations cap.

Replace the vague Prerequisite "Understanding of async patterns" with a concrete, verifiable requirement (or drop it) to tighten conciseness.

Clarify how the four patterns compose (which to use when) with a short decision note, so the sequencing doubles as explicit guidance rather than four parallel options.

DimensionReasoningScore

Conciseness

Lean body with a model table and four executable steps that assume competence; it never explains concepts Claude already knows. The only marginal fluff is "Understanding of async patterns" under Prerequisites, not enough to drop it below the lean-and-efficient anchor.

3 / 3

Actionability

Four complete, copy-paste-ready TypeScript implementations (withBackoff, queuedGenerate with real endpoint/headers, TokenBucket, batchGenerate) plus a concrete detection/action error table; matches the fully-executable anchor; not a 2 because the code is complete rather than pseudocode.

3 / 3

Workflow Clarity

Steps are sequenced 1-4 with error capture and a burst-spike action, but batchGenerate is a batch operation with no explicit validation/verification checkpoint (e.g., verify/stop on a results threshold), which the rubric caps at 2; not a 1 because the sequence and error handling are clearly present.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is well-organized into Overview, Prerequisites, Model, four numbered Instructions, Error Handling, Output, and Resources with only one-level external links. The rubric allows a 3 for skills with no external-reference need when sections are well-organized; not a 2 because organization is clear.

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

The description is specific, trigger-rich, and complete, clearly stating both what the skill does and when to use it with natural Ideogram-scoped trigger phrases. It is well-distinguished from generic rate-limiting skills.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions — "rate limiting, backoff, and request queuing patterns" — matching the anchor that lists multiple specific concrete actions; not a 2 because it is comprehensive rather than naming only some actions.

3 / 3

Completeness

Explicitly answers what ("Implement Ideogram rate limiting, backoff, and request queuing patterns") and when via an explicit "Use when" clause, matching the top anchor; not a 2 because the trigger guidance is present rather than implied.

3 / 3

Trigger Term Quality

Provides a broad set of natural phrases a user would say ("ideogram rate limit", "ideogram throttling", "ideogram 429", "ideogram retry", "ideogram backoff", "ideogram queue"), matching the good-coverage anchor; not a 2 because common variations are well represented.

3 / 3

Distinctiveness Conflict Risk

Heavily Ideogram-scoped with distinctive "ideogram"-prefixed triggers, making it unlikely to fire for an unrelated skill; matches the clear-niche anchor; not a 2 because the scope is sharply specific.

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.