ideogram-rate-limits
Implement Ideogram rate limiting, backoff, and idempotency 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-rate-limits89
Quality
86%
Does it follow best practices?
Impact
99%
1.35xAverage score across 3 eval scenarios
Discovery
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.
This is an excellent skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes explicit 'Use when' guidance, and lists natural trigger phrases that developers would actually use. The Ideogram-specific focus makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rate limiting', 'backoff', and 'idempotency patterns'. Also mentions specific use cases like 'handling rate limit errors', 'implementing retry logic', and 'optimizing API request throughput'. | 3 / 3 |
Completeness | Clearly answers both what ('Implement Ideogram rate limiting, backoff, and idempotency patterns') and when ('Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput'). Includes explicit 'Use when' clause and 'Trigger with phrases' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'ideogram rate limit', 'ideogram throttling', 'ideogram 429', 'ideogram retry', 'ideogram backoff'. These are specific, natural phrases developers would use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche focus on Ideogram-specific rate limiting. The combination of 'Ideogram' + specific error handling patterns (429, throttling, backoff) creates a unique trigger profile unlikely to conflict with generic API or rate limiting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code examples for Ideogram rate limiting with good structure and progressive disclosure. The main weaknesses are some unnecessary verbosity (prerequisites, basic explanations) and missing validation steps to verify the rate limiting implementation is working correctly. The code examples are production-ready and well-documented.
Suggestions
Remove the Prerequisites section - Claude already understands async/await and SDK installation
Add a validation step showing how to test/verify the rate limiting is working (e.g., logging successful retries, monitoring metrics)
Add explicit error recovery guidance for when max retries are exhausted (e.g., dead letter queue, alerting)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient but includes some unnecessary elements like the 'Prerequisites' section (Claude knows async/await) and verbose comments. The rate limit tier table is useful but could be more compact. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for exponential backoff, idempotency keys, queue-based limiting, and rate limit monitoring. All examples are copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | Steps are numbered but lack explicit validation checkpoints. The workflow doesn't clearly show how to verify rate limiting is working correctly or how to recover from persistent failures beyond max retries. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from understanding to implementation to examples. References to external resources and related skills are clearly signaled at the end. Content is appropriately organized for a single file. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.